[Q] Darkstones superRAM and Tmo-US users? - HD2 Android Q&A, Help & Troubleshooting and Genera

So, I'm interested in Darkstones latest build. I'm currently running Froyostone3.2 w/MooMoo MMS Fix.
So, my question is this: Does the superRAM build send/receive MMS correctly on T-mobile US? Are they the correct size, or are they all small and distorted? I'm reading mixed things in the main thread in regards to it, and most of that is several days old.
This is the only thing that keeps me from switching to that build. I text constantly and I'd hate for the main use of my phone to be limited.
I'm currently using stock 2.10ROM and 2.12 radio. I'm aware that should I get the superRAM build I'd need to go to 3.14 and 2.15.
Thanks for any and all help that doesn't involve "Search the threads n00b" or "google it...". Been there, done that. Thanks again!

pretzdothack said:
So, I'm interested in Darkstones latest build. I'm currently running Froyostone3.2 w/MooMoo MMS Fix.
So, my question is this: Does the superRAM build send/receive MMS correctly on T-mobile US? Are they the correct size, or are they all small and distorted? I'm reading mixed things in the main thread in regards to it, and most of that is several days old.
This is the only thing that keeps me from switching to that build. I text constantly and I'd hate for the main use of my phone to be limited.
I'm currently using stock 2.10ROM and 2.12 radio. I'm aware that should I get the superRAM build I'd need to go to 3.14 and 2.15.
Thanks for any and all help that doesn't involve "Search the threads n00b" or "google it...". Been there, done that. Thanks again!
Click to expand...
Click to collapse
lol...very similar here.
was using a moomoo fix build then switched to darkstone super ram 1.5. i am also on tmobile usa, and mms works perfectly.
what i did was, in the moomoo fix build, i backed up the apn, with apn backup from market.
then when i switched to darkstone super ram, i restored the apn using the same app

dapoharoun said:
lol...very similar here.
was using a moomoo fix build then switched to darkstone super ram 1.5. i am also on tmobile usa, and mms works perfectly.
what i did was, in the moomoo fix build, i backed up the apn, with apn backup from market.
then when i switched to darkstone super ram, i restored the apn using the same app
Click to expand...
Click to collapse
Excellent, thanks! I'm curious though. What moomoo build were you using? The same as I, or one of the different ones? Also, how's the data like?

pretzdothack said:
Excellent, thanks! I'm curious though. What moomoo build were you using? The same as I, or one of the different ones? Also, how's the data like?
Click to expand...
Click to collapse
id remember exactly what mood build, but data on super ram is alright, with slight drops here and there.

Related

Non working WiFi or Mobile Web on Cyanogen ROMS

