yashsingh1/xdaforums huggingface dataset:
[Droid 2 Global General] mactherapy:
I have had 2 d2Gs running on the Telstra network in Australia for months, with no issues at all. They are both running Fission and they are absolutely rock solid, no GSM issues, no reboots, great battery life, nothing to complain about at all.

My GF just went to Canada with her D2G and put a Rogers sim card in it (same 850mhz 3G as Telstra) now she is having GSM issues and reboots.

When she was originally on Vodafone in Australia she put her old Vodafone sim in the D2G and had random reboots, after she got a brand new sim from Vodafone the issues went away.

Rogers either have a crappy network or a network that is in some way incompatible with this phone, or their sim cards are not fully compatible. It is not the phone as such it is the combination of Rogers and the phone.

I would expect that if you put another providers Sim in your phone it will suddenly become rock solid. I have heard that the sims designed for iPads work really well in the D2G, I am not sure how they differ from a standard sim, but a few people have found that just changing the sim will turn an unstable phone into a solid phone on the same carrier.

Good luck!

PS. I'm going to be in Canada soon and I will be roaming on the Rogers network with an Australian sim that works perfectly here, that will prove whether the issue is with the local network or the sim.
[Droid 2 Global General] leobg:
Phone works ok on 2G here (Canada). 3G is problematic. SIM card is hugely important. Newer sim cards are much better, but still far from "rock solid". I have tested the phone on two of the 3 (3G compatible) networks here. Telus and Rogers. There are different issues on both and it seems Telus works a bit better as in most cases phone just loses data and retains calling messaging abilities. On Rogers it usually loses connectivity completely. Rogers has 2G and 3G/3G+ network on 850 and 1900 MHz. Telus is 3G only on the same frequencies. Interestingly, when bug occurs on Telus, phone believes it is on GSM (2G) while this is clearly not possible as Telus does not have 2G network at all.

I had the phone in Europe (Bulgaria) for about a month in Jun/Jul. Same issues while on 3G there too. Hence I used the phone on 2G mostly. On 2G phone could be called "rock solid" (and battery lasts 3x longer btw!)

I was hoping new firmware update will provide baseband fixes, since it stated "improved connectivity on networks in Europe and Asia", but we are yet to see the update.

I am moving to XT860 4G as soon as I figure out how to purchase one without having to change my provider. If this phone is as stable as my Milestone 1 I'll be quite happy.

D2G will go on standby for when I travel Stateside.

I strongly suspect the operator ban is the utterly buggy thing in the baseband.
[Droid 2 Global General] seventieslord:
let me know when you do.
[Droid 2 Global General] mactherapy:
I'm on 310hrs uptime, the only reason I am not over 1000 is because I tried one of the recent CM7 builds. I use a bluetooth car kit every day and a bluetooth headset once a week. I make and receive an average of 30 calls every day. I use around 1GB of internet data per month, mostly just surfing the net, watching videos, uploading photos and email data. I consider myself a heavy user of the phone and I trust this phone, it is better than the Galaxy S I had before it and better than the G1 before that.

I am puzzled and saddened to hear that other people are having a bad time with their phones, I can only assume that it is related to the software/firmware/hardware combinations that you have.

I have proved that I can turn my stable, reliable phone into an unstable phone JUST by swapping the SIM card. On the Telstra network (3G 850Mhz) it is rock solid, coverage is as good as any other phone I have ever owned, possibly even better. With an Optus card in the phone (2100Mhz 3G) the coverage is worse and the phone is flaky with random crashes and reboots.

I think people who have suggested that it has something to do with the way that the Baseband version has been crippled by Verizon are probably on the right track.

Just for comparison here are my specs:

Fission Rom

System Version Fission_2.4.3

Model Number DROID2 GLOBAL

Android Version 2.2

Baseband Version N_01.48.05R

Kernel Version 2.6.32.9-g9e2c63d xrpk47@il93lnxdroid25 #1

