yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 General] doministry:
Ok, so you're happy now how you dealed with it?

Hope so.
[XPERIA X1 General] Ganondolf:
when we get the x2 rom we can put it on the x1 and everyones happy. the x2 is better than the x1 but not by a large margin.

the x2 probably has the drivers which the x1 needed (i think it was htc fault that we did not have drivers and that the x1 has a cracking problem so im happy that they have gone to foxconn).

also my x1 with the Official SE r3 rom + tweaks is superfast with no lag or slowdown (vids and some games aside) so there is no reason why sony cant make the x2 lag free and superfast with the same cpu (especially if they now have the drivers), as the x2 does not have anything new apart from a fancy ui panel (which the ati chip and cpu with drivers should be able to handle with ease). i think its more down to how good the x2 teams developers are more than the hardware as it got no real big improvements over the x2.
[XPERIA X1 General] orelsi:
I haven't dealt with anything...

Actually, that might be the single positive aspect coming out from that X2 joke.

I would be perfectly happy, if we get all the software ported.
[XPERIA X1 General] spikegotti:
i think the x2 rom on the x1 would be nice, its just the keyboard and camera drivers that makes the difference, which our awesome chefs here can fix...a nice tasty recipe :)
[XPERIA X1 General] doministry:
That's what I say.
[XPERIA X1 General] orelsi:
LOL!

Well, I meant that you cut your own throat, but feel free to take it as you will hahaha!
[XPERIA X1 General] doministry:
Tralalala.
[XPERIA X1 General] doministry:
All the previews basically show X2 pre production units

snappy and fast.
[XPERIA X1 General] orelsi:
Indeed......
[XPERIA X1 General] caliban2:
the two of you are getting more and more childish with every post... please, what are pm's for?! :p
[XPERIA X1 General] doministry:
Yes I agree :p
[XPERIA X1 General] caliban2:
looks i have to say "sorry, SE" somehow... :D

itje got his hands on an official (!) 6.5-rom!!!

http://xdaforums.com/showthread.php?t=557348
[XPERIA X1 General] doministry:
Thats quite interesting
[XPERIA X1 General] comeradealexi:
AWESOME! :D!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[XPERIA X1 General] Chaosstorm:
Soon xperia will be a very cool ppc :P Look at this http://www.nuerom.com/BlogEngine/post/2009/09/06/Touch-Pro-running-at-800MHZ.aspx

There seems to be a way to overclock it to 768 MHZ !!! and the speed improves 50% :P from 300 integers to 450..
[XPERIA X1 General] caliban2:
yeah, sounds good. :)

but somehow i don't know if i want to overclock this thing... just think about the heat. you can't put in a bigger fan like in a pc. ^^

let's see what nue comes up with and how this will do in practice. i want better drivers first.
[XPERIA X1 General] frive:
Hehe, who needs X2 anymore (well except to be exploited software-wise)?

X1 will be back like phoenix from the ashes :D
[XPERIA X1 General] comeradealexi:
Look good, guess we'll have to wait till its released, plus it says its for the Touch Pro though?
[XPERIA X1 General] Chaosstorm:
touch pro, touch diamond, there all QMSM 7201A/7200A :P
[XPERIA X1 General] orelsi:
The heat will kill the cpu.
[XPERIA X1 General] caliban2:
that's what we have to wait for. who knows, maybe he'll be able to manage some steps in between, like 624 mhz. 800 is a bit much...
[XPERIA X1 General] doministry:
Hehe, I still want it :D

Has some needed things...
[XPERIA X1 General] orelsi:
Well, in this case it comes to how much risk the user wants to take. Some people might be prepared to shave 2 years from their cpu's expected lifetime, but others not.
[XPERIA X1 General] comeradealexi:
well ijte has got a 6.5 build with the x2 drivers running extremely faster so lets see what thats like first before we OC
[XPERIA X1 General] Chaosstorm:
i dont think this phone was designed to last longer then 2 years :P so.. why not make the most use of it :)
[XPERIA X1 General] gundamboy:
tested the touch pro overclocking, all it does is restart the X1 when it's not charging,

and locks up while charging.

best to wait for a final release!
[XPERIA X1 General] orelsi:
LOL :D. I am planning to use the X1 for as long as that as my primary device and 10 years more as a backup. :cool:
[XPERIA X1 General] Chaosstorm:
Ok .. in that case i wouldve bought a body guard for the x1 so he can jump when it falls or shoots some one that wants to touch it :cool:
[XPERIA X1 General] orelsi:
What makes you think I haven't hired one already!:eek:
[Hero, G2 Touch Android Development] muyan:
Major problem as a result of an unsuccessful attempt to permanently installing the recovery image.

