yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] chino331:
I have a right to state my own opinion whether I think something is fake or not-also to note I'm not the first one to bring it up. Telling other members that they should hold their tongue isn't polite and shouldn't be done. I'm hoping like everyone else that this is true - this would be awesome to have a fully functional port, but just looking at the pics I have my doubts.
[Touch Diamond, MDA Compact IV ROM Development] robocik:
Exactly how i think.
[Touch Diamond, MDA Compact IV ROM Development] l3v5y:
Can we not have a flame war developing?

I'd really rather not have to issue bans and close the thread.
[Touch Diamond, MDA Compact IV ROM Development] chino331:
Sorry l3v5y - wasn't trying to start anything - will not say anything else regarding that from this post forward. I just thought it was rude and the #2 rule from the link in your signature is "Be polite and respect your fellow xda-dev user".
[Touch Diamond, MDA Compact IV ROM Development] hoopsdavis:
You're correct you do have the right to your own opinion on the issue.

No argument there.
[Touch Diamond, MDA Compact IV ROM Development] l3v5y:
It wasn't directed at you. It's just these things develop, and then I have to spend time working out who did what to whom, and the ROM thread gets nowhere!
[Touch Diamond, MDA Compact IV ROM Development] jossgray:
Less talking more topaz
[Touch Diamond, MDA Compact IV ROM Development] omnicronx:
I meant no disrepect. I just think calling someone out before the claimed release date is disrepsectful in itself.

That being said, I am sorry chino, I was not trying to come across as being rude. I don't want this turning into a flamewar either, nor was that my intent. Lets just hope this is real, as I think everyone will agree, this would be a great addition to the community.
[Touch Diamond, MDA Compact IV ROM Development] chino331:
Davinci - with the world clock issue for the time being 1 hour behind - were you able to fix that?
[Touch Diamond, MDA Compact IV ROM Development] l3v5y:
That gets fixed by using the latest Topaz/Rhodium dlls, which have the dependency on the ported phone canvas.
[Touch Diamond, MDA Compact IV ROM Development] chino331:
it's cool man - not all your fault - bad day at work making me grouchy lol I'm really hoping that this is the real deal also, would LOVE to have a fully functional working port on my phone with out all the bugs!
[Touch Diamond, MDA Compact IV ROM Development] chino331:
ok that's good news! That clock issue was one of my biggest irks with the port - made me late to work a couple times because didn't wake up on time :D
[Touch Diamond, MDA Compact IV ROM Development] geeserver:
Ready to check you ROM out. Thanks for your development. :)
[Touch Diamond, MDA Compact IV ROM Development] moh.sakhaii:
I'm so desperate to get my hands on this ROM with everything inside and all the delicious packages for my own ROM :cool:
[Touch Diamond, MDA Compact IV ROM Development] Drybonz:
I think posting the thread 24 hours before having a place to host files was just inviting the drama really.

There is plenty of free file hosting places that lots of the major chefs use if the OP needs a recommendation we can probably come up with one fairly quickly. Not sure why it has been such an issue.
[Touch Diamond, MDA Compact IV ROM Development] jmz:
I am going to throw the BS flag right now. There is many reasons for it. The main one is 21734. WHAT? That is even higher than the rumored RTM of 6.5. I have also checked with a "source" or two and there is no build higher than the current RTM. And as many people know I do have a good source or two.

The second issue is the slider missing on the Manila screenshot. I know that the Tachi Manila does that when you enable landscape. It also is almost if not completely bug free if you install the right items with it.

The Topaz Dialer looks to be a different pic resolution and it is the only one that has a different taskbar. The resolution of the pic is less than the others. Not the phone resolution.

Now, with that said. If this comes out and it is completely legit, I will 100% apologize about this post and remove it. I will also post a formal apology on my site which gets quite a bit of traffic.
[Touch Diamond, MDA Compact IV ROM Development] hefman:
Not to fan the flames, but I have to admit to being a little skeptical about this as well. A build 734 that nobody seems to have seen in the wild, working Topaz dialer port after so many have failed, other "fixes" with Rhodium manila, having to wait "until tomorrow" to post the files, at least THREE different taskbars in the screenshots, OP's very low post count, etc... I guess one too many hoaxes has made me a pessimist.

That said, the time taken to thoughtfully provide that much relevant information makes me think this just might be real -- or it is a sadist at work.

I will patiently wait and hope to be proven wrong...

...F5...

...F5...

...F5...

...F5...

