yashsingh1/xdaforums huggingface dataset:
[Streak 5 General] Thremix:
Nothing huh?
[Streak 5 General] eSZee:
Yeah, setcpu can overclock it to 1.2 or so. otterbox defender if you want a beltclip, commuter if you don't.

Posted with StreakZilla, using XDA App.
[Streak 5 General] andrewmcd11:
I'm thinking of purchasing a Streak as well.

I'm curious, how many of you have had to get a replacement device from Dell? What were the reasons for this? Should I expect the same?

Thanks for the help.
[Streak 5 General] ajairola:
The GPS on the Streak is very good, Not sure why people complain about the battery life as I have no problem with it, also I recommend the Otterbox Commuter. The screen is not as fragile as It's made out to be, also the unresponsiveness that people have is usually fixed by recalibrating the screen after installing a new Rom(I have the streak in my pocket all day and never have the problem). Finally the Streak seems to be a difficult device to consistently manufacture properly, so you may have to get a replacement due to something being defective, but in my opinion it is worth it because it is a great phone.
[Streak 5 General] Thremix:
the only real problem I see now, is the fact that DELL makes the phone... lol I HATE talking to people from india!! If DELL were to just change that, they could be a great company again....

I'll get that 4800mah battery if I keep the phone... I just wish we had more devolpment.... So how much "better is the CPU in the HTC inspire than the streak?" is just just better on battery? I know that it can be OC to 1.8GHZ but since you cant add a big battery, thats just dumb...
[Streak 5 General] ajairola:
Dell's Mobility(Cell phone) Support isn't in India. Also the processor in the Inspire should be more efficient due to its smaller architecture and should handle graphics better as it has a better GPU (the Adreno 205 vs. the 200). As for real world performance differences I have no idea. Personally I've never had an issue with processor power on my Streak, also I've found on mobile devices that it is the amount of free Ram that matters more than processing power.
[Streak 5 General] eSZee:
Dell mobility does have a dept. in india. I' ve dealt with them 4 times but only once got a non indian person.

Posted with StreakZilla, using XDA App.
[HD Mini General] ninnitto:
why all the times i get off the battery from the device the clock is wrong??
[HD Mini General] kio4961:
Dear Friend

hd mini Like other mobile devices at the without main battery needed energy source to keeping live time. a small battery inside the phone is enabled this task and maybe in your phone this battery is low or damage but not worry because the task of this battery just was keeping living time and Nothing else.
[Droid Incredible Q&A, Help & Troubleshooting] bradsinram:
I've noticed a huge difference in the volume on headphones and earbuds on our phones compared to ipods. The ipod is Soooo much louder!! I read somewhere that it was determined by the kernel or is it just hardware capabilities? Is there some way to make it as loud?
[Droid Incredible Q&A, Help & Troubleshooting] k_nivesout:
I have seen an audio boost kernel around, a quick search should turn it up.
[Droid Incredible Q&A, Help & Troubleshooting] watt9493:
Power amp?

I propose a toast to the 21st century.
[Droid Incredible Q&A, Help & Troubleshooting] bradsinram:
Would it be compatible with warm z though?
[Droid Incredible Q&A, Help & Troubleshooting] k_nivesout:
Not sure, I don't remember if its a sense or aosp kernel..
[Droid Incredible Q&A, Help & Troubleshooting] dyetheskin:
I'm interested as well...poweramp only does so much until the amplification starts interfering
[General Questions and Answers] bburd:
I'm trying to use command line tools to develop an Android app. I'm calling aapt as follows:

"C:\Program Files (x86)\Android\android-sdk\platform-tools\aapt.exe" package -f --debug-mode -M C:\MyProjects\MyAndroidProject\AndroidManifest.xml -S C:\MyProjects\MyAndroidProject\res -I "C:\Program Files (x86)\Android\android-sdk\platforms\android-9\android.jar" -F C:\MyProjects\MyAndroidProject\bin\MyActivity-debug-unaligned.apk

