yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] :
here's how i see it. if you are using your phone, tethered to your computer, for things that you can/would do on your phone, i don't see a problem. netflix is available to stream directly to your phone, so why not have that same film on your larger screen? the one concession i'll make is that the bit rate may be higher on your pc to accommodate that larger screen, but otherwise, web surfing/podcasting, is going to be the same, no matter what.

that's the mantra i live by when tethering, if i can't do it on my phone, i don't do it on my pc. even without tethering, i'm using many gigs every month. it's just more convenient to make this post from my pc.
[EVO 4G General] nerrollus:
That's the way I've been doing it since they finally released a NetFlix app on the phone. It's just a lot easier to see and type on a laptop. I think there is a measurable difference in the bandwidth used for streaming to a laptop vs a phone, but I don't really know exactly how much. It's enough that I've noticed a significant drop in usage since I started watching it on my phone instead of laptop. I also used to play video games like EVE Online and Darkfall while teathered, but figured that was pushing it a bit since I'm not paying for their teathering service. lol :)

I also do a lot of remote support at sites with a 56k dial up modem as their access to the outside world... There have been a lot of instances where I'll use my phone to download some files I need at 3g/4g speed, then share the SD card as a hard drive and copy the files to several computers at the site.

I went into this deal with Sprint because they offered the only unlimited plan in the area. I've always assumed that if I'm paying for unlimited service I should have it. *shrug*
[Captivate Q&A, Help & Troubleshooting] yogib83:
My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems? :confused:

This is why I ask.

So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.

The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.

After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen. :eek:

Now at this point I'm really pissed off :mad:. I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success :D. The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier. :cool:

So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.

Thanks in advance for any and all help.
[Captivate Q&A, Help & Troubleshooting] kppanic:
Again... I hate to be that guy but you are posting in the wrong forum.

Please read the stickies and the rules before you decide to post.
[Captivate Q&A, Help & Troubleshooting] jhernand1102:
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...:)
[Captivate Q&A, Help & Troubleshooting] kamots:
try afv or something like that in the market. Its by scary alien and you can verify md5 sum nand backup. i just flashed a new rom but once I get all set up I will come back with the name. Its a free in the market.
[Captivate Q&A, Help & Troubleshooting] yogib83:
Thank you good Sir! That makes perfect sense. :D
[Captivate Q&A, Help & Troubleshooting] jhernand1102:
No problem Glad to help. Next time if you flash stock after installing ROM manager you can flash the kernel first and then don't boot up just go back into CWM recovery and then restore your backed up ROM and it will work fine.
[HD2 General] metroidnemesis13:
I have an HD2 I just bought, should be still under warranty (aside from running wp7 and random warranty-voiding stuff) and I am noticing an issue of when I totally kill it, it seemingly won't charge (or no charge light comes on at least) until I pull the battery out and put it back in. Also, I have noticed it doesn't power on from that state (light goes from orange to green) until I pull out the battery and put it back in. Is it just because I'm running WP7 and hardspl3 or radio 2.14.50... (or whatever recommended radio is for wp7). It's not a huge deal but it makes me curious. Also I get occasional restarts upon booting wp7 but it always boots into it (maybe 1 or 2 restarts every ten boots, and it seems to happen more after total kill). Just wondering if people are having similar issues.

WP7 is pretty cool, but I am wondering how many prefer 6.5? I'm an avid Android user (never ran 6.5 except on a Blackjack ii briefly, and yes, 6.5) and I was curious what you guys thought of wp6.5 vs wp7.

Lastly, I am wanting a magldr compatible sd version of a Desire HD ROM with sense and everything that isn't overclocked (I know there are some out there that are, ie DL.DesireZ 3.x).

Please advise.
[HD2 General] Kailkti:
It's not WP7, it is MAGLDR. MAGLDR does not have a software in it which allows the phone to charge when off.