:D
[Touch Diamond, MDA Compact IV ROM Development] bigfatdude:
Sounds sketchy, to say the least. I wouldn't be too surprised if the RUU file comes loaded with everyone's favorite credit card-stealing trojan.
[Touch Diamond, MDA Compact IV ROM Development] omnicronx:
I'm surprised nobody has asked I3V5y.. he is a mod afterall and was thanked by Davinci in the first post.
[Touch Diamond, MDA Compact IV ROM Development] chino331:
Oh I didn't about that - isn't the highest 6.5 build is 21725?
[Touch Diamond, MDA Compact IV ROM Development] jmz:
21726 is one I have seen in the mist but haven't checked into it a lot.
[Touch Diamond, MDA Compact IV ROM Development] MikeKnoop:
Also, note the use of papyrus in the screenshot, and today's XKCD :)

http://xkcd.com/590/

-Mike
[Touch Diamond, MDA Compact IV ROM Development] moh.sakhaii:
What?? RTM build. I assumes WM 6.5 is months far from release:confused:

What are you talking about jmztaylor?
[Touch Diamond, MDA Compact IV ROM Development] jmz:
Rumor is 21725 is the RTM of 6.5
[Touch Diamond, MDA Compact IV ROM Development] moh.sakhaii:
Well, In this case, It's a piece of s*** cause it has too many hard edges as latest build ;:p LOL
[Touch Diamond, MDA Compact IV ROM Development] Trident:
My prediction: Some time in the next 24 hours we'll get a post telling about some personal tragedy or computer malfunction that is delaying everything. Or there will be some sort of story about why it's getting delayed or cancelled. Could even be that the OP is offended by all of us doubters and goes and plays elsewhere. End result, this is never seen by anyone other than these mysterious developers.
[Touch Diamond, MDA Compact IV ROM Development] Royals:
This would be a great April Fools joke...if it was actually april 1st :D
[Touch Diamond, MDA Compact IV ROM Development] cloud5005:
Please stop talking....please wait only wait....

Come on Da vinci...someone believe in you...:)
[Touch Diamond, MDA Compact IV ROM Development] faxmonkey:
I'm hopeful, but wouldn't be surprised either way.
[Touch Diamond, MDA Compact IV ROM Development] l3v5y:
I offered to cab up the OEM packs as and when they're released. I haven't had anything in my hands yet, but as soon as I do, and as soon as I'm allowed, I'll post things.
[Touch Diamond, MDA Compact IV ROM Development] sheennick123456:
about different taskbars

these might be due to 3 different devices as mentioned on which they have tested this port :)

......just trying to keep the hopes alive :D
[Touch Diamond, MDA Compact IV ROM Development] indagroove:
you don't want to give me any credit for taking files from my kitchen buddy??
[Touch Diamond, MDA Compact IV ROM Development] moh.sakhaii:
Wow, What's going on? LOL
[Touch Diamond, MDA Compact IV ROM Development] hoopsdavis:
Its getting HOT in here!!!!
[Touch Diamond, MDA Compact IV ROM Development] hoopsdavis:
Hey Groove, I always appreciate your ROMs buddy.

Thanks
[Touch Diamond, MDA Compact IV ROM Development] indagroove:
what's going on is that he took my kitchen, faked a build, and is feeding you bogus. very rude Imo.
[Touch Diamond, MDA Compact IV ROM Development] moh.sakhaii:
OK , who did it? OP or the one in the previous post ?:confused:
[Touch Diamond, MDA Compact IV ROM Development] Leukay:
I figured that's what he did, but still have my fingers crossed. This could be a very cool ROM if its true. Unfortunately the screenshots seem very shady, but still waiting in anticipation.

plus, i apologize for adding to the "waiting" posts.
[Touch Diamond, MDA Compact IV ROM Development] TheLegendary87:
So Inda, are you saying there really is no fully working Topaz dialer and Rhodium manila coming from this person? This is all just fake?
[Touch Diamond, MDA Compact IV ROM Development] lemeiux1:
indagroove can you confirm that this is fake?

I just dont want to waste anymore of my time on this
[Touch Diamond, MDA Compact IV ROM Development] hmota78:
Why would someone go through all this trouble - screenshots, ROM information, Topaz phone canvas ... etc. - if non of it is real? I'm not saying it is or isn't, I just really don't understand why anyone would do that...:confused:
[Touch Diamond, MDA Compact IV ROM Development] Leukay:
I agree. It seems like a LOT of work just to play a little joke on everybody here. But as i said before, im not going to assume that it's fake just because nobody has seen it yet.
[Touch Diamond, MDA Compact IV ROM Development] indagroove:
Id bet good money this is fake, and when I get home I'll tell you exactly why.

