Hi guys. Yesterday I flashed Latest Kumara WM6.1 ROM. But now one big problem i have. Backlight is Ok after 30 sec, but LCD can not turn off automatically. Then Battery is going down very very fast about 3 hours.
How to fix this problem, help me guys....................................
Maybe ROM's problem...
I think maybe the ROM you use (last upgrade) got problem. If you wish, try to upgrade another ROM and see whether still got the same problem or not. The new rom I using now (refer my signature) is quite stable, you may try it.
You can search this rom from this website. Good luck!!
Related
I can't load android on my HD2 with enegy rom, can anyone suggest me anything. I even master reset my phone and do all the step as told. still when i try to load android camera flash flash one time and then white and black stipes on the screen. Please give me a solution...
rom version 2.08.50.08_2
13.sep.2010 wwe.
This is my first time doing this.
Welcome to the forums
Have a deep read @ this instructions.
Also have in mind that some Android builds have problems with camera.
milon.shabbir said:
I can't load android on my HD2 with enegy rom, can anyone suggest me anything. I even master reset my phone and do all the step as told. still when i try to load android camera flash flash one time and then white and black stipes on the screen. Please give me a solution...
rom version 2.08.50.08_2
13.sep.2010 wwe.
This is my first time doing this.
Click to expand...
Click to collapse
Did you mean radio rom. I think best radio for android is 2.12.50. I have been using android for some time and I have energy. Rom 13 Oct.version ifs working beautifully. Tell me exactly. Where u r stuck
ive had 4 or 5 different android builds running on my energy rom.......
The best one has definetely been this one.......
Try another build because its very likely you've just picked a build that doesnt want to play nice..........
Android on HD2 Energy Rom not working.
Whatsup buds. I'm a tech guy just like yourself and I am putting android on the HD2. I flashed with HSPL3 and I wasn't able to get it to work as it was on the Energy Rom. I have the two files on the phone, the HSRAC and the other one when I load the first one, nothing happens, as it should as it fixes the robotic voice, but the other one brings the phone to the white screen with the Android guy... but it stays on that, have you had similar problems doing this with Energy Rom?
sahidmiah said:
Did you mean radio rom. I think best radio for android is 2.12.50. I have been using android for some time and I have energy. Rom 13 Oct.version ifs working beautifully. Tell me exactly. Where u r stuck
Click to expand...
Click to collapse
Thanks.
I treid this solution but it doesn't work completely. My phone freezes when I make calls. I must initialize or plug in to use it again.
I tried too with latest HTC ROM, HSPL2, HSPL3, MDJ Froyo 4.6 and Froyo Sens 2.4 clean.
conantroutman said:
ive had 4 or 5 different android builds running on my energy rom.......
The best one has definetely been this one.......
Try another build because its very likely you've just picked a build that doesnt want to play nice..........
Click to expand...
Click to collapse
Thanks,
Please can you tell me wich HSPL do you use. I tried many combination.
Evry thing is working well except the essential : my HD2 freezez after I make a call.
To use it again, I must plug in, restart or waiting for a call (??).
I just installed a fresh KPO stock and used Gslmt 2.1 as a custom rom.
See this thread for more info:
http://forum.xda-developers.com/showthread.php?t=1216700
Problem I am having is that the shutdown option does a reboot in stead of a shutdown. Does anyone else have this problem.
Couldn't ask this in the Android dev part since I am new to XDA. So hope someone can help me here.
Still SOD and WiFi problems
This Rom still gives me the SOD problem and my WiFi is shutting down randomly. So I'll install a different ROM this weekend.
Tried then all by now.
Anyone had SOD problems and got the definitive solution with a Custom ROM?
Please share!
djcasl said:
This Rom still gives me the SOD problem and my WiFi is shutting down randomly. So I'll install a different ROM this weekend.
Tried then all by now.
Anyone had SOD problems and got the definitive solution with a Custom ROM?
Please share!
Click to expand...
Click to collapse
People have been saying the new kernel removed the bug. Try GingerReal, haven't seen reports of SOD over there.
As for me I don't get it at all normally.
Hi Sergei !
I use DSC from beginning. It is the best ROM.
I just wt to ask
Until now I already update .64b. I have no problem with all troubles such as wifi,reboot,camera...
Which kernel I should install? the original with upd0.64b or DSC_teamXX or GXkernel...
Bz i got confused about many of kernel
I need stability and long life battery for normal using.
Anyway thank a lot for the DSC rom from yr team
Appreciated that
Larry
For 0.64b I used the kernel that was provided. Prior to that I used GKernel 1.5, since I never had any luck with using the GXKernels on my device.
Good day to you!
Stable kernel is always included in our ROM.
We provide and test different kernels, but only tested and stable version goes into release.
First of all.....
Like many of us, we just wanted a solid/stable custom ROM and I couldn't be more grateful for the fine work Greg and _n0p_ are/have been doing.
I love DSC above the rest, but I too have the Wifi freezes, and have them with nearly all GB-based ROMs.
However, when I first went to GB from DJ_Steve, I didn't have Wifi issues. Unfortunately, everything else went wrong, so I searched for a better ROM. Ultimately, I installed Longhorn, with the BB and kernal. At that point, I started seeing Wifi troubles. After that point, every GB-based ROM gave me wifi freezes.
I've been following and installing the DSC updates as you release them, and each time, the freezes come back.
Each time, I go back and re-flash the GXkernal1.0, and all seems right. I may get a freeze on that kernal at some point, but I haven't had one yet. The other kernal updates gave me freezes within a few hours of installation.
Sorry for the tome, but suffice it to say, IMHO, GXkernal1.0 has been the stablest kernal for me.
Thank you. You gave a new idea.
Hi Sergei,
Good news!
I am using DSC0.64b+kernel 2.6.35-14-DSC-Team-Phoenix+ from yesterday until now. So far it is fantastic. I have no FC, no reboot, no prbl with wifi...
I were supprised why many people get wifi prbl.
Anyway thank u and yr team for DSC.
Yes, I have the DSC-Team-Phoenix kernal in right now. Installed this morning, got a wifi freeze a couple hours later, but battery too low to flash back to GXKernal1.0. So far so good on Phoenix. I'll reflash GXKernal1.0 later when/if I get another wifi freeze.
But yes, got wifi freeze on Phoenix too.
Hi _n0p_,
I saw in yr build.prop has 1 line:
#wifi.supplicant_scan_interval=120 instead of wifi.supplicant_scan_interval=120
might be it cause of wifi problem?
When I change that line, i have no problem at all with all yr DSC roms.
Sorry if that is wrong.
Larry
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