My advice to you, never, ever, let your phone lose charge. A dead battery is a dead phone in our case, unless you have spare batteries.
[HD2 General] metroidnemesis13:
I figured something like that. It's not going to botch the magldr flash though if it dies, is it? I would assume magldr is read-only or close to or something like that to where it can't corrupt itself.
[HD2 General] Kailkti:
I don't see why a dead battery can kill MAGLDR, it'll just leave your hd2 unable to turn on. However MAGLDR, I assume, isn't incorruptible. Well if you're afraid of corruption from leftover flashing, for whenever you want to flash WP7, Android or winmo, perform a task 29 first, flash MAGLDR, and then the OS. Well if it winmo, then a task 29, then simply flashing winmo and done.

Oh and the reason WP7 kept on rebooting on yours was because your sd card was incompatible. My advice is to reformat the sd card with panasonic formatter, full format btw, and then reinstall WP7. If that doesn't work, you just have to get a new card.

A MAGLDR SD desire hd version I know not of. Since NAND came out, SD development has died off so there are only a few developers that still strive in that forum.
[HD2 General] metroidnemesis13:
Well it restarts hardly ever so I probably am not going to worry about it. It's the stock HD2 sd that came with the phone. The reason I want an sd build is because I want to dual boot.
[HD2 General] bates_1974:
I don't understand how I seem to be the only one who can charge in magldr.

I've drained my battery many times to the point where it doesn't turn on to calibrate using Android. Pulled battery, reinserted and connected wall charger. Orange light comes on which means it's picking up charge, leave it for a few minutes so it gets some residual charge in it, pull battery and charger, reinsert, boot up, then during boot process plug the charger back in and away you are, charging from scratch.
[HD2 General] TheATHEiST:
I too didnt have any problems charging dead batteries via MAGLDR.

Those who are can update to version 1.13 as its now got a workaround for it apparently.
[HD2 General] metroidnemesis13:
I wasn't aware v13 was even out. Well it's not a big deal. Glad everyone is having this issue :P. This bug still beats having to wait 20 minutes for my stock Sammy Vibrant to boot up. Damn ridiculous.

Is your battery life worse on WP7 or WP6.5? I get roughly 8-10 hours. I'm surprised it burns that much electricity seeing as how all it is is some colored squares and no data connection or multitasking.

EDIT: Updated to MAGLDR ver. 1.13 without a hitch. Will see how this goes. For the record I was using 1.12.

I guess this is the fix:

"*Fixed Power-Off-Cable-Plug-Stop. Phone now detects this situation and reboots. Battery controller inside LEO needs runtime control during charge, it implemented in OS."
[HD2 General] bates_1974:
I could do it on the first version of magldr, as long as the Orange light comes on you're good to go, just leave to get some charge then pull everything reinsert turn on, simple...
[HD2 General] dc1128:
I found the trick--MAGLDR V1.13

Plug the phone into a wall charger. Hold the call end button as soon as the phone comes on booting into MAGLDR. Let the phone stay at the MAGLDR menu screen for about 15 to 20 minutes. Restart the phone and leave it on the charger. It will have enough power to make it to the android home screen.
[HD2 General] sarblohw:
sorry for the delayed reply bro but i justr had this problem lately and know abt the fix for it... just go into magldr by pressing the power key for sumtime on bootup... after that plug in the wall adapter for about 20 - 30 minutes... havng done that remove the battery and insert it agiain w/o the charger... start the phone and let it go the main wp7 screen where it will stay for only about 20 seconds... quickly run to the settings menu and switch on airplane mode and put the brightness to the lowest setting... and quickly lock the screen... the phn will start charging fine... now leave it for an hour to charge and then adjust the brightness as u like and turn on airplane mode... it will work fine... take precautions for next time... there is a kind of an odd fix that was in forums...(sorry dont have the link)... when the wp7 is working go to the default camera and go to the video camera mode and switch back to the still camera and press the windows buttn to go to the main screen... the battery drainage is very less in this case and the stanby increases... cheers!
[EVO 4G Q&A, Help & Troubleshooting] erik077:
I want to remove amon_ra and go back to Rom Manager? How to do this ?
[EVO 4G Q&A, Help & Troubleshooting] Vandelay007:
All you need to do is open rom manager and flash clockwork recovery right from there ....
[EVO 4G Q&A, Help & Troubleshooting] erik077:
Thanks! If am not wrong I can switch between them any time I want ?
[EVO 4G Q&A, Help & Troubleshooting] Vandelay007:
Yeah, just don't try to restore nandroids from one with the other
[EVO 4G Q&A, Help & Troubleshooting] erik077:
Thanks again
[EVO 4G Q&A, Help & Troubleshooting] Vandelay007:
Any time, glad I could help
[Vibrant Q&A, Help & Troubleshooting] jellette:
I ported random rom #100 to Vibrant the other day - nothing you guys will want. BUT, it had a live wallpaper as the default wallpaper. My question, that I can't figure out, is how to set a roms default wp as a live one on first load?
[Epic 4G General] socos25:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.