if it's somehow real, stuff was still taken from my kitchen without the proper credit,which is just rude. its fake anyway.
[Touch Diamond, MDA Compact IV ROM Development] omnicronx:
The background of the lockscreen in the screenshot is the same as Grooves custom background for his kitchen.

Go look for yourself: http://forum.ppcgeeks.com/showthread.php?t=60908

Could just mean he is using his kitchen though..(the OP did state he would thank others upon release) although groove may see something else that I am missing.
[Touch Diamond, MDA Compact IV ROM Development] hmota78:
Spot on! Exactly the same background.
[Touch Diamond, MDA Compact IV ROM Development] jmz:
Ironic? ???
[Touch Diamond, MDA Compact IV ROM Development] lemeiux1:
Ok now im positive this guy is full of ****! delayed until further notice? what happened? thought everything was "all packaged up and ready to go"?

give me a break
[Touch Diamond, MDA Compact IV ROM Development] jmz:
Instant Ban
[Touch Diamond, MDA Compact IV ROM Development] SOHKis:
yeah, what a coincidence...:rolleyes:
[Touch Diamond, MDA Compact IV ROM Development] xeo00:
delete this piece of ****

waste of time
[Touch Diamond, MDA Compact IV ROM Development] cchris81:
Yeah guys, check out the first post.... Totally saw it coming.
[Touch Diamond, MDA Compact IV ROM Development] jmz:
+1 for that
[Touch Diamond, MDA Compact IV ROM Development] jossgray:
*sigh* i was really excited for that
[Touch Diamond, MDA Compact IV ROM Development] NotATreoFan:
Closing this thread temporarily while us Mods review all the facts entered into evidence... (sorry, I always wanted to say/type that)
[G1 Android Development] schnogg:
I have been using JF 1.43 for a few months and loved it. Seeing that Cupcake became mainstream, I took the plunge two days ago and have been having issues. I tried JF 1.51, then a mod, then theDudes, all with some problems. I tried wiping and keeping apps in regular memory just for testing. I finally got a clean install using TheDudesCupcake which worked ok for me. When I pushed my preferences back using adb, it just hung on the "android" screen.

I was getting annoyed at myself for not understanding what was going on . The confounding problem was that the set of prefs that I was restoring had adb disabled, so I couldn't get a logcat to see what was really happening.

Long story shorter...

After some more fresh installs, I think what I have sorted out is that all of my preferences files lost their correct ownership. I found that when I had a program that was crashing, I would log in to an adb shell, use ps to see what user the app was running as, for example app_82. Then, I would chown app_82.app_82 for the directory within /data/data. I would then to it recursively since busybox doesn't have -R for chown by issuing the command chown app_82.app_82 /data/data/com.android.weather/cupcake/* and then chown app_82.app_82 /data/data/com.android.weather

It fixes programs that were having problems accessing their sqlite3 DBs which was the clue in the logs that led me to this solution.

As I am going through I see that it improves the performance and error rate of programs by doing this. Obviously core functionality doesn't have the same ease of repair.

Is this the wrong thing to do here? Is there a better way to restore files after an upgrade so that this doesn't happen again?

I saw that someone wrote a python script to fix these permissions, though I don't understand where they got python to run on Android in the first place. Is there a shell script that can parse an app's uid and fix its supplemental files accordingly?

I tried searching, but may not have used good keywords about this issue.

Any help/advice/info would be appreciated.
[G1 Android Development] schnogg:
The answer

This guy has a python scirpt that nicely spits out a shell script to fix all of them

http://blog.elsdoerfer.name/2009/05/25/android-fix-package-uid-mismatches/

"""Parse Android's /data/system/packages.xml file and spits out
shell code to fix UIDs.

This helps you fix "Package x.y.z has mismatched uid: 10089 on disk, 10079
in settings" errors.
"""

from xml.dom import minidom

xmldoc = minidom.parse('packages.xml')

packages = xmldoc.getElementsByTagName('package')
ignored = []
for package in packages:
try:
userId = package.attributes['userId'].value
is_shared = False
except KeyError:
userId = package.attributes['sharedUserId'].value
is_shared = True

# do not touch permissions of shared apks (they userid always seems to be 1000)
if not is_shared:
print "busybox chown %s:%s %s" % (userId, userId, package.attributes['codePath'].value)