Build Number Fission_2.4.3

I'm interested to know which versions of the Baseband other people are running and whether that relates to the stability of the phone. Is it possible to change the baseband version? I don't remember seeing any images..
[Droid 2 Global General] Gasai Yuno:
You cannot change the baseband firmware. It's signed.

And there are, iirc, two versions; one from 2.4.29 and one from 2.4.330.
[Droid 2 Global General] leobg:
Your baseband is from 2.4.330. And you are on fission which is 2.4.29. I am somewhat surprised yours is not acting up. Since I noticed what a big difference SIM card makes, your positive experience with Telstra is likely to the fact phone "likes" the sim.

I got bored of waiting for GB update and flashed CM7 yesterday. So far I am happy overal (using the wired headset in the car unfortunately). Missing Blur dialer/contacts and social networking widget. But 1/2 of the apps I used before are now unnecessary and uninstalled (like profiles, circle battery, touchdown exchange - so far push is fine (knock on wood)) and few others. I am using microsim (as this way I know I am using a late model sim), it has been acting up much less than my 2 year old sim before that. Yet to act up on CM7...

Oh, and CM fixes the signal indicator (finally seeing more than one bar signal - usually 4 bars now :)

Battery life doesn't look very promising compared to before, but I think it is too early to judge. Will be giving it a try.
[Droid 2 Global General] hgrimberg:
If you think the operator ban is the reason for the unstable signal, why don't you try the radiocomm hack from cellzealot that releases the ban for other american gsm carriers?
[Droid 2 Global General] leobg:
Turns out banned or un-banned it doesn't make difference. So that theory is shot.
[Droid 2 Global General] mactherapy:
Ok, I am in Canada with my D2G. I still have the Australian Telstra Sim in the phone and it is roaming on the Can Rogers Wireless Network. The phone has 120hrs of uptime and not a glitch since I have been here. I am moving around from WIFI and back to 3G with no issues at all, it works great. Coverage is excellent, I have been out in the hills and even though there were no bars showing I was able to get a use-able signal and send texts and surf the net, I actually got coverage in places that locals on the rogers network with other phones did not!

My GF has been out here for months with her D2G using a Rogers SIM, she has found that she had random reboots and it would often happen when switching from WIFI back to 3G, otherwise coverage wise she has found it to be good.

I have been running Gingerbread since 606 was first leaked, I have been on 607 since that became available. I updated my GF to 607 when I arrived here and so far she has had no issues with her phone.

I still think most issues people are having are possibly hardware related, so either something in the phone itself or a bad or incompatible SIM card.

Or software related. I have managed to make my phone unstable by installing zips and somehow corrupting the firmware on the phone.

The only way to be sure you have good software on your phone is to SBF the phone back to stock and this seems to cure most peoples issues.
[Galaxy S I9000 Q&A, Help & Troubleshooting] monkeytennis:
Hi,I am looking for the easiest way to add voodoo sound and video to my phone and keep seeing stock + voodoo.where is this?Cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] DMD9:
Here you go...

http://dl.project-voodoo.org/

Don't think video is included anymore though.
[Galaxy S I9000 Q&A, Help & Troubleshooting] monkeytennis:
So what hacks does it contain?cwm ect?
[Galaxy S I9000 Q&A, Help & Troubleshooting] DMD9:
CWM, lagfix and .ext4 with voodoo control plus, no bug with front facing camera...
[XPERIA X10 General] shedrule:
Hi I've just purchased new comp with Windows 7 Ultimate 64bit. I have used it to flash basebands and roms but when I go to root this option is greyed out, I am using the latest flashtool. Can anyone help please.
[XPERIA X10 General] ImS0Raw:
Turn on usb-debugging on your phone?
[XPERIA X10 General] shedrule:
I'm not home at the moment, never thought of that, I'll try later and let you know, thanks alot.
[XPERIA X10 General] shedrule:
Thanks PlayGunsta, what a plonker I feel, I've been using xrecovery that much I forgot the basics, thanks again all rooting fine. :)
[XPERIA X10 General] ImS0Raw:
No problem, have fun!
[XPERIA X10 General] melody8801:
:) that could happen...