The result is that Android now reports that the SD card is not present (I've tried 3 different cards), and the USB mode allowing adb is no longer available – the USB interface is not recognised (except from the bootloader).

I can flash stock firmwares from my SD card using Hboot or from RUU packages using USB by manually booting the bootloader, thus the interfaces themselves are working.

I have attempted to clean wipe the entire device, updating/downgrading and even installing the newest 2.73.405.5 ROM did not resolve this issue.

I have not found anyone reporting the same problem. I am running out of ideas and could really need some help/advice on how to resolve this. Especially if someone have a better understanding of how android is booted and how the symlinks and devices are created. I am a long time Linux user, but without the ability to use the recovery image/adb, USB or SD card to patch or inspect I am currently experiencing some difficulty investigating this further.

Update:

I've done some more digging and I think I have found the problem, however I don't know how to correct it.

Dmesg shows my kernel command as:

board_hero.disable_uart3=1 board_hero.usb_h2w_sw=1 board_hero.disable_sdcard=1 smisize=32 androidboot.baseband=6.35.06.18 androidboot.cid=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=HERO10000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT97ML906986 androidboot.bootloader=1.76.0007 no_console_suspend=1 console=null

it also lists:

trout: SD-Card interface disabled

and as a result /dev/block/vold/179:1 is never created and not mounted.

Is there a way to correct the kernel command line, or do I need to wait for a S-OFF Hboot firmware to have possibly correct this?
[Hero, G2 Touch Android Development] Reso9:
Same problem here. Nobody who knows how to solve this???
[Hero, G2 Touch Android Development] packetlss:
Can you still boot images using fastboot?

like: fastboot boot <recovery-image-name>

Also, which HBOOT version does it display?
[Hero, G2 Touch Android Development] Reso9:
It's showing HBOOT version 1.76.0004

I can still boot a recovery image but when i selcet update.zip, any zip or nanroid backup it's saying "Can't mount sdcard".

Another very big problem is that the device can't read any sd cards even when i have booted android normaly. It's always showing that no sd card is plugged in.
[Hero, G2 Touch Android Development] packetlss:
Really strange. Your cmdline say HBOOT is 1.76.0007 and your bootscreen 1.76.0004.

You can alter the commandline from fastboot though.

Try something like this:

fastboot -c "board_hero.disable_uart3=0 board_hero.usb_h2w_sw=0 board_hero.disable_sdcard=0 no_console_suspend=1 console=null" boot cm-hero-recovery.img

It only appends to the commandline though, but it's worth a shot.

For reference I give you my full booted cmdline if it is of any use.

# cat /proc/cmdline

board_hero.disable_uart3=0 board_hero.usb_h2w_sw=0 board_hero.disable_sdcard=0 smisize=32 androidboot.baseband=6.35.06.18 androidboot.cid=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=HERO10000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT<removed> androidboot.bootloader=1.76.0004 no_console_suspend=1 console=null

I'm pretty sure there is some way to configure the HBOOT, do you remember want exactly went wrong/what you did when flashing the recovery?
[Hero, G2 Touch Android Development] Reso9:
Thanks for your help but i have maked a big mistake in the meantime. I have flashed the new rom with ruu. Now it' showing HBOOT 1.76.0007 and i can't load the recovery image. Still it's showing me that there is no sd card.

The commandline that you have written doesn't works because of this. Nothing with fastboot works at the moment becouse of HBOOT 1.76.0007.

Do you know how to get back to 1.76.0004 or how to load fastboot with HBOOT 1.76.0007???

Edit: I have just saw your answer on the other post. I will give it a try. Thanks for your help.
[Hero, G2 Touch Android Development] Reso9:
It isn't possible to flash the old HBOOT because i can't access the sd card. Is there a way to enable the sd card without recovery or is there a way to flash the old HBOOT without sd card???
[Hero, G2 Touch Android Development] paulobrien:
So can the recovery flasher APK not flash without a SD card?

If not, how about tricking it into thinking the sdcard (when booted up) is there by mounting /data then symlinking /sdcard to a dir on /data?

P
[Hero, G2 Touch Android Development] Reso9:
I don't know if i can flash the apk recover without sd card. That's why i am asking for how to make this.

How can i trick on booting up? Do you know where i can find a tutorial or something like that?

Can you help me please?

I'am a newbee on android just changed from winmo.
[Hero, G2 Touch Android Development] Reso9:
Can anbody tell me how to do this?
[Hero, G2 Touch Android Development] dennis333:
I think I have the same problems.

See this thread: http://xdaforums.com/showthread.php?p=4547286

I can't use USB during normal Hero operation (so no option to mount SD card).

I can't use adb. If I do adb devices adb returns with none.

The 2 above are in conjunction with Windows (7 x64, but with correct drivers, it worked before) not recognizing the usb device.

I CAN however go into bootloader (power+back button) and use the fastboot command.

So what I do to flash stuff is physically pulling the sd card from my phone and putting it in my pc (via adapter of course) , copying the necessary files onto sd card and then putting the card back into the phone.

What I still want to try is flashing Amon Ra's recovery permanently and therefore you have to use a adb shell command (adb shell flash_image recovery /sdcard/Recovery-RA-HERO-v1.2.2.img).

I will try to use a terminal on the Hero itself (Better Terminal Emulator Pro) for this command or otherwise use the program FlashRec.apk, thus circumventing the need for adb at all I hope. :confused:
[Hero, G2 Touch Android Development] latiszm:
I have the same problem, It was working perfectly, then all of a sudden the computers wouldnt recognize the phone anymore (Unrecognized USB). I was speaking to HTC about it who told me to send the unit back for service/repair.

I will send it back to HTC tomorrow and it will take about 2-3 weeks till I get it back again. I will post a report here on what they did to it.
[G1 Q&A, Help & Troubleshooting] Pinesal:
So I have two G1s. ADB already works for one. And it used to work on the other one but after wiping and applying cyanogen's latest experimental build, adb doesn't work anymore. What are the steps to get that going again?
[G1 Q&A, Help & Troubleshooting] AdrianK:
Make sure USB debugging is enabled.

Settings > Applications > Development > USB Debugging
[G1 Q&A, Help & Troubleshooting] Pinesal:
Yeah it's on.

When I type "adb shell"

I get "error: device not found"

Any other ideas?
[G1 Q&A, Help & Troubleshooting] AdamPI:
Perhaps windows is using the wrong drivers?

It should have the entry

"HTC Dream Composite ADB Interface" in device manager.
[G1 Q&A, Help & Troubleshooting] Pinesal:
I can plug in the other phone and get ADB. So it's not a driver issue.
[G1 Q&A, Help & Troubleshooting] david1171:
If what is posted above me is what your device is listed as, then try opening up a task manager and stopping adb.exe and then try adb again. Something like that happened to me once and that is how i got it working again
[Tilt, TyTN II, MDA Vario III General] Dukenukemx:
My Kaisers Camera image has 3 blue vertical lines in it. I just got this phone a few weeks ago, and I didn't see them when I got it. I got it off Ebay, so it is used. Otherwise, phones in great condition.

Is there a way to fix this, or I gotta get the camera replaced? I don't see anyone selling the Camera replacement part. Will T-Mobile or HTC fix it for free?
[Tilt, TyTN II, MDA Vario III General] antonieoalan:
try changing the cooked roms

mine also had te same problem with shifu rom

now its good with other roms
[Tilt, TyTN II, MDA Vario III General] Dukenukemx:
I also had shifu rom and thought what you said. I switched over to the AthineOS, but it didn't go away. I didn't flash back to the original rom first on my phone. Could it be that I need to flash back to the original T-Mobile rom first and then to AthineOS?

Also, what rom are you using?
[Tilt, TyTN II, MDA Vario III General] Dukenukemx:
I installed the HTC orignal firmware, and then flashed TPCElite. I didn't fix it.

So, does this mean it's hardware?
[Tilt, TyTN II, MDA Vario III General] tdamocles:
I have a similar problem but with one red vertical line. I have A TPC v11 ROM loaded. I flashed to the stock rom but it still had the same problem. Any ideas?
[Tilt, TyTN II, MDA Vario III General] tdamocles:
Does anyone know where to purchase a rear camera assembly?
[Tilt, TyTN II, MDA Vario III General] Dukenukemx:
I noticed that with the T.i.R. v20 K rom, my Camera produces a strange horizontal fuzy line across my picture. It's not a thin line like the vertical ones, but a thick and white fuzzy bar going across the image. Problem is, it only appears when you look at the image after you're done using the camera.

Oddly, I switch over to a different radio rom 1.65.16.25, and now it doesn't happen. Instead I got one of my vertical lines to appear again. I had a 4th one appear a few months ago, but it had vanished. Now that I installed the 1.65.16.25 rom, it came back again.

By installing the 1.70.18.02 rom, the lines even changed color. Went from blue to red now. Some of the lines are broken, like parts are normal. Plus a 5th line is now added.

I'm nearly convinced that my camera isn't broken, but instead there's a problem with mixing the Radio+Roms. Especially since this is a T-mobile model, which isn't very popular here on the forums. I think by trying Android and using the camera will tell me if the Camera is physically broken.

Who else has this problem and has a T-Mobile Kaiser?
[Tilt, TyTN II, MDA Vario III General] stuntdouble:
As was previously suggested it definitely sounds like you need to keep testing different radio versions for your phone if you are getting these lines etc. About 99% of the time it's just due to that. I've had a similar problem before and I fixed it by going through about 15 different radios. It took a while but got there in the end. Perseverance is the key. Luckily it doesn't take long to flash the radio each time. Failing that, maybe try a new rom? Good luck.
[Tilt, TyTN II, MDA Vario III General] hermanwen:
lol i got the same problem too, eventhough using original rom. I had vertical and horisontal line :(
[Tilt, TyTN II, MDA Vario III General] mharrissmith:
[QU yoOTE=Dukenukemx;5141793]I noticed that with the T.i.R. v20 K rom, my Camera produces a strange horizontal fuzy line across my picture. It's not a thin line like the vertical ones, but a thick and white fuzzy bar going across the image. Problem is, it only appears when you look at the image after you're done using the camera.

Oddly, I switch over to a different radio rom 1.65.16.25, and now it doesn't happen. Instead I got one of my vertical lines to appear again. I had a 4th one appear a few months ago, but it had vanished. Now that I installed the 1.65.16.25 rom, it came back again.

By installing the 1.70.18.02 rom, the lines even changed color. Went from blue to red now. Some of the lines are broken, like parts are normal. Plus a 5th line is now added.

I'm nearly convinced that my camera isn't broken, but instead there's a problem with mixing the Radio+Roms. Especially since this is a T-mobile model, which isn't very popular here on the forums. I think by trying Android and using the camera will tell me if the Camera is physically broken.

Who else has this problem and has a T-Mobile Kaiser?[/QUOTE]

Have the same problem with Tir 20K. used to have TPC V11 without problems (Same radio on both) will tr to change ROM/Radio and let you know.
[Tilt, TyTN II, MDA Vario III General] mharrissmith:
Changed to JJBlaster3 Build 23518 ROM and the lines went away. Same when I had TPC V11. The problem was with the TIR Rom (or the Radio combination with it)
[Tilt, TyTN II, MDA Vario III General] stuntdouble:
Yes I think JJ applied some sort of camera fix months ago in his roms. But maybe it wasn't for this exact problem.
[Tilt, TyTN II, MDA Vario III General] Dukenukemx:
I haven't tried that rom yet. I'll let you know if it fixed it for me.
[Tilt, TyTN II, MDA Vario III General] btec1020:
Hi dukenukemx, is your TyTN II already fixed? Cos mine has the same problem. I've tried flashing around 5 cooked ROMs (always flashing stock ROM in between), and around 12+ radios. By the way I didn't notice if the lines were already there before I started flashing cooked ROMs. The first time I noticed it, there were 5 lines. Now I can see 7 lines. So looks like this can be software rather than hardware related. Hope someone can help me solve this problem.

Thanks everyone... Cheers...
[Tilt, TyTN II, MDA Vario III General] pjump:
hello need everyone help..

hello guys..

firt i wanna ask about camera also..i got kaiser 130,htc tytn 11 also but not sure what model at&t or tmobile or else..but my phone got front camera.

so my problem is i already flash with shifu roms.and my camera seem had problem to change to the front camera..at the screen there is no more icon for changing camera next to the storage andself timer..then i try to flash with other stock roms..but it wont come back.still the same untill now i cant use the front camera to make v.call and to snap pics

so i need yours advise and if there somebody who can help me please sent at my private mesage..or sent at my email pjump_slay@yahoo.com
[Tilt, TyTN II, MDA Vario III General] svcglobal:
HardSPL?

Could be possible that HardSPL 3.28 to be linked with the vertical lines camera issue?

Coincidentally or not, my TyTN II started to suffer this s**t just after upgrade to 3.28.

For the records, I already tried many cooked ROMs, radios and the issue did not disappear.

Thanks.
[Tilt, TyTN II, MDA Vario III General] Mr. Clown:
Have you try another hardspl and see if that solves your problem (also corroborates your theory?)
[Tilt, TyTN II, MDA Vario III General] love.me:
my camera seems got the same problem..

and my signal receiver is very suck..i always get no service on my device n my camera has a vertical line..

anyone has solve this problem?
[Tilt, TyTN II, MDA Vario III General] ChumleyEX:
Have you tried the solutions provided above.
[Tilt, TyTN II, MDA Vario III General] love.me:
i already done with camera fix,but that cab make my kaiser stuck at smart mobility,,

i use hardspl 3.29 n hardspl 3.56

should I try another hardspl?
[Tilt, TyTN II, MDA Vario III General] Asyraf1985:
Hi,

My TYTN suddenly don't have any sound.just vibrate only when incoming call and sms received. before this, everything work fine. it just happen after i change from silent mode to normal mode.

Is it related to my ROM? for ur info, my

ROM Version is 3.29.707.0 WWE

ROM Date: 05/07/08

Radio Version: 1.65.16.25

Protocol Version: 25.83.40.02H

I do searching regarding to my problem. Some people say that it is the radio version problem. I don't know which radio version is suitable for me. can anyone suggest to me?

I try to play MP3 in my TYTN but still no sound. I've also restart my phone.but it still same issues. Any recommendation to solve this problem?

Thanks
[Tilt, TyTN II, MDA Vario III General] ASCIIker:
hmmm, lets take a step back and first think about any possible changes you may have made just before the problem occurred. you say you only changed the sound profile from silent to normal mode. are you certain this was the ONLY major change you made? for example, did you just flash the ROM you are using or you have been using it for quite some time?

if changing the sound profile was really the only thing you did before the problem occurred, then your radio version SEEMS fine and you probably shouldn't change it.

have you checked the sound volume (system as well as ringer)? try bringing the volume down to zero and then bring it back up.

maybe you should change the profile back to silent mode or vibrate mode and then do a soft reset and then change it back to normal mode and then do a soft reset.

as a last resort, have you tried a hard reset?
[Tilt, TyTN II, MDA Vario III General] torchbearer:
Edit:

Thanks ASCIIker

I have made a new thread.

http://xdaforums.com/showthread.php?p=4480029#post4480029

Sorry for Hijaking!
[Tilt, TyTN II, MDA Vario III General] ASCIIker:
thread "hijacking" is not a good idea...

still, it seems that you are also experiencing the same issue. IF AND ONLY IF you also did NOTHING major when the issue started (like flashing a ROM). you say you flashed a ROM AFTER the issue started to try to correct the problem so that makes your case a bit different than the person who started this thread (who really did not do anything major it seems).

in your case, did you follow ALL the instructions on the first page and FAQ of the ultimate x2 thread? i'm asking because that ROM requires flashing stock ROM before flashing ultimate x2, and you haven't even mentioned which radio and spl you are using, so you haven't provided enough information. all the same, the above quoted post of yours seems to belongs in the ultimate x2 thread in my opinion, hence why i suggested that thread "hijacking" is not a good practice.
[myTouch 3G, Magic General] kchau:
which rom provides the most speed? im not talking about cpu clock speed, but rather the most efficient.

i ask because alot of the roms are either developed for the dream and ported to the magic, or build for both the dream and the magic. the dream has less resources, but is there a difference in optimizations that would make a magic only rom perform better?
[myTouch 3G, Magic General] pack:
thats a hard question to answer because if you look at any rom thread you'll see replys that say "this is the fastest rom ive used" so its personal opinion. if you want something that will work great for your phone use what it came with... the phone was built to run that and all but if you just wanna change it up... start flashing until your happy
[myTouch 3G, Magic General] kchau:
well what about my second question?

would a rom developed specifcally for the magic, and nothing else, would that be faster than a rom that works on both the dream and the magic?
[myTouch 3G, Magic General] st0kes:
One thing I can tell you is (if you have the 32B board Magic) don't bother with Hero roms if you are looking for speed. Cyanogen is the fastest ROM I've tried.
[myTouch 3G, Magic General] Johnny Blaze:
try Zeroxd latest 32b rom. Then search forum for adb explorer.

Using adb explorer remove the following from your device

Plurk, Stocks, Teeter, All widgets you will not use, pdf viewer, quickoffice, power manager pro, launcher if you are going to use touchflo.

Compare the speed Im sure you will be happy. Search the Zeroxd thread for the person who recommended this and thank him.