I noticed that camera etc. wasnt rotating so i've checked the g-sensor calibration and the bubbles arent moving so im dreading that it's a hardware fault
im running RCMix3d Runny v4.0
is it possible it is just a software problem and if so
has anybody else had the same problem and fixed it ?
enable auto-rotation
I thnk u would hav disabled that
auto rotation is of course enabled when i try to calibrate the g-sensor in settings the bubbles arent moving could this be a kernal problem ?
I was abt to say tat! But u figured it, Yea juz reflash the kernel
That should do well!
reflashed a different kernal no luck
also my usb isnt recognized when i plug my phone into the computer what a nightmare last time i trade phones with anyone
Cool man...ask tpbklake he is good at these.. i thnk u knw him..
Sent from my HTC Incredible S using xda premium
It sounds stupid but give your phone a good shaking and try again.
Tried that there bubbles still aren't moving I'm fresh out of ideas any more ideas be nice
Also I'm getting an error saying USB not recognized when trying to connect the phone
To a computer
you better reflash ur rom! Have a full wipe and let us knw the state of it
I did a full wipe and reflashed still no luck I'm gonna have to flash a stock Rom see if it works ill let you know the results
k try it..i think it's a hardware problem, first get ur usb working!
any luck? i am experimenting G sensor problems after i flashed OMFGB ROM
I'm going to assume it failed so he reverted to s-on and returned the phone.
ptda said:
any luck? i am experimenting G sensor problems after i flashed OMFGB ROM
Click to expand...
Click to collapse
I flashed the new ics rom and my sensors started working again ha
dont ask me why or how they just did then i flashed back to nikis rom and they were still working !
Related
Hey guys,
I upgraded my G1/Dream from an older cyanogen version, to the newer one 4.2.15.1
and now for some reason my phone keeps restarting Any reason why ?
Can you please tell me how to fix it?
I've taken battery out & Also 'green+home+red' . Same keeps happening.
It restarts when it wants, can be 2 minutes, 10, 30.. but lately ever 1 minute or so..
What can I do?
Bump
bump
Anyone?? please
I'd recommend a full wipe and reinstall of your desired rom from scratch. Sounds like kernel panics to me.
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Tone-E said:
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Click to expand...
Click to collapse
Why would you completely unroot and reroot? That's just too much work.
Wipe, and reflash. Also, a few apps have a problem with custom ROMs, try disabling apps that run in the background one by one until you find that your phone no longer reboots.
However, if you didn't wipe, I highly recommend that as the person before me said.
Hello
after several flashing between different roms and to stocks
I nothing can play out of the speaker !
after several tries of flashing things, I did fix it
but the rom that I flashed to isn't good
so I flashed to Cognition 2.2 beta 7 and the sound gone
flashed back ... same thing .. no sound at all
I flash to every possible file but no luck !
any suggestions ?
AhmadAlmousa said:
Hello
after several flashing between different roms and to stocks
I nothing can play out of the speaker !
after several tries of flashing things, I did fix it
but the rom that I flashed to isn't good
so I flashed to Cognition 2.2 beta 7 and the sound gone
flashed back ... same thing .. no sound at all
I flash to every possible file but no luck !
any suggestions ?
Click to expand...
Click to collapse
Flash back to stock using Odin one click then matser clear through Odin. After your phone reboots go into setting and perform a factory reset Setting/Privacy/Factory data reset. After that flash to your favorite ROM and see if you have sound again. This meathod worked for me when I had the no sound issue. Don't forget th Jh7 update through Kies mini.
climber1872000 said:
Flash back to stock using Odin one click then matser clear through Odin. After your phone reboots go into setting and perform a factory reset Setting/Privacy/Factory data reset. After that flash to your favorite ROM and see if you have sound again. This meathod worked for me when I had the no sound issue. Don't forget th Jh7 update through Kies mini.
Click to expand...
Click to collapse
I really appreciate your response
I'm on JF6 (2.1)
Tried to update through Kies mini ... but it shows the Firmware Version as "Unregistered device" !
AhmadAlmousa said:
I really appreciate your response
I'm on JF6 (2.1)
Tried to update through Kies mini ... but it shows the Firmware Version as "Unregistered device" !
Click to expand...
Click to collapse
Run a search in the captivate forums for unregistered device. I remember reading a fix for that, just don't remember which sub forum it's in.
It didn't solve the problem.
BTW, I didn't mean the "receiver" where u can hear calls...
I meant the loudspeaker !
I figured out what the problem is !
have u ever found ur coke can stuck at the machine ! what is the last solution ?!
kicking it ... real hard, huh ? ... that's exactly what I've done
I started shacking the phone .. hitting it with onto my palm... TADA .. melodies start flaying
thnx for ur suggestions tho
AhmadAlmousa said:
I figured out what the problem is !
have u ever found ur coke can stuck at the machine ! what is the last solution ?!
kicking it ... real hard, huh ? ... that's exactly what I've done
I started shacking the phone .. hitting it with onto my palm... TADA .. melodies start flaying
thnx for ur suggestions tho
Click to expand...
Click to collapse
Huh. I guess it was a hardware defect. I'd be sending that sucker back to samsung for an exchange.
AhmadAlmousa said:
I figured out what the problem is !
have u ever found ur coke can stuck at the machine ! what is the last solution ?!
kicking it ... real hard, huh ? ... that's exactly what I've done
I started shacking the phone .. hitting it with onto my palm... TADA .. melodies start flaying
thnx for ur suggestions tho
Click to expand...
Click to collapse
lololol IT WORKED ! Thanks.. shake shake shake, shake shake shake, shake your cappy
Yes there was a technician that posted the fix in a thread I was reading. He said to take the battery out and "thump" the area under the battery with your finger. Insta-fix, lol.
HAHAHA This is too funny! I actually had the same thing happen to my cappy!! I as I am sure everyone else on this forum tried all the techie fixes and flashing solutions and it ended up just requiring a simple thump! you gotta say it's kinda funny
It's a very odd one in landscape they light up, in portrait mode they don't. Well, when I noticed that problem I immedeately flashed framework-res.apk - didn't fix so I remembered when I went to recovery they did light up, so did I and started counting seconds while it loaded into it but they didn't light up. So is this some kindo of physical damage? Landscape uses obviously different LED's, it ruins the niceness from that phone, when bottom bar is dark At the moment i was using Nik's Trinity 2.0 rom and i'm using it so far.
Can you guys provide some help, it will increases my love to the phone substantially.
Therefore my phone will be shiny and elegant again!!
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
owziee said:
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
Click to expand...
Click to collapse
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
tpbklake said:
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
Click to expand...
Click to collapse
Yes, but they worked in recovery earlier
henrylife said:
Yes, but they worked in recovery earlier
Click to expand...
Click to collapse
When you boot in recovery, it is not using the custom kernel that your ROM is using. In order to rule out hardware, you need to check the phone using the stock HTC IncS kernel and a stock ROM.
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
henrylife said:
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
Click to expand...
Click to collapse
get back stock to test whether it is working,cm7 wasn't stock though..
Sent from my HTC Incredible S using Tapatalk
Don't lose root.... newest stock will up date your h-boot
I don't want to know to stock I know how these lights work. They depend on framework-res.apk and on kernel. Ok well stock may change but it's 5% reasonable. Is there some kind of diagnostic tool out? A fastboot one will be great.
UPDATE: 2 days ago I used my phone as router and it was charging, so yesterday I did disconnect my phone and saw lights worked. While in bus they started blinking
(like dying bulb) and few minutes ago i barely saw them and then everything was dark again. Sometimes they get revived for some time and process is under loop again
I'm trying to remember, it occured after attempts to get it charge, Incredible S usb dock doesn't work properly so i crumpled it a little bit and finally it turned on. First notice were the lights, and after heavy charge they got somehow revived. I want to see this panel with my own eyes, can someone put disassemble guide please?
I'm pretty sure new backlit is quite expensive but unfortunately Physical damage it is.
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
uggies said:
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
Click to expand...
Click to collapse
Nah, it shouldn't
Hello all,
I attached a log file which i hope, i BEG someone can help me with.
My camera wont open, i click the camera app and the screen goes black then i get a force close message, or a message saying cannot connect to camera. Sometimes the app opens and i get the cannot connect to camera message and sometimes it just force closes with a black screen.
I am on the stock 2.3.6 rom. i have dskchked the sd card, formated the sdcard and started over, tried different camera apps.
Attempted a different rom but i cant seem to get the drivers to see it when i start in fastboot USB mode. :-(
Can anyone tell me whats up?
Thank you
I really miss camera :-(
Well, since you said you already flashed a differenct ROM to see if it would help I'm going to assume it was something you know is stable like cyanogen or a stock ROM so it should work but just in case if you haven't already I would try passimg. Now you haven't done any radio flashes lately right?? Although from what you have said I think it may be hardware failure :/
Thank you for your reply, no i havent its on the 5.08 radio i believe, its changed to the defualt stock when u OTA right? i lost the works when i did an OTA to stock 2.3.6. I have just put recovery back on. i had CM7.1 before and it wasnt working, but it was working before that on stock 2.3.6. If you can picture that timeline. I thought reverting to stock would fix it. but apparently not.
Ok well when you reverted to stock did you use passimg? if not then I would give it a shot but if that doesn't fix it then I think it's a hardware failure sorry :/
I just flashed GRI40 using recovery then OTA to 2.3.6.
Is that any different to passimg??? im not sure of the difference?
Well it's because passimg by default makes a flash to every partition so it will wipe everything and put it all back in flashing a ROM on the other hand just does the system partition.
right... sounds interesting... can i passimg over the most current version... as im on the latest now... Or will it just say its up to date?
No unfortunately the most recent passimg file is frg83 so you'll need to use that but if it works then after that you should be able to flash anything you want and have no problem. For the instructions just check my sig.
worth a shot i guess... i just apply the froyo passimg and it just instal over 2.3.6, then it will naturally OTA to the latest again...? u recon it will work? shame their arent more people confirming this... its a lot of work!
passimg solved the touch pad buttons at the bottom problem i had of them not lighting up, unfortunatly the camera is still not working
alphecca911 said:
passimg solved the touch pad buttons at the bottom problem i had of them not lighting up, unfortunatly the camera is still not working
Click to expand...
Click to collapse
well if it was working perfectly before
than if u can open ur phone check all connections or go to some repair shop and get it done,
this might solve the problem.
this solved my camera FC problem
http://www.ebay.com/itm/31037916447...X:IT&_trksid=p3984.m1497.l2649#ht_1535wt_1185
As we all know by now the official 4.3 came out for the xperia T which was de and rooted, i installed it on the my xperia tl following the step by step instructions on the thread, everything works smooth for a while until the screen standby. when it does and im trying to unlock the phone the touch doesnt respond, i press the power button and tired again still nothing, pressing the power button several times and then the screen start pressing random things on its on activating and deactivating settings task bar is being pulled down etc then the touch start working and im able to use the phone until the screen time out and it happen all over again. i switch back to the 4.1.2 and i have no problem at all with it but im jus curious has anyone of the tl users experience this problem and is there a bug for us on the 4.3 and or if there is a solution ? please help me cause i love the 4.3 but hate the problem i have with it
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
St.Jimmy90 said:
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
Click to expand...
Click to collapse
i tried all that .. i also wipe cache and those other things . are u using a TL also?
No Xperia t
i need to know if any TL users are having this problem
I'm on a TL with official 295...everything works for me like it did on 4.1.2
Sent from my LT30at using xda premium
Did you try if reinstalling solves your problem?
St.Jimmy90 said:
Did you try if reinstalling solves your problem?
Click to expand...
Click to collapse
i tried everything i did it over from the begining with a stock 4.1 firmware from att and then root install cwm 8 wipe cache and factory reset and wipe the dalvik install rom and then update superuser right after . then reboot . when it loads it works perfect for the first few mins then something got activated and thats it the screen jus went crazy it start jumping and touching all over the place and then stop .
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
silasje1 said:
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
Click to expand...
Click to collapse
i dont think the screen protector has anything to do with it because i would have had the same problem when im on 4.1.2 because i did remove my factory installed sony screen protector aswell. i really believe its the firmware or module or drivers .what ever it uses to control the touch
i think i might find the problem, well atlease for my device ... my usb port is acting up when ever i plug it in anything wall charger or pc is freezes and i also disable to slide to unlock and set time out to 10 mins .. idk if this works for anyone else but ive been on it for 30 mins now and nothing has gone wrong so far
I must confirm that removing the screen protector makes the screen touches working a little bit worse, because the glass gets easier oily. It's even more worse, when usb charging is connected. Cleaning the glass makes it better again.
No issues
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
gpgon said:
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
Click to expand...
Click to collapse
i didnt know 8 was buggy i thought it was most stable .. ill try 6 .. thanks
i tried 6 .. its the same s**t so im done with this im jus gonna go back to 4.1 i cant deal with this anymore ive been trying for days to get this to work properly and its not like im a complete noob cause i came from the x10 so im quiet familiar .. so thanks for all ur help guys but im done with this