I assume that, because I've specified --debug-mode, aapt will attach a debug certificate, making my app runnable on an emulator. But I keep getting the message

Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]

How can I diagnose the problem?
[Omnia 7 General] sotong:
Looks like you got the Samsung error code. Try the following steps in the attached link; should help you out :)

http://wmpoweruser.com/samsung-releases-801812c1-update-error-fix-for-the-samsung-omnia-7/
[Omnia 7 General] GTI WR6:
what is your bootloader version?
[Omnia 7 General] KraFT_mk:
Its neither of that.

- If using update from Zune - the phone cant reboot on page 6 of 10.

- The update zune error code is because I have to disconnect the USB cable – reboot and connect again.

- If using Samsung update tool – Cant get the phone in DL mode.

- Bootloader ver. 4.10.1.9 (see first post)

This will be ugly.

K
[Omnia 7 General] jhughesy:
Bootloader ver. 4.10.1.9. Same problem. Used option B to update to Nodo. Tried using Samsung Tool but download mode wont come up.

Called Samsung service centre as per advise on the Samsung Update tool but they told me nothing they can do and to call Microsoft. Meh!
[Omnia 7 General] VoodooKing:
Unable to update even after using Samsung Tool. Phone keeps rebooting at Samsung Omnia 7 logo.

OS Version: 7.0.7390.0

Firmware revision number: 2424.10.11.1

Hardware revision number: 3.15.0.4

Radio software revision: 2424.10.11.1

Radio hardware version: 0.0.0.800

Bootloader version: 4.11.0.3

Chip SOC version: 0.36.2.0
[Omnia 7 General] Tony.Montana.:
Try this guide