I'm stumped. And agitated.
I'm stumpitated.
Every Cyanogen-based ROM i flash, I cannot get Wifi or mobile web to connect.
This is true of all current Froyo builds (all Cyanogen) and roms like Droid Does.
Weird thing is, I can get connected to wifi and ping local computer IPs. But I cant ping any websites or load them in the browser or apps.
I am flashed to MetroPCS. Haven't had any problem in ROMS like PlainJain, xtrROM, Evil Eris, etc.
Anyone have any troubleshooting steps or insight? Thanks in advance - I love this community!
jessebwallace said:
I'm stumped. And agitated.
I'm stumpitated.
Every Cyanogen-based ROM i flash, I cannot get Wifi or mobile web to connect.
This is true of all current Froyo builds (all Cyanogen) and roms like Droid Does.
Weird thing is, I can get connected to wifi and ping local computer IPs. But I cant ping any websites or load them in the browser or apps.
I am flashed to MetroPCS. Haven't had any problem in ROMS like PlainJain, xtrROM, Evil Eris, etc.
Anyone have any troubleshooting steps or insight? Thanks in advance - I love this community!
Click to expand...
Click to collapse
wifi works for me using Cyanogen-based ROMs i know for a fact because my phone isnt activated and i use wi fi
Are you using a custom kernel or something?
Hungry Man said:
Are you using a custom kernel or something?
Click to expand...
Click to collapse
Not that I'm aware of - how would I find out? Do the ROMS themselves not define the kernel?
Beyond that, why would it work in all other non-cyanogen based ROMs?
jessebwallace said:
Not that I'm aware of - how would I find out? Do the ROMS themselves not define the kernel?
Beyond that, why would it work in all other non-cyanogen based ROMs?
Click to expand...
Click to collapse
wifi does work , what rom are u using ? cuz again i have to use wi fi to test somethings and it works perfectly
tazzpatriot said:
wifi does work , what rom are u using ? cuz again i have to use wi fi to test somethings and it works perfectly
Click to expand...
Click to collapse
I said Wifi doesnt work for me, not for you. Thats the issue altogether - it seems isolated for some reason.
I tried KaosFroyo, CELB and the CM direct, as well as DroidDoes (TCP's new cyanogen based). Can't get Wifi or Mobile to work on any other them. ROM doesnt matter, it seems to be anything cyanogen based for me.
Grdlock, Ivan, xtrRom, xtrSense, EvilEris, etc have all worked for me completely though - non cyanogen based.
jessebwallace said:
I said Wifi doesnt work for me, not for you. Thats the issue altogether - it seems isolated for some reason.
I tried KaosFroyo, CELB and the CM direct, as well as DroidDoes (TCP's new cyanogen based). Can't get Wifi or Mobile to work on any other them. ROM doesnt matter, it seems to be anything cyanogen based for me.
Grdlock, Ivan, xtrRom, xtrSense, EvilEris, etc have all worked for me completely though - non cyanogen based.
Click to expand...
Click to collapse
i know ur not talkin about me lol im just tryin to help u out ,, sorry just tryin to help u out
tazzpatriot said:
i know ur not talkin about me lol im just tryin to help u out ,, sorry just tryin to help u out
Click to expand...
Click to collapse
No prob dude, I know what you meant. Didnt mean to sound ungrateful
Its just such a weird thing, and I feel limited by it, and the fact that it seems to be so isolated is irritating.
Works for me on CM5 and CM6 ROMs.
hallstevenson said:
Works for me on CM5 and CM6 ROMs.
Click to expand...
Click to collapse
Guys,
I know it works on other peoples phones. Not being rude, but I dont need a list of people who its working for. I'm asking for some help, some direction, some possible things to check.
Not to be off topic.. but can someone direct me to the CM direct ROM? I haven't seen that anywhere. Sorry if thats a stupid question lol
Its just the one with CM in the post title.
http://forum.xda-developers.com/showthread.php?t=728866
jessebwallace said:
I'm stumped. And agitated.
I'm stumpitated.
Every Cyanogen-based ROM i flash, I cannot get Wifi or mobile web to connect.
This is true of all current Froyo builds (all Cyanogen) and roms like Droid Does.
Weird thing is, I can get connected to wifi and ping local computer IPs. But I cant ping any websites or load them in the browser or apps.
I am flashed to MetroPCS. Haven't had any problem in ROMS like PlainJain, xtrROM, Evil Eris, etc.
Anyone have any troubleshooting steps or insight? Thanks in advance - I love this community!
Click to expand...
Click to collapse
Try my flash for metro here:
http://forum.xda-developers.com/showthread.php?t=730289
As always make a nandroid backup first.
Make sure you have booted your rom at least once successfully before applying my flash (it modifies the telephony.db that will not be present until after the first boot)
The problem you are running into is that in the build.prop the carrier info is still pointing to verizon, once i changed mine to cricket it worked, i assume changing it to metro would work for you as well.
I believe metro's proper MNC should be 310024 if you want to edit it manually, if i recall off the top of my head, anyways my flash should set that for you and get you squared away.
EDIT**
Actually sorry i mis read this, my flash will not assist with WIFI but it should get your mobile network to route through metro's proxy and get MMS working.
This sounds like a ROM issue if wifi is not working, or something hardware related.
token419 said:
Try my flash for metro here:
http://forum.xda-developers.com/showthread.php?t=730289
As always make a nandroid backup first.
Make sure you have booted your rom at least once successfully before applying my flash (it modifies the telephony.db that will not be present until after the first boot)
The problem you are running into is that in the build.prop the carrier info is still pointing to verizon, once i changed mine to cricket it worked, i assume changing it to metro would work for you as well.
I believe metro's proper MNC should be 310024 if you want to edit it manually, if i recall off the top of my head, anyways my flash should set that for you and get you squared away.
EDIT**
Actually sorry i mis read this, my flash will not assist with WIFI but it should get your mobile network to route through metro's proxy and get MMS working.
This sounds like a ROM issue if wifi is not working, or something hardware related.
Click to expand...
Click to collapse
Already running your flash, boss
Doesnt make a difference on these roms for me.
Works nice on xtrROM, though
Hmm, so to clairify if you use CELB 2.8, boot it, then flash my flash, then boot CELB then reboot CELB that you still do not get mobile web/mms?
Weird, almost sounds like your not getting DNS or something.
if you do an NSlookup on like www.google.com, then on the phone try to ping the number you got from nslookup, do the numbers match or what comes back?
I think that this flash won't work for some Froyo ROMs for whatever reason.
Either Autostart doesn't start up (did it ever ask you for SuperUser permissions, ever?)
Or
u2nl needs to be in a different place (worth investigation)
Or
Your proxy is set correctly, so wifi is trying to go through the proxy (which may not work), but something else isn't working correctly, so wifi is looking through the proxy, but something ELSE is wrong with mobile network.
Do a nand backup
then restore yourself to a 2.1 ROM and make sure it still works.
Is the first condition I listed at the top of this post, the case? Or did it ask you? 2.2 might have a superuser issue with Autostart. That'd make sense, since the Proxy might be working (which would be why your internet won't work when wifi is on), but your Mobile Network won't (which, of course it wouldn't, of Autostart wasn't starting up).
jessebwallace said:
I know it works on other peoples phones. Not being rude, but I dont need a list of people who its working for. I'm asking for some help, some direction, some possible things to check.
Click to expand...
Click to collapse
Sorry, but I don't know what there is to "check". There are NO options or configurations necessary with the WiFi setup.
token419 said:
Hmm, so to clairify if you use CELB 2.8, boot it, then flash my flash, then boot CELB then reboot CELB that you still do not get mobile web/mms?
Weird, almost sounds like your not getting DNS or something.
if you do an NSlookup on like www.google.com, then on the phone try to ping the number you got from nslookup, do the numbers match or what comes back?
Click to expand...
Click to collapse
K, CELB 2.8 was the first Cyanogen rom to work, thats cool - but it didn't work with your flash. I had to do the manual input from the guide. I already had autostart.sh and u2nl in my root - does your flash overwrite them? still, even if it didnt, it should have set the right permissions, right? I wasnt until I input all the shell commands that I got mobile and app web.
I think that this flash won't work for some Froyo ROMs for whatever reason.
Either Autostart doesn't start up (did it ever ask you for SuperUser permissions, ever?)
Click to expand...
Click to collapse
Yes, it did ask me for permission. On all ROMs ive tried, Froyo, DroidDoes, etc.
Or
u2nl needs to be in a different place (worth investigation)
Click to expand...
Click to collapse
Seems plausible
Or
Your proxy is set correctly, so wifi is trying to go through the proxy (which may not work), but something else isn't working correctly, so wifi is looking through the proxy, but something ELSE is wrong with mobile network.
Click to expand...
Click to collapse
This wouldnt explain while neither Wifi NOR mobile web doesnt work on either. I can't get either to work all all, and they both work on regular 2.1 OTA Roms (and now CELB 2.8)
Do a nand backup
then restore yourself to a 2.1 ROM and make sure it still works.
Click to expand...
Click to collapse
I use xtrROM 3.0 day to day, and its always worked. So yes, it still does.
Is the first condition I listed at the top of this post, the case? Or did it ask you? 2.2 might have a superuser issue with Autostart. That'd make sense, since the Proxy might be working (which would be why your internet won't work when wifi is on), but your Mobile Network won't (which, of course it wouldn't, of Autostart wasn't starting up).
Click to expand...
Click to collapse
Autostart asks for permissions, so I assume its starting i'll try again just to confirm. You mentioned the Proxy might be working which would cut the wifi - how do I get around that?