i broke my X10 yesterday, and then i had the same problem...

i needed to reflash the original firmware of Sony and then reroot it again...
[Android Software/Hacking General [Developers Only]] bbbird1:
Hi all,

I'm trying to root my HTC Desire HD using ginger, and it works fine, except for the fact that when I try to copy my suid root shell to /system it lasts only after the first reboot. Apparently the bootloader (i think...) is erasing any unknown file... Do you know why? And who's doing that? Is there a way to keep my root shell without flashing the phone?

Thanx a lot!
[Milestone XT720 General] mchlbenner:
Hi Guy this the deal are xt720 bootloader 8089 and the leaked bootloader 8090 don't flash this and no link yet I don't want you to brick your phone.

I will sweeking developers help with this one I will soon flash this on one extra phones if I get good info.
[Milestone XT720 General] Mioze7Ae:
If you're committed to doing this please coordinate with #milestone-modding developers. Please read the logs very carefully, this does not seem to be an easy thing to do. They were writing and compiling custom programs to flash and verify the flash as they went. If/when the phone bricks, you want to be able to know that it bricked because the bootloader doesn't work (i.e. you want to rule out the possibility that you didn't make a mistake doing the flash). Also, from the logs it looks like there are many incorrect dumps of the XT701 bootloader.

Have you thought about how you might try to convince us to follow in your footsteps if you were to succeed?

Edit: sorry, didn't mean to call you names, poor wording
[Milestone XT720 General] Knoedelkopf:
can someone explain what he means exactly ?

does he know to crack bootloader of xt701 or what ? i don't get it :D
[Milestone XT720 General] Knoedelkopf:
http://www.mod2xtreme.com/showthread.php?t=8720

hmm our bootloader is 8089 right ? so it's gonna be impossible with the leaked bootloader of xt701 ? cause just

BL_8090_umts_stcu_Consumer_replacer.sbf

BL_8091_umts_stcu_Consumer_replacer.sbf

BL_8094_umts_stcu_Consumer_replacer.sbf

are leaked.. ??:confused::(
[Milestone XT720 General] fjfalcon:
Will do try tommorow on broken xt720.

Will se... will it work.. or i get breaked on it.
[Milestone XT720 General] Knoedelkopf:
what is the worst thing that could happen by trying to unlock the bootloader with those files?

irreparable software damage?

or could we just flash original rom back if something goes wrong?
[Milestone XT720 General] Mioze7Ae:
The bootloader is the software that runs on the phone to receive and flash the sbf. If that stops working... you can't flash any sbf.

A whole crew tried flashing the XT720 bootloader onto an A853 middle of last nov and ended up with a brick. See http://milestone.bekaakut.de/index.php?date=2010-11-16 starting around 20:00.
[Milestone XT720 General] Knoedelkopf:
those guys seem to have bricked their phones right? so no chance with these xt701 bootloader unlockers ?
[Milestone XT720 General] mchlbenner:
Unttil this has been test for work or not don't flash those ABC's okay you get a brick for your trouble.
[Milestone XT720 General] fjfalcon:
critical error \n febe \n 0047

pacient just rebooted to android... =)
[Milestone XT720 General] Mioze7Ae:
So the sbf simply errored and didn't apply? Did you flash the CG32 or the CG30? I think CG30 is the right one, but you mentioned CG32 on #mm. Did you use sbf_flash or RSD Lite? And which bootloader version did you try?

I wonder if the cdt.bin table records the locations of the signatures? Since the XT701 bootloader seems to be smaller than the XT720, we may have to pad more FF's in there to get the signature to the correct location? But I don't know if the trailing FF's are included when computing the signature, so that may invalidate the signature... hmmm.
[Milestone XT720 General] fjfalcon:
I'am have tryed 80.90.

Tryed to flash cg30, cg32.

Now will try to do so for cg30 only.

Second error was:

critical error \n DEA1

Will make third attemp to cg30 only now.

RSD lite was used...

cg30 don't flash at all - said to small size.

phone alive.. so new attemps tommorow.

Mioze7Ae, thanks for pm's - will try to improve.
[Milestone XT720 General] fjfalcon:
./sbf_flash ../other/BL_8090_hack.sbf

SBF FLASH 1.11 (mbm)

=== BL_8090_hack.sbf ===

00: RDL03 0x82000000-0x8204CFFF 9571 AP

01: CG30 0xB0020000-0xB005FFFF 20ED AP

02: CG32 0xB0160000-0xB017FFFF 2151 AP

Milestone found.

>> uploading RDL03

Uploading: 100% OK

>> verifying ramloader

-- OK

>> executing ramloader

!! unexpected response

--(9) [02]ACK[1e]JUMP

RX(9) [02]ERR[1e]G[03]08

!! failed

>> rebooting

Thats an error.

I think we should prepare ramloader for it...
[Milestone XT720 General] Mioze7Ae:
Did it survive for another attempt? Was the bootloader modified at all?
[Milestone XT720 General] fjfalcon:
Youp, it still alive.

Bootloader 80.89.. still..
[Milestone XT720 General] mchlbenner:
Great work were are getting close any modification bootloader sbf give link wensday I can flash them I have also download different roms to try.
[Milestone XT720 General] fjfalcon:
Tryed to read img as smg.. get nothing..(RLD img don't found) But i had some headeache so must be that a reason.

Using SBF_RECALC for that process.
[Galaxy S II Q&A, Help & Troubleshooting] jodeltje:
I was just standing outiside and noticed that I couldn't read the screen of my new Galaxy S2 which I never noticed on my Nexus S. So I compared the two in direct sunlight.

Isn't the sAMOLED+ supposed to be brighter than the original sAMOLED screen?

Is my screen less bright than other sAMOLED+ screens?
[Galaxy S II Q&A, Help & Troubleshooting] Elvoski:
My Galaxy S 2 is definatly brighter in sunlight than my Nexus S.

although i have turned off my auto brightness and whacked it right up on both..
[Galaxy S II Q&A, Help & Troubleshooting] dan13l:
At brightness zero the nexus s is brighter than the galaxy s 2.

I noticed that in bright sunlight, I can't see the screen at all on my SGSG2 with it set to zero, which causes a bit of a problem upping the brightness! On the Nexus, I could see well enough to change it.

I think at full brightness though, the SGS2 is brighter. My retinas haven't recovered from accidentally setting 100% whilst reading at night.
[Galaxy S II Q&A, Help & Troubleshooting] LawAce:
I've been wondering whether there is a way to boost the brightness, I was going to make a topic about it.

Some reviews I've seen say they had to turn the screen down to lowest brightness as the screen is so bright, etc. however my screen is nothing special in terms of brightness really and I have it on full, with auto adjust off :confused: colours are good though.
[Galaxy S II Q&A, Help & Troubleshooting] jonny_ftm:
Yes, disable auto brightness maybe
[Galaxy S II Q&A, Help & Troubleshooting] jodeltje:
yes, I did that. the pictures are taken with both screens on 100%

I guess my screen is just not as bright as others :/
[Galaxy S II Q&A, Help & Troubleshooting] BlueScreenJunky:
Also, under Settings -> Display, make sure that "Auto Adjust Screen power" is disabled... this option tries to save some battery by lowering the brightness when the image displayed is brighter : It can be useful in movies but it's just useless and annoying when you're browsing or reading.

PS : And SuperAMOLED+ is not supposed to be brighter than sAMOLED, it's the same without the pentile matrix. When samsung announced an improvement in battery life and brightness they were still comparing it to LCD screens from a few years ago.
[Galaxy S II Q&A, Help & Troubleshooting] jodeltje:
thanks bluescreenjunkie, that setting actually helped (a bit). :D

and yes, your probably right about samsungs claims as well, I probably subconsciously interpreted samsungs claims the best way possible ... (so I had a reason to go buy it).

thanks for your input.
[Galaxy S II Q&A, Help & Troubleshooting] SquirtingCherry:
well it is possible to increase the brightness but it takes some development, like supercurrio did for the 2.3.3 kernel for the nexus s and cm7 sgs1 kernel with the voodoo app.

Dont know if hes gonna do the same for the sgs2, i really like it on my sgs1 for sure.
[Galaxy S II Q&A, Help & Troubleshooting] jodeltje:
he increased the brightness? well that explaines it then (as it's running a voodoo kernel) :).
[Defy Android Development] lny:
Hi,

I'm running cyanogenmod beta6 and my device randomly reboots.

So, I piped logcat in a txt and the last lines were:

E/k9 ( 2491):	at com.fsck.k9.mail.store.ImapStore$ImapFolderPusher.internalOpen(ImapStore.java:2975)
E/k9 ( 2491):	at com.fsck.k9.mail.store.ImapStore$ImapFolderPusher$1.run(ImapStore.java:3058)
E/k9 ( 2491):	at java.lang.Thread.run(Thread.java:1019)
E/k9 ( 2491): Caused by: java.net.SocketException: Host is unresolved: imap.gmail.com
E/k9 ( 2491):	at java.net.Socket.connect(Socket.java:966)
E/k9 ( 2491):	at com.fsck.k9.mail.store.ImapStore$ImapConnection.open(ImapStore.java:2344)
E/k9 ( 2491):	at com.fsck.k9.mail.store.ImapStore$ImapFolder.getPrefixedName(ImapStore.java:675)
E/k9 ( 2491):	... 5 more
D/panic_daemon( 1866): bp panic!
D/panic_daemon( 1866): ACM device enumerated!

k9 mail was the last action before panic (btw. what is bp?). Does this means that k9 is the problem?

thx

Lenny
[Epic 4G Q&A, Help & Troubleshooting] pathare:
Ive had this problem with multiple ROMs after a week or two using a ROM when the phone boots up everything starts to force close. Including google frameworks. does anyone know what might be causing this? Its happened with Simply AOSP V3.1.1 and syndicate 1.1.0 fully loaded. My phone is currently rooted on EC05 the only ROM that it hasnt started happening on is BlazeROM V2. I always flash back to that and have no problems.
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Are you pulling the battery without waiting for full shutdown after vibe? This will cause fcs on ROMs that have journaling off. Check your ROM for how to turn journaling on because it is different for some ROMs and try it. To be safe clear all your data and Dalvik cache. You can go. Into manage applications and clear data for apps that are still fc'ing.

Do you BONSAI?
[Epic 4G Q&A, Help & Troubleshooting] pathare:
Thats definitely it, I have a second battery and I dont always wait for it to vibrate after shutting it down to change it. So is that something that I HAVE to do? or can I do something with the journaling you were talking about? what is journaling?
[Epic 4G Q&A, Help & Troubleshooting] chris41g:
Use my zip in the dev section, it will turn journaling on for any ext4 rom...
[Epic 4G Q&A, Help & Troubleshooting] pathare:
I found your post, thank you! can you tell me what journaling does exactly though?
[Epic 4G Q&A, Help & Troubleshooting] ZiggSVO:
http://en.wikipedia.org/wiki/Journaling_file_system

what I gather from journaling is that it makes sure that if files are modified (a setting is changed, etc.), if it gets interrupted while the file is being modified (like if you pull your battery it gets a hard reboot), the file won't get corrupted. keeps the file in like a cache until the change is finalized. Having journaling enabled makes the device a bit less responsive (because it is managing this cache) but protects against corruption in case your phone reboots unexpectedly.

good example would be video games: how it tells you if you see this symbol, don't power off your system until it is gone or your save file could become corrupted.
[Epic 4G Q&A, Help & Troubleshooting] chris41g:
There are 3 types of journaling in ext file systems, journal, writeback and ordered. Basically all write entries are written to the journal first in journal mode then to the disk and the journal is replay in the case of a crash making data and metadata current. In writeback mode only metadata is stored in the journal then data to the disk, and can result in old data in case of a crash but no corruption, in ordered mode it writes the data to the disk first, then journals metadata but keeps track of the grouping in "transactions". This is the default mode, and the most efficient and safest. Slightly slower than writeback, much faster than journal. Will result in current data and no corruption on a journal replay.
[Epic 4G Q&A, Help & Troubleshooting] abqdavid:
Can you post the link to the post your referring to? Im having the same problem, however I don't get where to go? Where is the "Dev" section?
[Epic 4G Q&A, Help & Troubleshooting] pathare:
http://xdaforums.com/showthread.php?t=1071723

So will enabling the journaling from your link put the phone in journal mode or ordered mode?

and would I just save the zip to my SD and run it from recovery mode?
[Epic 4G Q&A, Help & Troubleshooting] chris41g:
Ordered on system and data, and writeback on cache
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Do what the man says. Since I turned journaling on I never get FCs. Still good practice to wait for the vibe to change batteries.
[Epic 4G Q&A, Help & Troubleshooting] reinaldistic:
i had this problem with a battery i bought online not providing stable enogh power to the device, do you have a non official battery?
[Epic 4G Q&A, Help & Troubleshooting] jonnoh:
Same Here...

I have had similar issues but it is a bit different on AOSP than Syndicate. After a few weeks or when the phone gets too hot, I will get the continous Force Close messages on Syndicate. I have not yet seen that on AOSP, but do get the Force Close errors when an app needs to scan the SD card. After using these two ROMS I really dont want to go back to stock but am considering doing so...
[Epic 4G Q&A, Help & Troubleshooting] silver03wrx:
Turn on journaling
[Epic 4G Q&A, Help & Troubleshooting] JohnCorleone:
This could be one of those "all of our Epics are different" things. If I run a ROM with no journaling, even if I add nothing or change nothing, I start getting force closes after day 4 or 5 every time. I can't figure out why and I prefer not to have Titanium make a nightly backup so I run journal on and don't get force closes anymore at all. Maybe if you wipe re-flash and enable journal you won't have the issues anymore
[Epic 4G Q&A, Help & Troubleshooting] tazfanatic:
http://xdaforums.com/showthread.php?t=1071723

Use the files in this link to enable or disable journaling save to sdcard and flash from cwm all set

I count on my phone and can not be constantly reflashing so I enable it so no more issues.
[Desire Q&A, Help & Troubleshooting] TopGear63z:
Yesterday when i had updated my rom, i turned my phone on, the problem already started 1st thing that showed up was saying that i have to force close com.htc.bg and immediatley after com.htc.bgp:S, i'm not able to go in weather and in the settings(accounts&sync) i can't enter facebook to delete it. It give me a FC message and goes back to the homescreen, even while playing games this happens? Any solution without a full wipe, have a lot of apps, it takes years to backup and restore... only if i have to i will..

any help?

BTW: rom is InsterCoin v33, v32 had no problems;)
[Desire Q&A, Help & Troubleshooting] TheGhost1233:
Wipe dalvik cache (and reflash the rom whiteout wipe). Might help.
[Desire Q&A, Help & Troubleshooting] TopGear63z:
thanks but i've already tried it;) no change only difference that the .bgp FC dissappeared but .bg stayed
[Desire Q&A, Help & Troubleshooting] TopGear63z:
nevermind solved my problem:)