yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] mastamoon:
Should we flash back to default then reflash the mod? Why the change between doing both to now only doing the ip up?
[Fascinate Android Development] imnuts:
You shouldn't have to, but you could. I decided to change it since it's only really needed for ip-up. I don't know fully how Android handles switching between 3G and wifi, but that is the only time I could see an issue arising, mainly if connecting to a corporate network or potentially a free wifi hotspot (hotel, cafe, or similar). Think of places that may have restrictions in place on browsing or a TOS agreement before use, and that would be a place were a potential issue could arise. If you have an issue, then I would try going back to the default and trying one of the new packages, otherwise, I'd just leave it as is.
[Fascinate Android Development] Falcyn:
Thanks for this! The Google package does work over 3G, but not over Wi-Fi.

You can test any DNS resolver by going to http://myresolver.info. There, you can see your resolver's IP address (and click the ? to find out who the IP belongs to).

Over 3G, the resolver is Google. Over Wi-Fi, though, it's my ISP. And it's definitely a phone thing, because over the same Wi-Fi connection my PC using Google's DNS shows Google's resolver.
[Fascinate Android Development] imnuts:
You should be able to set what DNS servers you want somewhere for WiFi as well, but I can't find how right now. If I do figure it out, I'll be sure to post back as well as update the first post on how to do so.
[Fascinate Android Development] geeknik:
Just set the same DNS servers for eth0 that you do for ppp0. =)
[Fascinate Android Development] imnuts:
But I can't seem to find any configuration file for eth0. In Wifi settings, it allows you to set DNS servers, but they don't seem to take unless you fill in the rest of the static IP settings.
[Fascinate Android Development] jstranges4:
So I'm now on DNS level 3 and its smooth (thanx!), but which of these are best to use in your opinions?
[Fascinate Android Development] imnuts:
The best is subjective, and will vary from location to location really. I prefer OpenDNS personally for the phishing detection and autocorrect on domain names. They also tend to update their cache really quickly, so if a site would change hosts, urls redirect properly faster in general. I haven't really used Level 3 or Google, but they may be faster for people than OpenDNS as they use anycast from what I can tell. This will change the actual DNS server your device queries be different from what it's set to as it will redirect you to the closest available server based on your locatioin.
[Fascinate Android Development] mastamoon:
Any idea if flashing kernels overwrites these changes?
[Fascinate Android Development] imnuts:
Kernel updates should not change this, nor should flashing themes. However, flashing ROMs will remove the change as they tend to format /system. You could bookmark http://myresolver.info and just browse to it after a change to verify.
[Fascinate Android Development] jt1134:
No
[Fascinate Android Development] jstranges4:
Thanks for the info!
[Fascinate Android Development] imnuts:
It's been found that using this will break your ability to send MMS messages. Receiving messages will still work fine. I'll look for a solution to this then so we can maintain the custom server while still being able to send pictures and video.

Sent from my Super Clean Voodoo Fascinate
[Fascinate Android Development] imnuts:
I believe I have found a temporary solution, which may be the only solution. Files in the first post have been updated. The change that was made removes the custom dns entry for the second server and instead replaces it with the network provided DNS server. I'll continue to look into trying to get a method that won't rely on the network, but I'm not sure if it will be fully possible to do so.
[Fascinate Android Development] pkopalek:
Click the link in the OP about manually doing this yourself instead of flashing that zip.

It is addressed there, and you can fix your mms with one terminal command.
[Fascinate Android Development] imnuts:
Not sure what you're getting at with this. Care to elaborate?
[Fascinate Android Development] mastamoon:
yes please share!
[Fascinate Android Development] imnuts:
I updated the zips again and they are now hopefully fixed with MMS working. Instructions post also edited to reflect the changes made in each zip. If you download from my Google Site, be sure to get revision/version 3.
[Fascinate Android Development] nexttonomy:
Thanks for fixing the MMS issues....I just installed the updated openDNS zip and my MMS messages work again!

Thanks again...

Nexttonomy
[Fascinate Android Development] imnuts:
Thanks for posting back that the latest update works. Glad you're enjoying it.

Sent from my Super Clean Voodoo Fascinate
[Fascinate Android Development] joebob2000:
What are the servers we are supposed to use for MMS to work normally? I did some digging on my phone (JT super clean 0.9) and found that the init.smdkc110.rc had just the google 8.8.8.8 and 8.8.4.4 addresses in it. However if I do a getprop I can see that the ppp adapter and the generic dns property both have some other address (66.174.95.44) in them, and that is what shows up if i browse to myresolver.info.