How to limit Email File Size received on Froyo?

Is that anyway to set this in incoming mail for Android like what I do in Winmo ? Or any application can do it ?
Yep.....
Mail>Windows Button>More>Settings>Send & Recieve>Mail Size Limit....
Thanks for reply but I cant see MORE option as I am using Froyo 2.2 by Darkstone.
osrg said:
Yep.....
Mail>Windows Button>More>Settings>Send & Recieve>Mail Size Limit....
Click to expand...
Click to collapse
He's right, I also cannot see this option in Froyo.
Sorry guys, i just checked Darkstones version and he does not have the settings that dan's RC1 release does. My apologies.
osrg said:
Sorry guys, i just checked Darkstones version and he does not have the settings that dan's RC1 release does. My apologies.
Click to expand...
Click to collapse
In the Sense version it's working fine, because that is a different e-Mail application (by HTC). But the original Android E-Mail application does not seem to have that option...
Using K9 as my default email, it is better and more responsive than the stock one but still cannot set the email size limit ...

MMS problems!

Whenever I receive a picture message from someone it comes out with extremely horrible quality. Its not there phones, there phones have 5mp cameras and I'm getting pictures that are pixalated really bad. I know I'm not gonna get 5mp quality messages but this horrible. Sending pictures quality is fine just receiving. Details in my sig. Anyone know an answer?
Sent from my Nexus One using XDA App
mms
hmm...
actually i cant send pic mesages with my hd2 running froyo, its the only thing that doesnt work, everything else runs to total perfection, mms has always been broken for me...
as far as receiving images though i dont recall having received one on my current rom. ill go try it..
http://forum.xda-developers.com/showthread.php?t=766241
worked for me
terminal 7 said:
hmm...
actually i cant send pic mesages with my hd2 running froyo, its the only thing that doesnt work, everything else runs to total perfection, mms has always been broken for me...
as far as receiving images though i dont recall having received one on my current rom. ill go try it..
Click to expand...
Click to collapse
Works fine for me, sometimes it will take a little while but it works. Pretty sure its the build your using. The one I use is bad ass except for this.
Sent from my Nexus One using XDA App
thatruth132 said:
http://forum.xda-developers.com/showthread.php?t=766241
worked for me
Click to expand...
Click to collapse
The link you posted really only addresses MMS send and receive issues relating to incorrect APN settings.
A fix for the compressed MMS issue is listed on Page 3 (Comment 25), but the instructions are only achievable if you have a Linux box. Plus you have to delete your old data.img and do a fresh install.
BetaBoy,
The poor quality MMS issue is discussed more in-depth on this thread.
http://forum.xda-developers.com/showthread.php?t=774672
The problem is only affecting Desire builds and is not an issue on the standalone Froyo builds.
Now there are two ways to fix the compressed MMS issue.
Option 1:
1. Download ES File Explorer from the market, install
2. Go to ./system/etc/ directory and look for a file called "mm_property.conf", open the file to edit.
3. Change the wapprofile=" to "http://www.htcmms.com.tw/Android/common/NexusOne/ua-profile.xml"
4. Save the changes
If that is too complicated, then the following option is for you! I went with option 2 because I am not proficient with file explorers and I couldn't figure out how to correctly access the system directory...
(Please note, with this method you have to delete your old data.img and do a fresh install)
Option 2:
Go to this thread and download the corrected data.img.
http://forum.xda-developers.com/showthread.php?t=774672
(Also note, Chiasoft has only corrected FroyoStone Sense V2 and Mattc Froyo Sense 1.7)
If you send him a PM, maybe he can put together a data.img for your setup.
And Betaboy, what the hell are you running 2.1 for anyway?
No need for any of that
The problem was fixed i just went into Messages>settings>Custom User Agent>Nokia N95
Problems Slved!
.BetaBoy said:
No need for any of that
The problem was fixed i just went into Messages>settings>Custom User Agent>Nokia N95
Problems Slved!
Click to expand...
Click to collapse
You aren't running the sense Build; Vanilla Android has different fixes. If it's a CM port, then you can modify the UA within the MMS app.
On another thought: Sense is "prettier" looking on that nice 4.3" display on the HD2 than stock Android, no matter how you theme it, imo.