http://windowsteamblog.com/windows_...spx?utm_source=twitterfeed&utm_medium=twitter
[Omnia 7 General] VoodooKing:
I came from there. Doesn't work for me. Samsung still having issues...
[Omnia 7 General] Tony.Montana.:
sorry about that...It worked for me :(
[Omnia 7 General] Freypal:
wow... just wow....

I have said 4.10.1.9 bootloader version. I did nothing wrong, i updated my phone when prompted by official means and MS response is to call samsung support?

That is frankly not on. I am really angry about this, I have been such a strong supporter of MS and their products. I have Windows on my PC, I've had both XBox console and had windows mobile and now windows phone. I feel so let down by this, what a load of crap.
[Omnia 7 General] newfla:
Same bootloader, successfully updated from 7008 only with zune
[Omnia 7 General] andreabarbera:
I have bootloader 4.10.1.9, and I managed to update my phone by putting the phone in download mode using the trick as described in this video: http://youtu.be/D0aoabVtPJ8

As an alternative, you could use a usb jig, the same ones that can be used for Samsung Galaxy S.

By putting the phone in download mode, you can install the Samsung patch. After that I had no problems installing the 7392 update through the Zune client.
[Omnia 7 General] PubERB:
Omnia 7 8Gb unlocked from factory.

My configuration was:

OS Version: 7.0.7008.0 (updated from 7004 removing the mobileOperator ID into the registry)

Firmware revision number: 2424.10.10.6

Hardware revision number: 3.15.0.4

Radio software revision: 2424.10.10.6

Radio hardware version: 0.0.0.800

Bootloader version: 4.10.1.9

Chip SOC version: 0.36.2.0

I did the trick of hungarian vpn to update to 7390, but in one week I restored to 7008 version again due to warning of Microsoft about unofficial updates.

Now I have 7.0.7392.0 using Zune normal update. No problems at all updating.

Very happy after long waiting. :D
[Omnia 7 General] GTI WR6:
I have bootloader version 4.10.1.9 and I updated from NoDo to 4392 using Zune. Did not need to use the Samsung tool. My phone is a T-Mobile UK unlocked.
[Omnia 7 General] s7yler:
Successfully updated from 7008 to 7392 only with Zune, all steps went fine.

My configuration now:

Samsung Omnia 7 16GB unbranded from Germany

OS Version: 7.0.7392.0 (before it was 7008)

Firmware revision number: 2424.10.11.1

Hardware revision number: 3.15.0.4

Radio software revision: 2424.10.11.1

Radio hardware version: 0.0.0.800

Bootloader version: 4.11.0.3

Chip SOC version: 0.36.2.0
[Omnia 7 General] yovaman:
The same problem here, unbranded Omnia 7

Updated to NODO with the wifi trick.

Bootloader version: 4.10.1.9

Can't get the phone in Download Mode.

Samsung...never again, the last phone from this OEM I buy.
[Omnia 7 General] frblckstr1:
And another:

Unbranded Omnia 7

Updated to NoDo with the 'pull network cable after 3 seconds' trick.

Bootloader version: 4.10.1.9

Can't get the phone in Download Mode.

Last thing to try is the trick with the 3 resitors and the USB port to get it into download mode (first need to find me the 100 ohm resistors)

Also considering not to buy another Samsung... but I do like the display!
[Omnia 7 General] DAVIZINHO:
Hello,

I have a debranded omnia 7

botloader: 4.10.1.5

firmware pda: JJ5

firmware phone: JJ3

nodo update throught zune desconect method

yesterday i try to update from nodo to 7392 and its imposible. allways stop in steep 6, during the reboot of the phone.

I apply samsung patch and the i can update to 7392 in the first atemp.
[Omnia 7 General] florinr08:
Unsuccessful after patch

I used the Samsung tool before even trying the 7392 update from 7390. After that, I tried updating but I'm getting the endless boot loop. :( I don't even know if it would have worked without the patch. I'm debating whether I should call Samsung up and see what solutions they've got for me, but I'm not sending my phone in if that's what they'll request! -.-
[Omnia 7 General] florinr08:
Samsung response

They suck! They said to contact Microsoft because it has nothing to do with them since the phone isn't able to connect with the Zune software or something..... I don't think she understood that it all works fine and dandy up until the phone needs to reboot and it just loops over and over again without even getting to the update screen... -.- Which, to me sounds like it's their problem since they need to be able to get the phone to boot up into the update mode screen (whatever the name for it is again...).

I never intended to have anything to do with Samsung because I knew how I hated their phones and designs (although the Omnia 7 is exempt from the design statement) but that's the only Windows Phone that Three UK offered!! :/
[Omnia 7 General] ManGastaS:
I have the same problem guys, Im stck with samsung omnia7 logo and I can't get to download mode! GRRRR this sucks
[Omnia 7 General] Freypal:
First Samsung phone i've ever owned. It will also be the last. Regardless of how nice the screen may be there have been far too many problems already with this device and i've only had it 6 months.

How can a company be that incompetent? The same thing happening previously on Android devices.

Can't wait for the Nokia handsets to arrive.
[Omnia 7 General] florinr08:
Same here! :/
[Omnia 7 General] xdamir:
Here is the link to the fix for this problem.

http://support.microsoft.com/kb/2547687
[Omnia 7 General] frblckstr1:
That does not help for us that can't get into download mode via the camera+volume up buttons.
[Omnia 7 General] Freypal:
I tried ringing Samsung as per the KB article as i have the bootloader that cannot enter download mode and Samsung deny any resposibility and that it is MS fault.

This is appalling service from Samsung. So annoying.
[Omnia 7 General] KraFT_mk:
There are hundreds posts on different blogs and forums created by Omnia 7 users explaining that their phones CANT GO IN DL MODE. All fixes for those O7 users are useless at this point.

K
[Omnia 7 General] giobooo:
Ok, this may be the solution to the endless boot but i can't assure anything. What happened to me was that my phone got disconnected during Download mode and i was taken to the endless boot. After some trial and error what i did was pulling out the battery and than putting it back on while keeping down the power button. This broke the endless boot and booted my phone without any problem.

I hope this helps but i really can't assure anything since i can enter in download mode and i have the 4.11.0.3 bootloader.

If this was a known solution then just ignore it! :D

Good luck!
[Omnia 7 General] Freypal:
The only option I can see is a recall of affected handsets. Users cannot be expected to Jig their own phones. Then again for this to happen first Samsung are going to have to acknowledge the problem.
[Omnia 7 General] florinr08:
That is what I did... I hadn't tried the update before applying the patch so I don't know if I should have applied it or not, but now whenever I try updating my phone to 7392 I get an endless boot loop at Zune's step 6 in the update process...
[Omnia 7 General] simdao:
No problem upgrade from 7008 to 7392 in OSX

ROM: BSE I8700BSEJK1
[Omnia 7 General] Forzahibs:
Not had this update yet :confused:
[Omnia 7 General] VoodooKing:
Thanks but 7008 to 7392 works fine.

It's 7390 to 7392 that is having a problem.
[Omnia 7 General] VonCrisp:
Guys don't even bother explaining to Samsung support that the update doesn't work. Their objective is to deny responsibility.

What they will do is flash your firmware at any offical Samsung service points... For free. This will fix the issue.
[Omnia 7 General] evolutionqy7:
Well hence why this is my last Samsung phone. Ive got tempted by the screen and hardware (which they have the best out there)

But seriously software and support wise Sammy is ****. I had a bad perception of them for a long time over previous purchases years ago. I took the dive to find that nothing has changed.

Ive had battery problems with my Omnia 7. They were meant to send me out a new battery 2 months ago. Still nothing. Just went of and bought a new one myself on ebay.

Bought a new Factory Sim Free Galaxy S for my gf and that wouldnt work with our network as well.

So balls to u sammy. Aint getting any more of my money.
[Omnia 7 General] bmazloum:
Unable to upgrade as well.

Can't get into Boot Loader.

Going to order/make a USB JIG since I'm not in the same country as where I bought the phone from. Hopefully that will fix it. If not, I hope Mango update works fine.

F'in Samsung. If only HTC made an attractive phone with WP7.
[Omnia 7 General] Thunder_:
I got the same issue (Hang at step 6) but this fix did the trick for me. Can you get to download mode following the steps?
[Omnia 7 General] florinr08:
Yes, my phone can get to download mode and I've tried applying Samsung's patch but that's what happens after the patch... :/
[Omnia 7 General] oomniia7:
Guys my phone still doesnt show update available but I have a question:

when I hold volume up + camera + power button, my phone turns on and shows me image of "mobile-usb cable - pc"...

Does that mean that my phone CAN enter download mode and that I am safe when update is finally available for me ?

I am aksing this because mine is version 4.10.1.9 and I see that is THE problematic version ??? Now I am confused.. how am I able to enter DL mode :S

Phone: Samsung Omnia 7

OS version: 7.0.7004.0

Firmware revision number: 2424.10.10.6

Hardware revision number: 3.15.0.4

Radio software version: 2424.10.10.6

Radio hardware version: 0.0.0.800

Bootloader version: 4.10.1.9

Chip SOC version: 0.36.2.0
[Omnia 7 General] madonion:
^ No, you have the faulty bootloader. Download mode is a yellow triangle with an exclamation mark in it.
[Omnia 7 General] oomniia7:
dammit >.<

I've read on WindowsPhone Blog that they are resuming updates for Omnia7, does that mean they've fixed this or ? :S

I have bought omnia7 2 days ago so I am new in this..
[Omnia 7 General] Freypal:
Unfortunantly not. They are resuming the update but anyone with bootloader 4.10.1.9 is stuffed, myself included! Without being jigged the phone cannot be updated.
[Omnia 7 General] KraFT_mk:
UPDATE:

If you want to update with USB-JIG I created this simple guide.

USB-JIG for Samsung OMNIA 7 - Correct instructions! Quick and very SIMPLE guide !
[Omnia 7 General] xDomsx:
As far as I see it, unsuccessful updates are only those from 7.0.7390 to 7.0.7392.

If you haven't forced update and you're updating from 7.0.7008 you should be fine.

Please correct me if I'm wrong...
[Omnia 7 General] Freypal:
It's not just forced updates. I updated to 7390 when prompted by Orange and it's given me the faulty bootloader.
[Omnia 7 General] br_other:
I think that's the Download mode for 4.10.1.9

The forum doesn't allowes me to post link, therefore copy and paste the link below:

byteex.com/upmod1.jpg
[Omnia 7 General] oomniia7:
Yup thats the picture I get, but it seems that is not the download mode ?
[Omnia 7 General] Freypal:
It's not download mode. The only way to access download mode appears to be by jigging the phone. It's very simple to do. The guide is on here and the resistors only cost me 48 pence!
[Omnia 7 General] spt1234:
Updated my Omnia with T-mobile branding in germany just right now and i had the faulty bootloader 4.10.1.9

EVERYTHING WENT WELL! No problem, i m now in 7392 and got a new firmware and bootloader as well! Niiiiiice :)
[Omnia 7 General] Freypal:
Hmm perhaps i didn't need to apply the Samsung patch then ^^
[Omnia 7 General] spt1234:
After the official T-Mobile (Germany) Update i also have new firmware etc.