I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.

I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...

I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??

I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
[Epic 4G General] Kanojo:
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.

Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.

Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.

Hope this was of some use!
[Epic 4G General] socos25:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.

I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.

The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..

Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...

Oh well, it has made me more aware of what is going on behind the scenes with my phone.
[Epic 4G General] coryshad:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.

Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
[Epic 4G General] Kanojo:
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
[Epic 4G General] csmacdroid:
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
[Epic 4G General] || Acer ||:
I am so glad I didn't update to 1.0.7!
[Epic 4G General] dr_gibberish:
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.

Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
[Epic 4G General] socos25:
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.

What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.

I think for some reason you have to install it twice.. Strange I know..
[Epic 4G General] eddieyee:
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
[Epic 4G General] kos26:
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
[Epic 4G General] socos25:
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.

Want to try a speedtest with the wifi tethering while going down th road.

I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
[Sony Ericsson XPERIA X10 Mini] ysfm:
hii

i want to know whats the serial

which i have to change in the build.prob

so u can update my x10 mini with the middle east firmware??
[Desire Q&A, Help & Troubleshooting] njay222:
I currently have a htc desire on three. I tried rooting it today using the revoke method, revoke says done. However htc desire is still not rooted. Going to the hboot section and recovery mode gives me the following messages.

ClockworkMod Recovery v2.5.0.7

E: Can't Find MISC:

E: Cant mount cache : recovery/command

E: Can't FInd MISC:

E: Can't mount Cache:recovery/log

E: Can't find MISC:

I have used revoke program about 40-50 times. Sometimes it wont root saying firmware too new. Sometimes it went through and said done. Ran the programme on both windows and linux as i heard windows could have driver problems even though i installed the drivers properly. DId have force 2 sd before however undid this early today before rooting. I have also reset phone multiple times to see if that helped.
[Desire Q&A, Help & Troubleshooting] mikep99:
Its because you have a PVT4 Desire.

You need AMONRA recovery.

Do a search, there's been a number of posts about this recently.
[Android Software/Hacking General [Developers Only]] Rosco911:
So I tried it yesterday, downloaded an app, and recognized my phone, sent it, all was good, was a free app btw.

But today I decided to buy an app....whent to the paying option, and I got a message saying that the phone is not on my carrier, and couldnt download content.

This blows!

Anyone with any more issues from the market web store?
[Android Software/Hacking General [Developers Only]] Takkie85:
I got the same ... No idea how to (re)add my phone. The first download was seamless, no probs what so ever, now it doesn't reconize i even have a phone.

HTC Hero - Tastyfroyo
[Epic 4G Q&A, Help & Troubleshooting] zanderman112:
Im using the gingerbread keyboard right now. So i was wondering if someone could do the same for the honeycomb keyboard? If you think i should request this somewhere else, please tell me where.

Sent from The Chaotic Void
[Epic 4G Q&A, Help & Troubleshooting] musclehead84:
Is it out yet?
[Epic 4G Q&A, Help & Troubleshooting] zanderman112:
I do not know. I get most of my info here. Like i didnt know about the gb keyboard till somebody posted the renamed apk. I posted here cause i trust the epic devs. I was hoping somebody would know.