[Q] Exchange email working with Sense builds only?

hi Guys, can't seem to find an answer to this and hoping someone would know...can you use exchange email with stock Froyo 2.2 or only with the Sense builds? Thanks for any advice.
OK, how should I say it....
The Sense exchange support is not as good as the native froyo support.
Why ?
Sense can only support one exchange server.
The vanilla Froyo part can support multiple exchange servers, in my case the companies exchange and my private zarafa.
So far, yes, stock froyo support exchange.
greets
dominic
Exchange
I have had it working on ALL builds I have tried (ShubCraft, Bangsters, HyperDroid, FryoStone to name a few) no problems from day one. I recommend getting touchdown from the market if you want to use it seriously, the options are way more advanced and user friendly, the widgets are also excellent. worth the £20.
I haven't had any trouble using Bangsters v1.2. Make are you clear out each entry before you fill in your account information. I found that when I simply completed an entry by adding to what was already three it wouldn't connect. If I cleared each entry and then typed my info into the blank, no troubles. Best of luck.
Sent from my HTC HD2 using XDA App
Ok thanks to all, sounds like I am good to go...but numbskull, seeing as you have tried all the builds, which one did you stick with? I am still on froystone V1 (v2 seems to have issues from what I can read) but am using LauncherPro so don't figure I need a Sense build (although, is the dialer different without Sense?). Heh, hijacking my own thread!
numbskull100 said:
I have had it working on ALL builds I have tried (ShubCraft, Bangsters, HyperDroid, FryoStone to name a few) no problems from day one. I recommend getting touchdown from the market if you want to use it seriously, the options are way more advanced and user friendly, the widgets are also excellent. worth the £20.
Click to expand...
Click to collapse
Mnemoch said:
Ok thanks to all, sounds like I am good to go...but numbskull, seeing as you have tried all the builds, which one did you stick with? I am still on froystone V1 (v2 seems to have issues from what I can read) but am using LauncherPro so don't figure I need a Sense build (although, is the dialer different without Sense?). Heh, hijacking my own thread!
Click to expand...
Click to collapse
I have finished on ShubCraft STOCK CM6, using ADW. no issues for over a weeks use now, enjoying it. But I am using the r10 kernel from michaprima, a good combo, not th one that comes with shubcraft.
Exchange works also without Sense!
Hi. Exchange works also without Sense! I tested it already on many BUILDS with and without Sense.