OS: 7.0.7392.0

Firmware: 2424.11.2.3

Hardware: 3.15.0.4

Radio: 2424.11.2.2 (i think equal to the one of the newest firmware release I8700XXKC1 XXKB2)

Bootloader: 5.2.1.4

I had the defect Bootloader 4.10.1.9 before but everything went without a problem! Glad i didnt force any update. things that last will be good in the end ^^

I noticed, that if i swipe accidentially on the "back" or "search" button when surfing or in games, they will not be activated. Only if i lift the finger. PERFECT!
[Omnia 7 General] oomniia7:
Does it mean they've fixed it ? woohooo

EDIT: I've just plugged in my oomnia7 T mobile hungary and it shows update.. but i am afraid will it brick my phone because i have that faulty bootloader... with 7004 software on it.. ?

Phone: Samsung Omnia 7

OS version: 7.0.7004.0

Firmware revision number: 2424.10.10.6

Hardware revision number: 3.15.0.4

Radio software version: 2424.10.10.6

Radio hardware version: 0.0.0.800

Bootloader version: 4.10.1.9

Chip SOC version: 0.36.2.0
[Omnia 7 General] spt1234:
i also had it, nothing heard so far that someones phone with the bootloader got bricked. everybody i know from german forum with same bootloader had success

try it! i had the same thoughts but now everything is perfect. if somethin will go wrong in the update you can restore normally.