for subdir in ('', 'databases', 'shared_prefs'): # note we don't touch lib/
print "busybox chown %s %s:%s /data/data/%s/%s" % (
'-R' if subdir else '', userId, userId, package.attributes['name'].value, subdir)

Essentially, you can use adb pull to pull /data/system/packages.xml locally, run this python script on it, and then send each command back. One way to do this on *NIX is

adb pull /data/system/packages.xml . ; python fix.txt | xargs adb shell
[P3600 ROM Development] uniz:
can somebody make a dutch wm 6.1 rom??
[Touch Pro, Fuze Themes and Apps] LumberjackZac:
I have the garmin mobile xt 4.20.30wp on my phone and I installed and configured nodata because i don't have data plan. Why is it that garmin can still connect to Medianet(EDGE) and i struggle to keep disconnecting it?

I don't believe it needs to be connected for the GPS to work, or am i stupid?
[Touch Pro, Fuze Themes and Apps] Captain_Throwback:
Do you have aGPS enabled? If so, that's why.
[Touch Pro, Fuze Themes and Apps] LumberjackZac:
Duh, didn't check. lol
[XV6700, PPC-6700 ROM Development] Friend in China0755:
Hello, my friends.Excuse me, does the ability help me once? Friends I come from Shenzhen, China- My demand some cellular phone software be read the xv 6700 ROM-nk.nbf software with read radio_.nbf document of can the software help me? Thank you I would on-line etc. of. This is very the yuluozhenai@ of my mailbox 63. com with gratitude!!!:):):)
[XV6700, PPC-6700 ROM Development] ghost_nup:
er,I think no one would understand what you say.

I think you can visit www.diypda.com ,it's all in Chinese.

BTW Chinglish is a funny thing:p
[XV6700, PPC-6700 ROM Development] chuckknight:
If I'm understanding your request, the answer is as follows: You need a copy of QPST. It's a piece of software used by service technicians, to edit/modify settings on CDMA phones, including the 6700 series.

We don't usually discuss such things, on this forum, but there is a wealth of information on google. Use the search terms "qpst ppc6700" and see if that answers your question.
[XPERIA X1 Themes and Apps] MattiasSod:
Great multimedia app (Orb, twitter, flickr, youtube and more) just released In new version, workin well with Xperia (but not fully tested by Kinoma themselves). Only issue I´ve found is that softbuttons may not work.

http://www.kinoma.com
[XPERIA X1 Themes and Apps] knaplullig:
looks great!

to bad it costs 30 dollars..

bit too much if u ask me
[XPERIA X1 Themes and Apps] CowMix:
looks like theres a free version, I'll try it out
[XPERIA X1 Themes and Apps] souljaboy:
its a ripoff

its advertized as FREE player .

then asks for email < ok

then when u give them ur email , finally open player , u need to BUY player

WASTE OF TIME not recommended for any1
[XPERIA X1 Themes and Apps] shithead:
Nah

Kinoma FreePlay is a free version of Kinoma Play

There's a difference between FreePlay & Play.

You need to put the emailadres in FreePlay Application to "activate" it.

They don't spam or anything so :) Give it a try.

If you want more stuffs you need to buy Kinoma Play, which is about 30 dollars.
[XPERIA X1 Themes and Apps] BuddyLee:
i made a video on kinoma play

http://www.youtube.com/watch?v=lhm2ZT4ImFs
[XPERIA X1 Themes and Apps] mccoffein:
Hy,

you can also try this one http://www.ffmpeg-wince.org
[XPERIA X1 Themes and Apps] £thereal:
thanx guys its realy a cool program;)
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] dexterbh:
Hey,

I got my TD2 this morning and i love it.. such an amazing phone.

Altough probably from my mistake, i have problems with my music.

I got a MicroSD card, and i put some songs on it, and put it in the phone, and they played fine. Bu then i wanted to be cool, and a few of my songs didnt have an album photo, as i was scrolling between them, so i thourth i add photos to everyone of them. I got my MicroSD card out of the phone, and deleted the songs of it, and added photos to my old songs and put those on to the SD card again. But in the phone, in the Music album at "Now Playing" all the list of songs shows, without album and i cant click on them. I cant play it, a cant delete (i dont know how.)

If i go to the File Explorer -> Storage Card -> Sounds -- Its empty, but there are all the songs on my phone, and idont know how to get rid of them.

How do i clear the whole playlist, artists, songs on the phone ?

Or what do i need to do?

Anyone got any ideas ?

I apprichate the help in advance.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] aLKayeL:
Have you tried a soft reset?
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] peter van lis:
Disable Tflo3d

Soft reset