Sent from The Chaotic Void
[Galaxy S I9000 Themes and Apps] Tehpriest:
Came across this little bit of magic while looking for one for my low power but brilliant Commtiva N700 tablet. It has only failed to play 2 vids for me so far , one it did a weird split screen thing with (.FLV) and the other had no vid but both played the music.

Xyplayer. Free on the market and I have no connection whatsoever. Just think it's worth telling about.

(I did try the Neon version which is for Cortex-A8 handsets (the Commtiva is supposed to be Cortex-A8) but it just would not work.
[Droid Incredible Q&A, Help & Troubleshooting] frontay:
Hello everyone,

I recently rooted my friend's Droid Incredible, and installed Myn's Warm 2.2. He told me he was unable to send pictures from it. I told him that the image file was probably too large, and it wasn't being compressed down into a size that is acceptable to be sent as sms over the Verizon network. I told him the usual, try restarting your phone, maybe that will help. I tried sending him a picture (1288KB) from my Evo (sprint) and received a message from sprint saying "that the receiving service provider has a size limit for picture and video. My message may not be received." So I have a couple of questions

Does anyone know what that size limit is? Is there a rule of thumb i should remember when sending a photo via sms, like "Dude, don't try to send a photo over 500KB" or something like that.

What Roms will automatically compress images for the user when they are going to send them via sms, is this only on the stock rooted Roms?

Please if you have any suggestions, comments, ideas they are much appreciated
[Droid Incredible Q&A, Help & Troubleshooting] g00s3y:
I think the size limit for the INC is 1MB.

I believe the phone sending the picture will automatically resize it if it is bigger then the limit for that phone. But the receiving phone doesn't resize the message sent, I think it has to be 1MB or less.
[Droid Incredible Q&A, Help & Troubleshooting] frontay:
I am running the latest mikfroyo, it does not. And on his phone is not resizing the images before being sent either. I guess I will just read up on the roms, and try out a couple others on his phone.
[Vibrant General] ttibbetts83:
to fix avatar after updating to froyo you need to clear your drm protocal

go to settings

tap applacations

tap all

scroll down to drm protocalls and tap that

tap clear data

reset phone 2 or 3 times and movie will play

to root just use superoneclick
[Vibrant General] kmfisher:
This worked! I cleared it, rebooted and tried it. It failed, so I rebooted again and it worked. Thanks!
[Vibrant General] hireafiretruck:
Thanks ttibbetts83 worked after second restart!
[Vibrant General] gravelox:
Or just launch the video player. It'll load Avatar.
[A7 General] Plasmah:
Does Darktremor Apps2SD work ok on the Elocity A7?
[A7 General] sdialect31:
I have tried it but, it seems the mount point for A7 is not what the program expects so things end up on internal storage instead of sd card. /sd and /mnt/sd appear to point at internal locations, OEM has hosed this one.
[Captivate Q&A, Help & Troubleshooting] bbto:
hi,

i'm going to flash a custom ROM to my i896, i'm currently on stock ROM + speedmod k12t, have already disable lagfix, and backup all data.

i did researched, but what i want to know is not there.

i know i need to be on stock ROM to before flash, since i'm on stock rom, i still have some questions

so i got 2 questions:

1. do i need to flash back to restore kernel before flashing ROM?

2. after flashed ROM, do i need to flash the speedmod kernel aagain?

thank you.
[Captivate Q&A, Help & Troubleshooting] mengbo:
1. no, you don't need to flash to the stock kernel;

2. usually the rom comes with certain version of kernel, you can definitely replace it if you want to use the latest speedmod, for example.
[Captivate Q&A, Help & Troubleshooting] bbto:
thank you so much.

i got another question

i use odin3 to flash ROM

i put the ROM file in the PDA section. leave phone and CSC blank.

but what should i put in PIT section?
[Captivate Q&A, Help & Troubleshooting] mengbo:
usually i only use odin3 to flash to the stock rom. you need to put .pit file in the PIT and a tar file in PDA.

but since you are flashing to a custom rom, usually you can get the cwm file and use cwm to flash. it is easy and quick.