The phone-pc usb screen shows up for 5-10 minutes during the update dont disconnect! this is normal

just give it time and wait 7008 update took about 20 minutes, to 7392 about 30 mins
[Omnia 7 General] VonCrisp:
Fear not! My German Omnia 7 "pull connection" NoDo 7.0.7392.0 just told me that I had a new update (I rebranded back to T-Mobile).

I updated and voila! It Fixed my bootloader!!! No Jigs!!!!

I confirm like spt1234]

Firmware: 2424.11.2.3

Hardware: 3.15.0.4

Radio: 2424.11.2.2

Bootloader: 5.2.1.4

I went from JJ6 all around to:

PDA: I8700XXKB3

Phone: I8700XXKB2

CSC: I8700DTMKB3

Important! I lost my German T-Mobile "Old town with canal" lock tscreen and am left with a desert!... not that I care.. but whatever rocks your boat right?
[Omnia 7 General] florinr08:
Well I'm still left here unable to update to 7392 from 7390 because of the boot loop issue. (I have tried the Samsung patch with no changes to the loop problem.)

I also discovered according to http://support.microsoft.com/kb/2530409 that by pressing and holding the camera button while booting up, I should get the "Connect to PC" image but it seems that I get absolutely nothing and just keeps booting to the OS. I'm thinking that this might be the issue as the 7392 update tries to get the phone into this state but fails and so I'm guessing that's why the boot loop occurs? Anyone have any more bright ideas so far?