Is this just a big smoke and mirrors game, or what?
[Fascinate Android Development] imnuts:
I don't know if VZW uses the same servers across the country or not, so you need to leave at least one network assigned DNS server to be able to send MMS messages. You also can't send/receive MMS messages via wifi either.
[Fascinate Android Development] joebob2000:
I think I get it now... There are network assigned DNS servers coming in whenever a connection is established, and the addresses in init.smdkc110.rc must be some sort of default or last resort or something. Changing them, at least on my phone, seems to have no effect (contrary to the 'manual' suggestions in this thread...) Changing the ip-up script, as the zips do, is the only way to force an interface to take on a certain dns server as part of the connection process. Forcing them both to be set to your own (off-provider) server is a recipe for disaster since VZ has intranet-style naming available only to internal hosts.
[Fascinate Android Development] imnuts:
If anyone can figure out what server(s) the device tries to connect to while sending/receiving MMS messages, we could put the necessary addresses in the hosts file and dump the network provided server completely.
[Fascinate Android Development] Accord281:
Wait, so is MMS not working on WiFi? Can we please be clear as to what exactly is broken when you do this? Thank you.
[Fascinate Android Development] imnuts:
MMS never worked over wifi as far as I know, it only works over the data connection. If we could find out what server the phone needs to connect to and it's ip address, we could put that info in the hosts file and then be able to do mms over wifi.
[Fascinate Android Development] hetaldp:
in CDMA device we can also put DNS Server via QPST or QxDM which reside in NV of Device and become OS independent
[Fascinate Android Development] joebob2000:
The MMS server is probably not accessible from the internet-at-large, otherwise without an authentication scheme anyone could forward MMS into the network without paying for them. To be clear, this mod only changes the preferred DNS server your phone uses for name resolution, it will still have as a backup the internal automatically assigned dns server. Without doing this mod at all, your phone relies on the (sometimes slow) internal dns servers.
[Fascinate Android Development] psychomaniac189:
nice to see your still around imnuts! will this mod work on other vzw android phones? htc incredible perhaps?
[Fascinate Android Development] imnuts:
The mod will work, but you'll probably want to edit the ip-up file manually unless you confirm that it's the same as the one on the Fascinate. Otherwise, you may have connection issues.
[Fascinate Android Development] imnuts:
Just so people know, it looks like DL30 uses the same ip-up file as DH12/DI01/DJ05/DL09/EA29 does, so this will work on the Froyo leak as well.
[Fascinate Android Development] garywojdan81:
Tried flashing all three in jt's new cwm red & it errors out with a "bad file" msg & aborts. I'm on dl30 sc 1.0 with dl09 modem.
[Fascinate Android Development] NOsquid:
^^

Odd, it worked for me. Red cwm, dl30 super clean.
[Captivate Themes and Apps] clown_luv:
Im looking for the nexus one boot animation for captivate any one have a link to it that will work with perception build 5?

EDIT
[Captivate Themes and Apps] flashman2002:
What is cappuccino? Is that another device or a ROM?
[Captivate Themes and Apps] TheEscapist:
Any bootanimation will work, as long as it's named bootanimation.zip. Ask one of the guys in the Nexus forum, I'm sure they'll find one for you.
[Captivate Themes and Apps] flashman2002:
Ahhh...what a d-move haha. You said cappuccino in your first post and edited it to say captivate. I could have helped you had you used proper terminology. You can find bootanimations anywhere. Find a nexus ROM, download it and pull it from the zip...simple as that.
[Captivate Themes and Apps] King Shady:
Dude you're not funny at all. you're the actual ****.
[Captivate Themes and Apps] flashman2002:
And you have a problem...I clearly was kidding because I said I could have helped earlier. But because you are on the internet its cool to be childish like you. Anyway...be constructive and help the guy out and you may join the party. Otherwise take yourself some place else.

This is my captivate. There are many like it buy this one is mine.
[Captivate Themes and Apps] Pmac25:
In the second post here.

http://xdaforums.com/showthread.php?t=666959
[Captivate Themes and Apps] clown_luv:
Thank you
[Desire Q&A, Help & Troubleshooting] DJ 1:
Hi, please dont hate on me for bumping my topic, but really wanna try and get a fix for this...

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

