Dear friends, I must confess, I am romManiac, it is my way to describe myself and my constant need for trying every ROM in outer space, flashaholic is the old word for that and I needed something fresh, I just to do that since I got G1 back in 2008 I think.
My last attempt was last night when i decided to flash persist.img, because I was suspecting that my sensors messed up, but now I have to confess to myself that in every custom rom Pie based, I have a strange problem during the calls, even after flashing persist.img, I feel strange vibrations during the call, my display would not come back after or even during a call, if I want to switch to video on viber or similar. Am I really hitting the wall here, it does not happen in MIUI. And finally when I finish the call and turn on my display I can see that notifications are pulled down for some reasons.
Does anyone else have similar problems during using our beloved RN3.
I am using latest Havoc 2.2 on RN3PRO.
Thank you in advance my friends.
Hmmmm, I wonder after so many days of trying to find a solution, does dt2w can give me this kind of trouble, maybe it registers my ear as a finger hahahahahhah, I am serious.
dejson said:
Dear friends, I must confess, I am romManiac, it is my way to describe myself and my constant need for trying every ROM in outer space, flashaholic is the old word for that and I needed something fresh, I just to do that since I got G1 back in 2008 I think.
My last attempt was last night when i decided to flash persist.img, because I was suspecting that my sensors messed up, but now I have to confess to myself that in every custom rom Pie based, I have a strange problem during the calls, even after flashing persist.img, I feel strange vibrations during the call, my display would not come back after or even during a call, if I want to switch to video on viber or similar. Am I really hitting the wall here, it does not happen in MIUI. And finally when I finish the call and turn on my display I can see that notifications are pulled down for some reasons.
Does anyone else have similar problems during using our beloved RN3.
I am using latest Havoc 2.2 on RN3PRO.
Thank you in advance my friends.
Hmmmm, I wonder after so many days of trying to find a solution, does dt2w can give me this kind of trouble, maybe it registers my ear as a finger hahahahahhah, I am serious.
Click to expand...
Click to collapse
May be u kept option enable - vibrate every 5 minutes.
Or may be dt2w enabled causing it.
Related
As mentioned above, Will you brick your HD2 if you keep flashing new ROM or Keep installing Android for many times?
Because recently i keep trying new ROMs and keep installing Android on my HD2... then call history or missed call record didnt keep in the phone everytime i make call or receive missed call, even i switch back to Window 6.5.
Numerous installation will it destroy your HD2???
If i understand this correctly .. the answer is a VERY easy.. and resounding..
YES!!!!!
Ok now that the scary part is over.. let me explain why.. just like your battery can only be charged and discharged a certain amount of times.. your memory system can only be written and overwritten a certain amount of times...
Now first of all this amount might be 10,000,000 or it might be 10,000 or even a grand.. and there is really no way of knowing when it will finally just be a corrupted system that cannot be written on anymore..
But here once again is ANOTHER catch.. every time you call or text anyone it saves stuff into your phone.. call logs texts messages.. navigation settings gps position.. camera settings and pictures.. location settings from roaming even antenna search and location just from walking around your block.. or hell even sitting still and satellites moving out of range and antennas resetting there position of incoming information signature....
SO
Yes.. you can only write and re write a system "x" amount of times.. but reality is.. someone on a stock rom who has never flashed a single thing.. who is on market place alot , traveling alot.. taking lots of pics.. ect.. has probably approached this threshhold closer than you have.
And
Since we dont know it it will handle 1,000,000,000,000,000,000,000,000,000,000 megs of re write or 100.. there really isnt any point in worrying about it.
P.S.
Your ps3 remote.. will eventually stop charging.. your hardrive on your laptop will eventually crash.. your ipod will eventually be useless.. your dvr will eventually quit holding movies.. get where im going here? ReWriting damages stuff.. but we have NO way of knowing how much.. and youll probably upgrade before you ever have to
Well-explained bro! Thanks for that... But i assume there are lot more ppl keep flashing new ROMs and androids to test each amazing development!
What bout you? ROM addicts? LOL...
But weird enough, my call logs dont keep records anymore! Any idea that i could solve this problem?
whizzkid_cool said:
Well-explained bro! Thanks for that... But i assume there are lot more ppl keep flashing new ROMs and androids to test each amazing development!
What bout you? ROM addicts? LOL...
But weird enough, my call logs dont keep records anymore! Any idea that i could solve this problem?
Click to expand...
Click to collapse
If you mean it doesnt keep between flashes.. PIM is getting more and more useless and they need to either update or i think the lot of us are going elsewhere.. there are alot of solutions.
I used to be a rom addict... now im a hardreset addict.. which i guess is almost as bad.. but it seems most roms have hit a wall where the updates are person specific.. so it there isnt something in the log i want .. i just let it pass.. for instance i cant see moving from energys 216XXX rom for a while.
I'd just keep on flashing by heart.. What you are probably aiming for is called 'wear leveling', which indeed means blocks on the memory can be written a finite amount of times.
However, I believe that even with flashing your device daily, it will most likely not fail until you have had your new phone 2 years from now..
And IF it fails because of bad blocks, just send it in for repair.
BLAST3RR said:
I'd just keep on flashing by heart.. What you are probably aiming for is called 'wear leveling', which indeed means blocks on the memory can be written a finite amount of times.
However, I believe that even with flashing your device daily, it will most likely not fail until you have had your new phone 2 years from now..
And IF it fails because of bad blocks, just send it in for repair.
Click to expand...
Click to collapse
I just got my HD2 for 2 months and i have been flashing for umpteen times... It is just fun to see how the cooked ROMs like, any new features... Then now i started to feel my HD2 is sick already... Keep freezing and now all the call history doesnt record, such as call out, receive call or even missed call!
Then i do a Hardreset... Still no use... Any idea??
Flashed 1 too many times..
I have been flashing new roms to find out which one helps android run best and I bricked my TMOUS HD2. White screen with green htc letter. I can get to the Hard reset menu but I'm not sure what or where to go from here. Any advice? Thanks.
Jremy said:
I have been flashing new roms to find out which one helps android run best and I bricked my TMOUS HD2. White screen with green htc letter. I can get to the Hard reset menu but I'm not sure what or where to go from here. Any advice? Thanks.
Click to expand...
Click to collapse
Hardreset menu, did you press volume up to restore the factory default setting?
could try a task 29 too
so lets get this right if i flash it 100,000,000,000,000,000,000,000,000 time it will bugger it up maybe....bugger only 99,000,000,000,000,000,000,000,090 times left
your call history thing is probably android related.....
mine was screwy the first time I booted back to wm...
some info was still there but it wouldn't store anything new
turned out that the date was set to 2011not 2010, check that....
Tried task 29, but failed to do so.... It hanged on black HTC screen with percentage bar... what should i do next to save my lovely HD2??? :`(
I have having issues with the haptic feedback. It will work most of the time when I first unlock the phone, but it will randomly stop working as I am using it. An example is when I am typing a text message. the haptic feedback will work for the first couple of words and then it will just stop. Then all of the buttons on the bottom will not give haptic feedback also. Sometimes when I lock it and leave it alone for a minute it will work again. I do have it enabled in the settings. I have tasker installed and I thought that could have been messing up so I uninstalled it and it is doing the same thing. I even did a factory wipe and left everything uninstalled to make sure it wasnt any of my apps messing it up and it still did it. Is anyone else having issues? I am trying to see if there is something wrong and if i need to try and get it replaced. It is rooted and I have the telsa rom on it right now so I want to make sure I am the only one having issues before I unroot it and take it to Verizon. I have also tried it on different roms and kernels and it does the same thing. Thanks
If you are using any kernel other than stock you will have this issue, they all do. Same happens with me on the TB and happened to me on the Incredible, don't know why or what causes it, but it happens.
yukongt300ex, you have just described exactly what I have been experiencing with my Thunderbolt (in fact it has just done it while typing this post) and I'm running stock Sense..
Does anyone have a fix for this?
That is strange. I figured more people would be complaining and we would be hearing more about it if it is that common.
Yet another reason I cant wait for cm7!
yukongt300ex said:
That is strange. I figured more people would be complaining and we would be hearing more about it if it is that common.
Yet another reason I cant wait for cm7!
Click to expand...
Click to collapse
I think most of TBolt owners have the haptic feedback turned off
And soon as I get use to it not providing any feedback, it comes back... it's just teasing me lol
the same exact thing happens to me. in the middle of texting, the haptic feedback will just shut off throughout the whole device, including the soft keys on the front on my thunderbolt. i've found the stopping if usually triggered by me typing too fast for the thunderbolt to handle. for instance i'll type 3-4 words it won't register, then all the haptic feedback with come at once in one super long vibrate, and then it just shuts off for good, until i put the device to sleep for 5-10 minutes. then repeat -__________-
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
Right guys, I have been on the Original Development section asking similar questions and had good suggestions, but here is the problem in a lot more detail as I don't want to spam the section with the same problem and get literally no reply as people are busier with other things on there. Basically the phone has it's two speakers, the earpiece at the front and the speaker at the back both of which are working and functional. However the problem lies in the phone calls. I bought the phone on stock firmware, latest UK generic update it was and everything was fine. I decided to root the phone and flash PA 2.13.1. As soon as I did this I came across a few issues, one being NFC not working and the current and seemingly unfixable issue that I have with the phone calls where, as I receive a call and answer it the microphone doesn't work, I can't hear anyone and they can't hear me. Both on loud speaker and through the earpiece. It's as if they disable when a call comes through. But when I hang up or they hang up I can hear the end call tone, the beep coming through the earpiece. So I know that it works. The same goes for loud speaker, however I already knew that it still worked as I can play music through it cleanly. It's in perfect working order.
I've tried several solutions, including flashing new modems, RIL etc. Flashing 3 part software. I have yet to try flashing the 3 part software with a .PIT file, like mx.pit as I simply can't find that file (if someone would be as kind to link me it) anywhere. I'm currently back on stock XXALE8 UK firmware. The problem is still there. I STILL can't make a phone call without this annoying thing happening, and as I said, the problem wasn't there before I flashed PA. It's so f****** annoying as I followed the instructions perfectly, I mean, I've been using android since 2009 and rooting and flashing is nothing new to me. I've never had an issue as severe as this one.
Anyways, thanks in advance for any suggestions you guys can throw at me, I know you'll all agree when I say the GS3 kicks ass and you'll know my pain when I tell you it's being a broken piece of crap haha!
EDIT: Right, I have made another definite discovery with this problem! It's to do with my signal. When I answer a call or make a call, it appears to connect to the caller for roughly about 0.01 seconds as it says it's connected, but then it hangs silent for a while, about 13-15 seconds before disconnecting saying there is no service in the area. Give it another five seconds and the signal reconnects. It is the exact same effect you would have if you were on the phone on the train and went through a tunnel, it would say you were connected when you aren't. Does this make sense, anyone know what the cause of this could be?
Hello,
My problem is very weird and i couldnt find any solution for it yet. Some time ago when someone was calling me i couldn't hear the voice and the caller couldnt hear mine, when i turned speaker on it was all fine. I tried to work it out by installing and uninstalling certain things in the phone and'ive come to the stage where if i try to call someone or someone calls me my phone freeze (nothing can be done) and then restart itself.
My current ROM is latest nigthly CM 12.1.
What could possibly cause this? I wiped everything possible like 3 times already, made factory resets, installed rom again and again, nothing helped..
EDIT: Ive tried installing different ROMS, CM11, CM12.1, Stock Rom, still same issue.
Loading the backup (5gb) of the phone before flashing it and doing all the stuff didn't help...
I had a similar issue on my old S4. Turned out to be one too many "drops" by my baby, cracked the circuit board behind the glass. This caused issues with calls not going through, cant't hear people, it disconnects by itself, sporadic reboots, some force closes, and eventually me trading it in for the S5..lol That was my 2nd replaced board in that S4 in as many months. Needless to say, my daughter does not play with daddy's new phone any longer..lol That was my experience, hope it helps. Good Luck!
Thanks for the answer, but unfortunatly i treat my phone pretty good and it would be a big coincidence if something mechanicly broke inside it, as i said it happened the same day as i uninstalled Hangouts and something else with Root App Deleter...