Thanks.
[Omnia 7 General] oomniia7:
EDIT: my phone just updated to 7008 normaly, but now theres another update :/
[Omnia 7 General] br_other:
Yes, it comes first 7008 then 7392.

It goes really smooth and you'll get new firmware with fixed boot loader.

But even with the NoDo, I still miss some things which I saw by another Omnia 7 with 7008 from the factory.
[Omnia 7 General] oomniia7:
Yup, I can confirmt it too, T mobile hungary, unlocked omnia 7, updated with faulty bootloader.. everything works fine, now it is :

7.0.7392.0

bootloader: 5.2.1.4

woohoooo looks like they've fixed the problems !!!!

P.S yed, the old canal wallpaper is gone, replaced with deset.. but who cares.. never liked that one anyway :D
[Omnia 7 General] madonion:
I just tried to update from 7390 (I walshed the phone) to 7392 but I'm stuck at the Omnia logo. It's just sitting there and zune is just sitting on step 6. It doesn't seem as though I'm ever going to get a error message.

I don't have the faulty bootloader so I could do the samsung fix but isn't that for a specific error?

What should I do about this?
[Omnia 7 General] KraFT_mk:
If you have 4.10.1.9 that does not mean that you will have problems updating 100%. So far mostly affected were devices with that version.

Nothing is fixed. Hardly they will fix anything at this point.

So:

- Your update might work without any problems.

- Your update might work without any problems after you used the Samsung update tool.

- Your update might NOT WORK at all as described in the first post.
[Omnia 7 General] madonion:
The samsung update did work. I now have the new bootloader and driver versions as given above. :)
[Omnia 7 General] ManGastaS:
Still

Still waiting :(

unbranded omnia 7 4.10.1.9 boot
[Omnia 7 General] sksarda:
Poor Battery Performance after update...anyone?

My phone's fimware also got updated from JJ6 to KB3 after getting the 7392 notification (bootloader fixed as well).

However, I have experienced that my battery is draining very quickly post the update...even without much use it is hardly lasting from morning to evening, while earlier I could easily go without a recharge for 2 days on moderate usage.

Is anyone facing a similar battery problem, or is it just me?
[Omnia 7 General] KraFT_mk:
@sksadra

Please stay on the subject. This thread is for unsuccessful updates only.​

Thank you.

_________________________________________________________________

PS

If you have 4.10.1.9 that does not mean that you will have problems updating 100%. So far mostly affected were devices with that version.

Nothing is fixed. Hardly they will fix anything at this point.

So:

- Your update might work without any problems.

- Your update might work without any problems after you used the Samsung update tool.

- Your update might NOT WORK at all as described in the first post.
[Omnia 7 General] sarasera:
I have bootloader version 4.10.1.2 and got stucked in the reboot loop at step 6. I installed the Update fix but my omnia still hang in the reboot loop at step 6.

I then tried to restore to before nodo but even here stucked in reboot loop :(
[Omnia 7 General] Fylen:
My solution

Like a lot of people, I was in 7390 and the last update didn't want to be installed (infinite loop).

In fact, i had installed the new Firmware I8700XXKC1 XXKB2, but didn't update the pda part. That was my error. Just updated it and the 7392 update worked at first time.

I hope it could help you.
[Omnia 7 General] florinr08:
For those who managed to install this update, please try this and tell me your findings:

If you hold the camera button while turning the phone on does it go into "Connect to PC" mode as opposed to "Download Mode" with camera + vol up?
[Omnia 7 General] VoodooKing:
Those who can update can definitely enter Connect to PC mode. No need to ask around for this. It is confirmed.

It's those who can't update that can't enter Connect to PC mode.
[Omnia 7 General] florinr08:
Yes but I was wanting to make sure that that was the correct combination of keys for it. So if Samsung already knows this or not, I figured something out that I hadn't realised before: the reboot loop is because that Connect to PC mode is broken?..