thanks.
[G1 Q&A, Help & Troubleshooting] kjdsider:
I've searched with google and on these forums, but still haven't found an answer to this situation. Here's what I'm seeing and I'm not quite sure how to make of it.

This is on a rogers htc dream with the ebi1 port of roms. I've had 2 different roms with the same incident.

Main symptoms:

- Home and call buttons don't work

- Holding power button only gives reboot or power off

- - power off actually reboots

- can't receive calls. calls in go straight to voicemail

I had this happen on an éclair build after a long usage time(9 months?) and clearing davlik didn't work, so doing a full wipe + install fixed the issue. The new rom i used was cyanogenmod 6.1 with froyo, and everything worked fine after install. However, after installing all the apps back in, moving some to sd, getting gapps synced up correctly, etc etc, and rebooting, the same symptoms reappeared.

This seems to be some kind of issue with the phone module (is there such a thing?). I've ruled it out being a button hardware issue since the buttons feel and work fine in recovery and when i had the clean flash on. This happened on two different roms with two different android releases, so I'm thinking it's either an apps issue or some other kind of configuration issue that causes the phone functionality to partially disappear.

The only solutions I've found is to fullwipe and install, but i've tried it and it repeated itself after first reboot. So I won't go down that route just yet.

I'm not familiar with android but is there a way to access any kind of logs or how to do some debugging to figure out why these functions are missing?
[Windows Mobile Development and Hacking General] coolmoney:
please i need rom for o2 xda pm300 image 2.15.4.115 and spl 2.15.0001 thanks in advance:confused:
[Android Software/Hacking General [Developers Only]] discourse:
c:\androidsdk\usbdrivers" it says that the folder I specified doesn't contain driver

I've run into an error while trying to root my Nook Color. I'm doing it on a Windows7 32bit machine

When I reach this step " A new window will appear. In the Copy manufacturers files from: window enter c:\androidsdk\usbdrivers" it says that the folder I specified doesn't contain driver software.

I followed the USB ADB instruction to the letter quite a few times but still no luck.

Does anyone know what could be wrong?

I am new to Android.
[Android Software/Hacking General [Developers Only]] discourse:
[SOLVED]

Never mind. I got it sorted. The path in the tutorial is wrong.
[Touch CDMA Android Development] aceoyame:
I will be re-releasing 4.5 tomorrow with the odex script. In my testing it seems that 5 is a little slower, but has a lot more features. I will keep 4.5 as my speed build and 5 as my fast but little chunkier build.
[Touch CDMA Android Development] mikurej95:
Can you get screen shots?

I would really like to see the gingerbread look before i make any changes.
[Touch CDMA Android Development] aceoyame:
It has the regular Cyanogen mod 6.1 look. All I added from gingerbread was the animations. So whenever a prompt comes up or you use the lockscreen looks different. The gingerbread theme would require a lot of work to work with CM so I just used the animations as those were just xml files.
[Touch CDMA Android Development] necafe:
Is this a gingerbread rom?

I wonder this is gingerbread..

if then, does it changed some UI features?

You already answerd my question. Thanks..
[Touch CDMA Android Development] aceoyame:
Released 4.55 which is a re-release of 4.5. It contains updated modules + auto odex script. Also added in the web browser since skyfire needs it. Use 4.55 for maximum speed. RLS 5 is not the fastest build.
[Touch CDMA Android Development] vinny13:
Trying RLS5 right now! Looks good so far :)
[Touch CDMA Android Development] aceoyame:
Try rls 5.1! It includes a bug fix that was in 5.0. The fix brings the speed up to par with 4.55
[Touch CDMA Android Development] vinny13:
Will do... Should I wipe my data for this?
[Touch CDMA Android Development] aceoyame:
If you only just installed and wiped the data before do it. If not then I think you'll be fine. If you have any weird issues after that then do it. Also check the kaiser kernel development for a kernel that seems to have fixed data corruption issues. Not sure if it's just the kaiser that had the corruption or if it was all 3 devices.
[Touch CDMA Android Development] Prowess:
5.1 Odex Link

aceoyame,

Would you mind putting up the link for this? Thanks,
[Touch CDMA Android Development] vinny13:
It's on the first post already, the odexed 5.1 link has a typo at the beginning where it says

ht