Delete in Application Data\HTC\AudioManager_Eng the file AudioManager_Eng.vol

Enable Tflo en let the musictab search again
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] jchoong:
When I first got my TD2, I loaded a lot of my MP3 music into the SD card; these albums also have pics. Then when I ran music from TF3D, after a few secs, the track will hang. This happened not only to MP3 from my SD card, but also MP3 titles that are preloaded into the TD3 (2 music pcs I believe). I tried all sorts of things; even wrote to HTC Support but could not resolve the hang problem. Then, by coincidence, I put a different SD card (with no MP3 files) into my TD2. To my surprise, the hang problem disappeared. Subsequently I deleted almost all of the MP3 files from my original SD card, but kept just 2 albums (with pics), and TF3D Music played these without any problems. Still don't know the cause of the hang; I know the MP3 files were a problem, but can't pinpoint exactly which MP3 file or pic.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] dexterbh:
Oh guys, your awsome :)

Thanks very much for your help.
[Touch HD General] cartwright118:
Hi guys,

Just a quick question, if I successfully install the Hard SPL onto my Touch HD, is it still possible to permanently brick my device when installing a ROM if something goes wrong with the install?

As i read on another forum this quote 'it's always advisable to install Hard SPL as it prevents you from bricking your device with a problematic ROM flash'

Thank you in advance,

Regards, Chris
[Touch HD General] crajee:
Under usual circumstances with even least common sense you almost can't as you can always get to the tricolor boot screen and flash again. But if deliberate (force flash a different device ROM etc) then one possibly can..
[Touch HD General] cartwright118:
Okay mate, thank you for the reply.

Regards,

Chris.
[Touch HD General] amarullz:
Ok.. 1 question from me... Even the USB is disconnected in half of flashing?
[Touch HD General] johnpatcher:
That doesn't harm anything. As long as you are not going to flash the SPL (which can't be done with HSPL as it is write protected) you can't damage your device. You can still get to the tricolor screen and flash your ROM once again.
[Touch HD General] amarullz:
Great... Thanks for your info. For safety reason I will never upgrade or change SPL:D.

just flash the ROM as much as I want :D:D:D
[Touch Pro, Fuze ROM Development] tshwashere:
I am trying to flash from the bootloader to recover from an installation error on my Fuze. I've entered into the tricolor bootloader screen by holding down Vol.down and reset. Now, when I plug the phone into the computer, the computer recognize the phone as a Qaulcomm CDMA Technologies MSM, and is trying to install a driver for it (which it cannot find.) When I run the Custom_RUU, it does not find my Fuze and is showing a ERROR[260]: Connection.

What am I doing wrong? Do I need to find a driver for Qualcomm first? I searched, and it seemed that when you enter bootloader to flash, it is suppose to say USB at the bottom. Mine says Serial. Does that matter?

If more information is needed to troubleshoot:

SPL is SPL-1.90.OliNex

Phone is unlocked by using Olinex's unlocker

Rom was EnergyRom 3.0 Phoenix 51909

Problem was caused because I tried to install Studio Kuma Traditional Chinese Fonts on it. That program works flawlessly on a WM6.1. Of course, Energy 3.0 are WM6.5, hence causing the problem.

Any assistance is very appreciated.
[Touch Pro, Fuze ROM Development] SamsungGalaxySamsung:
Try sd card flashing:rolleyes:
[Touch Pro, Fuze ROM Development] player911:
You have connect your device to your USB port and let it find the drivers. In order for it to download the drivers, you must have Activesync or Windows Mobile Device Center.

Once you have one of those downloaded, launch it and connect the device while it is running normally. Opt to connect via Activesync on your phone. You don't have to have these running in the future but you need it to find the drivers and install them. Leave the Activesync connection intact while you run the Flash program.

Once the phone reboots in bootloader mode, the PC will probably download some more drivers. The Flasher will probably time out while the drivers are being downloaded and installed. Keep trying.

Once the bootloader drivers are downloaded and installed, try to run the Flasher program again. Sometimes you'll need a reboot if something is hung up.

You SHOULD be able to reboot, put the phone in bootloader mode (Down + Power + Reset) and it should change "SERIAL" into "USB". Once it displays "USB" you are good to go. Load up the Flasher program and it should go all the way through without the assistance of ActiveSync or Mobile Device Center.

I always flash in bootloader mode, I just know the initial pairing is rough.
[Touch Pro, Fuze ROM Development] tshwashere:
Well, I flashed from sd card, and the phone is working now. Thanks for everyone's replies.