[Q] Question about swype beta

Hi, I just got my email to join the beta. I am using a build on my htc leo right now and when I goto download the installer apk, I click the link and it just goes right to download unsuccessful. Anyone else having this problem or had it?
I am not sure if this is cause of how I run android or if it's just cause I am using the phone data and not wifi (which they make a big deal about you using cause it's 10 megs)
Anyway if you got some information for me please let me know? Also for the admins, I know we can't post swype as it counts as pirated.
Ok I got the same email.. I thought my problem was the build.prob listing phone as hd2 so I changed it to ace.. Tried again fail.. Turned mobile browsing back on and it work!! Not sure which did it but it installed and licensed.. Hope that helps..
swyped from my HD2 Android
squish099 said:
Ok I got the same email.. I thought my problem was the build.prob listing phone as hd2 so I changed it to ace.. Tried again fail.. Turned mobile browsing back on and it work!! Not sure which did it but it installed and licensed.. Hope that helps..
swyped from my HD2 Android
Click to expand...
Click to collapse
How did you get it to change, just a simple eidt of the prob file? I assume you made the change and rebooted to get it working so it would then lable itself as a ace. Hmm, I shall try this. Thanks and any more info you can give me would be great, oddly enough I got into the beta with each of my emails I have used lo.
I assume you edited this line "ro.product.model=Nexus One" Mine currently says nexus one.
I currently use this build (http://forum.xda-developers.com/showthread.php?t=823471)
Yes that's the line I edited. In my desire hd build it said hd2.. I changed it to ace.. I believe you should be fine then. Make sure the browser is set to mobile browsing.. I thought it was a problem but I don't know for sure. Guess I can boot my desire build, and try there as I haven't changed the build prop on it..
swyped from my HD2 Android
squish099 said:
Yes that's the line I edited. In my desire hd build it said hd2.. I changed it to ace.. I believe you should be fine then. Make sure the browser is set to mobile browsing.. I thought it was a problem but I don't know for sure. Guess I can boot my desire build, and try there as I haven't changed the build prop on it..
swyped from my HD2 Android
Click to expand...
Click to collapse
Thanks, I am reloading my HD2 as we speak. Something I was working on more or less nuked my build. Oh well live and learn. But I will try seeing it to mobile once I get it back up and will post back to you. Thanks.
so booting my desire blue topia build launcher forced closed.. Fail.. Guess its shot.. And now swype doesnt swype on my blue topia hd build.. Wow!!
Edit: reset to touch input then back to swype now it swypes again..
swyped from my HD2 Android
How did you set it to mobile browsing?
In browser, menu, more, settings, make sure mobile browsing is checked
swyped from my HD2 Android
Odd, well it seems to want to work now.
So it works?
swyped from my HD2 Android
Aye, when I reloaded another build it just downloaded without any issues and installed fine. So now that I got the right apk file I am good now. I will just move it to my thumb drive should I load another build to test again.

Categories

Resources