http... Just remove that part and you're good to go.
[Touch CDMA Android Development] aceoyame:
Just fixed the typo.
[Touch CDMA Android Development] vinny13:
Hmm.. I noticed that the SD card does not mount correctly? I think? It seems like everything is looking for

/mnt/sdcard

when it's mounted as

/sdcard

... How can i fix this? Is it the builds fault or the kernel?
[Touch CDMA Android Development] aceoyame:
Are you using haret? If so in scoot's build there is a fix for that. Mine is based off his so any issues with his will be in mine.
[Touch CDMA Android Development] vinny13:
Nah I'm using nand... I think I built my kernel wrong in Atools :S

Am I supposed to set the fstab part to anything or just leave all three options on auto?
[Touch CDMA Android Development] aceoyame:
I always leave mine on auto and use the boot menu. I personally use sys on nand and data on an sd ext2 img.
[Touch CDMA Android Development] vinny13:
Ahh I figured it out :P

The fix is in Scooter's thread: http://www.mediafire.com/?ojnj6drt3ad8mu1

You should probably add that to your first thread.
[Touch CDMA Android Development] booblik2009:
Great ROM. Several issues so far:

1) Can't update Google Voice

2) Stock browser force closes without even opening

3) much-needed built-in clock is missing (any good free substitude?)
[Touch CDMA Android Development] aceoyame:
Well the clock is excluded since there is a clock in the task bar. Any clock will do, remember this is a barebones. I just heard about the browser issue and I thought I solved it before but evidently it is still there. Let me know if it was the odex or de-odex build that had the issue. Lastly I am going to try to figure out why google voice is not updating.
[Touch CDMA Android Development] vinny13:
After using for a couple days now I've experienced quite a few lockups where I've had to reset the phone, or get very sluggish, and also once or twice where the phone would just reset itself. Running the latest kernel on nand (VOGUIMG-320-FROYO-11-29-10.NBH) with RLS 5.1, anyone else having these issues?
[Touch CDMA Android Development] Does_It_Matter:
Is there some way to edit these so that they run from NAND?

I notice they make a system.img and data.img on the microSD card.

Kind of sucks for speed if you're running a class-2 mem card.

Trying to run this on a Vogue.

I typically do not install a lot of apps, so am not worried about running out of space in NAND.
[Touch CDMA Android Development] vinny13:
Its the kernel you're using. Go to l1q1d's sourceforge page and grab a kernel from there, and select system and data on the boot menu on the phone and you'll be good to go with the install. I had the same issue and that's what I did. Don't use Atools.
[Touch CDMA Android Development] aceoyame:
Just added 5.25. Delayed releases and had a lack of response due to ISP issues and the fact that I wanted to work out the bugs in 5.2.

Changes:

Fixed Xbins

Updated Market

Dropped filesize a little (only a few hundred Kbytes)

Slight performance increase
[Touch CDMA Android Development] booblik2009:
Woo-Hoo! It's been almost a day now since I installed 5.25 and all random reboot issues that were making your previous ROMs unusable on my Vogue seem to be gone. Thank you for all your hard work.
[Touch CDMA Android Development] aceoyame:
Thank you for the comments. You should be thanking Daedric though, he provided the Xbins fix and the updated market for me. The Xbins is what was causing the biggest stability issue after the storage bug that existed in RLS 5. This is my final release until CM 7 is released on the Dream or Sapphire. I just cannot improve 5.25 any more besides slight incremental updates for things like the market.
[Touch CDMA Android Development] mrbryan:
so far lives up to your suggestion of fastest build. Most responsive since warm donut for me.

Thanks!
[Touch CDMA Android Development] aceoyame:
To be honest 5.25 is my 2nd fastest build lol. For max speed get 4.55, dunno what it is but that build scores on average about .2-.4 Mflop/s faster in linpack. Guessing it might be a difference in the nightly CM builds. But yes, I use 5.25 myself just because it looks much more polished.
[Touch CDMA Android Development] ricerony:
sd card functionality?

for the life of me i can't get my sd card working... Do i need to install this with atools? I've been away from the scene for a good while.

so i put the install in the sd card /andboot folder. nothing else is in there. Installed system and data on nand, but after everything finishes and android boots up i go to settings and check on sd card, it shows as unavailable. At first i thought it was a bad flash, but i've done this over 10 times and tried 2 different cards and its still not working.

