Hello all....
First off...i appoligize if im posting in the wrong spot...kinda a newbie to this whole android world. I recently installed the cyogen mod 10,1 mod for my Telus Samsung 989d. I managed to get my it working right and my phones incredibly fast. The only issue is that my reception is horrible now. I'm not sure how to fix those so I thought I'd pay for ROM manager and get new ROMs directly from my phone but I can't find any stable ROMs. If anyone knows what I'm doing wrong or can explain how to fix it..please let me know.
Thanks!
not easy to get a Rom
Well as i understand your problem is that the ROM is reducing your signal.
I think you should either search for a good rated ROM and till you find that i think you should restore your Stock Rom
I know that stock isn't that cool but still you will get a good signal
Hit thanks if i helped
Yeah, you need either to change the ROM or restore the stock ROM if you feel that this ROM makes your signal reception worse.
mahmoodinho said:
Well as i understand your problem is that the ROM is reducing your signal.
I think you should either search for a good rated ROM and till you find that i think you should restore your Stock Rom
I know that stock isn't that cool but still you will get a good signal
Hit thanks if i helped
Click to expand...
Click to collapse
It just sucks that every ROM I try doesn't work. Is there any websites which allow you to search for ROM by model and carrier ?
I recently update my kernel and rom. I am now using the Infamous rom and kernel. I am still having problems.
When I place or receive a phone calls It starts out good and within a few seconds it starts breaking up. It sounds like I have poor signal but I have 3 to full bars and the other person has good signal. I can put it on speaker phone and have the same problem. When I first got the phone it worked great, But flashed a kernel ( not this one another one ) and it started doing it after that. but like I said I've flashed the Infamous kernel hoping that would take care of the problem but it continues. Ive also tried several other roms.
I found a new touch wiz rom on XDA just now and am going to try that one.
Should I try a STOCK rom and Kernel ? if so can someone please send me link to where I can get the STOCK rom / kernel from
any ideas would be greatly appreciated!!
Thanks !!
Hello friends.
I am new to this wonderful community and very happy to be a part of it.
I am facing a very strange problem. I am trying to update my WT9i Live with walkman from Gingerbread to Ice cream sandwich. Problem is .. whenever I flash an ICS rom my touch doesn't work !! Everything else works fine (physical keys / network / audio). Then if I install GB rom again it works flawlessly.
I have unlocked bootloader.
I am using Flashtool to flash stock roms.
* WT19i_4.0.2.A.0.58_(1254-1868).ftf = works
* WT19i_4.0.2.A.0.62_(1254-1889).ftf = works
* WT19i_4.1.B.0.431_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_CUSTOMIZED CE3 WORLD I 1254-1889.ftf = touch doesn't respond
I have no idea what could be the reason. Any GB roms works smoothly. Any ICS roms bricks the touch screen. I have tried custom kernel (mesa .. kappa) and many custom ICS rom .. same problem. But at any moment I flash GB rom .. everything works.
I did all the research I could (for last 4 days) and read many threads .. tried many things. Nothing helped.
Please help me! Please Please Please.
I have seen many threads with problem "touch does't work because of flashing wrong rom or kernel".
I don't think that's my case. Because whenever I flash a stock GB rom .. it works just fine. Problem happens with ICS roms .. custom or stock.
I am going to try some custom GB rom with custom kernel. I'll post if that works.
This thread is most likely my last hope of finding a solution .. please help!
Just out of curiosity downloaded the 587 ICS generic rom from flasstool website then flashes it .. same touch problem.
Now downloading latest Nightly CM10 coconut. I'll try it. CM 9.1 stable did not worked .. same touch problem.
Please Help ! I dont see a clue ! Why ICS roms would freeze my touch when everything else works? I am on the verge of throwing my phone out of window !!!
Latest CM10 Nightly build = same problem .. touch screen is not working.
Flashed Stock GB = everything is fine !
:crying::crying::crying::crying::crying:
Now I am downloading every regional roms of stock ICS .. its all I can think of.
I know its a very old phone and update / development for it completely stopped. Its forgotten. Still I love this little cute handset and I would love to get ICS on it (for app support .. many app do not work on GB .. like google chrome).
So please help !
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Pixelado said:
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Click to expand...
Click to collapse
Hello. Thank you for replying. Its a second hand phone .. my brother purchased it from a friend then gave it to me. So it may have a replaced display or digitizer. I just checked with my brother and he said his friend never repaired the phone.
So GB and ICS use different digitizer drivers? Is it possible to use GB touch drivers with ICS?
No idea. Your problem is truly rare haha.
I'm out of ideas here, most of the time flashing a stock ftf does the trick, but not here.
if I were you, i'd sell that phone to someone who woulndn't care about software updates hehe.
Hello Friends.
I am posting this in case someone else face the same problem and find this thread. In my opinion ..this is a very rare and strange problem.
This problem should never happen with an original handset.
If your touch only works with Gingerbread stock roms and even after complete wipe other stock roms freeze your touch .. then you can be sure that your touch was replaced with a cheap one. Go to a servicing center and replace it with a good touch or sell the phone to someone else who doesn't care about updates.
I went to a servicing center today and replaced my touch. Now it works smoothly with stock ICS rom. I am sure it will work with CM too. It costed me around 25$.
1 tip to recognize low quality touch. Low quality touch will not have transparent bottom-left and bottom-right button. You wont be able to see the key lights through it. Good quality touch will have transparent button. Another warning .. after market touch is most probably not scratch resistant like the original touch .. so you may want to use a good screen protector (plastic film) on it.
This is not only for WT19i. Whenever you buy a secondhand set .. make sure its touch wasn't replaced and best to check if its upgraded and working properly.
Thanks to "Pixelado" for hinting me about the replaced touch issue. Then it made sense to me .. there was no other logical reason for the stock rom not working.
I am very happy with my upgraded ICS But kinda sad about the money loss ! Anyway loss is loss. This is a good handset and I hope it will serve me good. Now looking for a way to root it.
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Pixelado said:
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Click to expand...
Click to collapse
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
I've never tried mesa, so no comment there. Quie frankly, rage 3.2 seemed to be all i ever needed when using a stock rom. I tried lupus, but stopped using it when they switched from CWM to TWRP.
Angelina7 said:
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
Click to expand...
Click to collapse
i have same problem too
can u solve this problem?
hello every one
proximity sensor of my s3 works continiously on secret menu it shows PROXIMITY:1 ADC:0(0.0.0)
i did every think
flash other stock roms upgrade and downgrade
cleane sensor
recalibrate with many methodes mentioned it stops for few minutes but retunes to work
is it a hard or soft problem
what is the solution a ccording to you please help
any solution ???,,
i am still waiting for your help
Rom or kernel issue.
Stick with the roms that work for you.
Darke5tShad0w said:
Rom or kernel issue.
Stick with the roms that work for you.
Click to expand...
Click to collapse
but because of somme bugs on somme roms i hated my s3
stock roms always are full working
i installed my stock roms on other I9300 phones it didn't cause any problem
i think that the problem is similar to 'not registred on network' issue
:good: thank you for your responce i thinked that no one will anwer me
thank you again
problem remains
i have edited the post because i observed that even with custom rom it works some hours and the problem returns
Hello everybody
I think that the problem is sloved but i am in test period
I cleaned hardly the sensor till i scared that it is broken definitivelly now it is working
And i test it
I will update if any news .thanks
I own a Galaxy S4 I9505 device.
Earlier I was running the stock based Custom ROM (Imperium 16.1, Android 4.4.2) on my S4 and there was no problem at all. That ROM gave me supreme performance, stability and battery life.
And then official Lollipop (5.0.1) was released by Samsung. I flashed the latest stock based custom Lollipop ROM on my device and the problem started (or may be the problem started because I have dropped my device once).
Now what happens is ... after I flash a ROM everything is working fine. But then after some uncertain period all the sensors stop working on the device.
Sometimes the issue is resolved by a simple restart, at times I have to clear the Cache and sometimes I have to clear the Cache and Dalvik Cache**.
All the sensors start working and after some time suddenly, all the sensors stop working.
I have tried all stock based Custom Lollipop ROMs and even AOSP based Lollipop ROMs, but this problem is persistent with all the Lollipop ROMS.
I have even tried Original Lollipop Firmware (flashed through odin), but the problem persists.
I open the back-cover and tightened all the screws, thinking it could resolve the issue. But the problem persists.
I am not able to decipher if this is a Software or Hardware issue.
Can anyone help me on this? Has anyone faced this type of problem? :crying:
I am not sure if this is the right place to post such a question. If it isn't please guide me to a proper thread.
Thanks
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
radz.min said:
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
Click to expand...
Click to collapse
@radz.min thanks for the screen shot .... you think it could be a hardware issue ... but as i mentioned .... sensors work good for half an hour or so and then they stop working ... if it was a hardware issue ... it should not work at all .... right ??