can someone please help me? I even tried formatting a 2nd partition as ext2 and that still does not populate anything.
[Touch CDMA Android Development] aceoyame:
I've heard about this with a couple SD cards. From what we saw was it was just the SD card they were using. You followed everything correctly if you were able to boot in.
[Touch CDMA Android Development] Does_It_Matter:
Do you have a Vogue?

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

You have to apply the Vogue SD fix

I had the same issue, and had to apply that Vogue SD fix

I guess the rom works just fine on Kaiser/Polaris, but Vogues need the SD patch
[Touch CDMA Android Development] Prowess:
THAT IS IT! THANKS, I should stay in vogue,
[Touch CDMA Android Development] WnG88:
Can you post an update to have the status bar in black or a black theme?
[Touch CDMA Android Development] aceoyame:
I could but that requires far to much work for myself. I think thoughtless kyles black theme might work on the deodex version if you add the files but I myself will not do that as it is not my work. On the other hand if you try it out yourself it is ok. I tried to add a black theme before and it completely messed with the Gingerbread theming that was done.
[Touch CDMA Android Development] scooter1556:
In my CyanogenMod build which this build is based off you can go to 'Settings-CyanogenMod Settings-User Interface - Tweaks extras - Select a theme - 'STOCK_Black' which will give you the black status bar etc. Unless it's broken in this build because of the gingerbread stuff added to the framework this should work ;)
[Touch CDMA Android Development] cyburke:
how is the battery life on the 5.25 build? i am interested to try this one on my vogue but am hoping that it gets pretty good life!
[Touch CDMA Android Development] Josue_181:
According to this commentary the battery life not is much in comparison with other builds.
[Touch CDMA Android Development] aceoyame:
Battery life is = to any other froyo build. Battery life comes from your kernel not your build. If the kernel itself has bad life then obviously the build will. Essentially if the phone is running with a kernel that has good life then it should be faster than an equivilent Donut build as the cpu has more time to sit idle.

Also it MAY work with the .25 kernel, I have no idea. I think I recall someone having it work with the latest .25 kernel, but that may be due to it having enough modules from .32 now to work.
[Touch CDMA Android Development] hom.hom:
GREAT/FAST BUILD!:D

And I know it is an extra, but how do you change the profile of the build, to use it on the new google android market site. Right now, it says to be not compatible woth my device which is profiled as T-MOBILE HTC CyanogenMod Kaiser/Kaiser. Maybe to profile the phone as HTC Legend of something like that....
[Touch CDMA Android Development] andrewmp:
Hey, love this ROM. Where can I get the Google Calendar APK for it?
[Touch CDMA Android Development] tablo:
sorry if this is a stupid question but does GPS work on this build?
[Touch CDMA Android Development] scooter1556:
I would imagine so, it works on all other builds for Vogue/Kaiser and no one has reported that it doesn't :)
[Touch CDMA Android Development] ricerony:
it works well for me using googlemaps.
[Touch CDMA Android Development] adeyo:
a little help needed on a great build

this rom is great -nice and fast! thanks!!

on another note, i am experiencing sometimes that the phone won't wake after it goes to sleep, requiring a reboot. anyone know how i might fix this? I am running the latest kernel 2.6.32 (14_01_11) from here: http://it029000.massey.ac.nz/vogue/files/voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh ...i overclocked to 572 w/ rogue tools. pushing the side camera button lights up the green/red phone control buttons, but no screen will awake.

any tips appreciated!

EDIT: now experiencing random reboots too :(
[Touch CDMA Android Development] Omegavirus:
maybe the overlock is too high.. there seems to be a touchscreen/reboot/lag bug with newer roms when you overlock.. /:

also at 480mhz the touchscreen of my devices acts random.. /:
[Touch CDMA Android Development] adeyo:
thanks for the tip! i will try to reset the clock to the default. i try to power the phone off to charge, but it automatically keeps coming back on.

EDIT: ...what do you recommend for clock speed?
[Touch CDMA Android Development] Omegavirus:
the best should be to leave it at 400mhz (stock) until the problem is solved i think..
[Touch CDMA Android Development] sovogue:
Originally installed Myn's Warm Donut using NAND instruction from crobs808.

Tried to update to Gingerbones by copying the install.tar to sd card and holding volume/d pad to choose nand install. Installed but is not working right.

I'm missing a step, yes?