Related
I guess what I mean to say I am sick of all these problems, with both stock and cooked roms, I just want a phone that works smoothly.
What I wouldn't give for ANY ROM that is reliable.
I have tried ROM after ROM, and I still have not found even one that is truly reliable. The stock ROMs, or ones close to stock are maybe better but not OK.
I am so sick of the slow HTC messenging client (I have tried the fix to disable it, but that doesn't work)
Even the regular windows messenging freezes.
In fact the phone seems to have a lot of fun freezing up all the time. It usually unfreezes after a while, but why would I want a phone that I have to wait 5 minutes for before I can do anything?
All I want is 1 reliable ROM. It doesn't have to be lightning fast, just something that doesn't waste my time.
It would also be nice to have something with a bit of cool graphics in it too, but that is not important.
I have read online about a lot of people having the same problems. Why can't we seem to fix this? I have a lot of faith in Xda-developers, so I know this can be done.
try cooking your own then maybe you'll see how hard it is to make a reliable rom. :|
Yeah, I don't mean to give any offense to the chefs, as I thank them for their effort, but I think the problem is deeper than that.
I just want to know what I can do? Or maybe how can I help to discover the root cause of these problems?
you know...i dont think its the ROMs...
honestly i think it's because the stuff that's on the phone (whether its a stock ROM or a cooked one)
it NEEDS more memory...
thats what i think at least...
well how can one build a ROM that is snappy and reliable?
Its not the RAM, its the Qualcrap MSM7200 processor. Same processor for 3 generations. Thats why.
Check my signature & words of Gandhi Ji, you will understand why we fail. Our greed always outgrows our technological developments & what we are left with in the end is nothing but frustration.
To be specific have shipped ROM & attain the nirvana.
Kind of same feelings here. I have been using modified ROMS and now I realized that some of my text messages don't go through to people. This is kind of bad because I already fired one person from our company because there was misunderstanding cause she never received the message but I didn't believe her cause I got confirmation from the operator that she got the msg
and JUST now the phone just suddenly went blank and now it says that has to reset the device completely. I didn't even touch the phone I just noticed that it had lost the wallpaper suddenly and then tried to reinstall the wallpaper didn't work. Then reset and the phone didn't get on anymore
Luckily after some waiting the screen came and said I can reset the device. Now has to reinstall everything again. Fuuuuck. Would have other things to do than this..
phony said:
I am so sick of the slow HTC messenging client (I have tried the fix to disable it, but that doesn't work)
Even the regular windows messenging freezes.
In fact the phone seems to have a lot of fun freezing up all the time. It usually unfreezes after a while, but why would I want a phone that I have to wait 5 minutes for before I can do anything?
All I want is 1 reliable ROM. It doesn't have to be lightning fast, just something that doesn't waste my time.
It would also be nice to have something with a bit of cool graphics in it too, but that is not important.
Click to expand...
Click to collapse
have u tried my rom. i think i got them all covered
let me know here y it wouldn foot ur bill
cheers
Maybe we should start a quest to find that one ultimate ROM that makes this thing into a phone we can rely on.
I bought this phone because I use all of it's features heavily, I text and email and call and view documents, and surf the web and listen to music and watch videos and more constantly on this thing.
For it to be unreliable negates all the good functions it has.
How about we all work on finding/testing one ROM that is priority #1 Reliable?
phony said:
Maybe we should start a quest to find that one ultimate ROM that makes this thing into a phone we can rely on.
I bought this phone because I use all of it's features heavily, I text and email and call and view documents, and surf the web and listen to music and watch videos and more constantly on this thing.
For it to be unreliable negates all the good functions it has.
How about we all work on finding/testing one ROM that is priority #1 Reliable?
Click to expand...
Click to collapse
lol...seems kind of a self defeating goal. Can there be anything such as the one perfect Rom when we each have our individual preferences and priorities? Also, we have to factor in the reality that the networks themselves are not reliable. So, if ATnT or Verizon drops calls and text messages, can we really say it is the Rom that is unreliable?
agent_47 said:
have u tried my rom. i think i got them all covered
let me know here y it wouldn foot ur bill
cheers
Click to expand...
Click to collapse
hehe, wonderful suggestion... but... this is the ROM I currently use and it has all the same sort of problems.
I really appreciate the ROM though, thank you for making it.
mcfarlan said:
lol...seems kind of a self defeating goal. Can there be anything such as the one perfect Rom when we each have our individual preferences and priorities? Also, we have to factor in the reality that the networks themselves are not reliable. So, if ATnT or Verizon drops calls and text messages, can we really say it is the Rom that is unreliable?
Click to expand...
Click to collapse
I was thinking of making one that can be the basis ROM from which all others are birthed. Or at least find what formula or tricks we could apply to make the ROMs better?
lawlz. Good Luck finding the 100% perfect rom.
If you look at each rom's thread, each new rom they release more likely has a new OS build. Then each new build has their own issues, either from previous version or new issue entirely.
IF the rom the chefs release is just plain unusable, they normally release a FIXED rom with the same build.
Known issues are just that, chefs normally don't fix them because they just can't. So hoping for a new build of the software might fix it.
Each of the roms' issues can be fixed with patches, there are general patches that can be found all over or a patch by the chef when they sometimes forget to fix an issue unique to their rom.
From what i've been noticing, no chefs has cooked up the same rom more than 5 times to fix some issues until it is 100% perfect. By the time they do that, there's a new build of the software and they'll be cooking that instead. Not only just the OS build, they'll also add/remove some programs, change programs to newer versions.
All of these combined will introduce new issues.
Then the cycle continues...
There's about 20 or more Rom selection out there that you can choose from. There's gotta be one that is close to your preferences.
A rom that is deemed 100% reliable to others may not be the same to you.
corepda said:
Check my signature & words of Gandhi Ji, you will understand why we fail. Our greed always outgrows our technological developments & what we are left with in the end is nothing but frustration.
To be specific have shipped ROM & attain the nirvana.
Click to expand...
Click to collapse
Well the shipped 6.5 ROM on the Tilt2 seems to have the same freezing problem according to countless reviews on the web.
f1ip said:
A rom that is deemed 100% reliable to others may not be the same to you.
Click to expand...
Click to collapse
Perhaps then we should deem what is reliable. Firstly, 100%, I know, is too much to ask for, but I want as close as I can get.
So reliability to me means: I can use the phone as it was meant to be used.
This means: no freezing, no need to reset constantly, when someone calls me I can see the caller ID, etc
Simple and easy.
Now is that too much to ask for?
phony said:
hehe, wonderful suggestion... but... this is the ROM I currently use and it has all the same sort of problems.
I really appreciate the ROM though, thank you for making it.
Click to expand...
Click to collapse
really???
phony said:
1.I am so sick of the slow HTC messenging client (I have tried the fix to disable it, but that doesn't work)
2.Even the regular windows messenging freezes.
3.In fact the phone seems to have a lot of fun freezing up all the time. It usually unfreezes after a while, but why would I want a phone that I have to wait 5 minutes for before I can do anything?
4.It doesn't have to be lightning fast, just something that doesn't waste my time.
5.It would also be nice to have something with a bit of cool graphics in it too, but that is not important.
.
Click to expand...
Click to collapse
1.i don have HTC clent cooked in to begin with.
2.source of sms hanging is the showcase suite, which is not cooked in
3.well i don share that with u
4.hmmm...let me think
5.hmmm...let me think
sorry i tried helping u out but i don think u are on my rom coz then u would know that leo sms client is not cooked in. nor is showcase suite
thnx for ur input though
Well there are Roms that are really reliable and very fast. I'm using the same custom ROM for a long time now... I never had to reset, no freezing. It just works.
It's more stable then stock even. Just search in the first 3 pages of the rom thread for the touch x roms.
So no it's not to much to ask. I think this thread should be closed because it's only about whining. Nothing constructive.
EDIT: and that's not the only ROM that is stable. And let me remind you that al cooks are doing it for fun and free willing. As end user you can't complain. You have no right. Asking and making requests is fine, but I'm getting sick of people saying nobody is listening or will respond on questions asked multiple times and awnsered multiple times. The same is for people screaming other people don't make them what they want while they have to knowledge about the subject at all.
This is not ment offensive in any way to anyone.
quarintus said:
Well there are Roms that are really reliable and very fast. I'm using the same custom ROM for a long time now... I never had to reset, no freezing. It just works.
It's more stable then stock even. Just search in the first 3 pages of the rom thread for the touch x roms.
So no it's not to much to ask. I think this thread should be closed because it's only about whining. Nothing constructive.
EDIT: and that's not the only ROM that is stable. And let me remind you that al cooks are doing it for fun and free willing. As end user you can't complain. You have no right. Asking and making requests is fine, but I'm getting sick of people saying nobody is listening or will respond on questions asked multiple times and awnsered multiple times. The same is for people screaming other people don't make them what they want while they have to knowledge about the subject at all.
This is not ment offensive in any way to anyone.
Click to expand...
Click to collapse
Well, as I said in the first few post, it is not the fault of the chefs, and I appreciate greatly all their efforts. I never complained about the chefs and their ROMS, it is the system itself. Perhaps I am asking Windows Mobile to be better.
It think it boils down to Microsoft building a system that is not up to par, then HTC trying to hack on their software which creates a system that is is inherently flawed.
I fully support and am grateful for all the custom ROMs out there. At least it gives us more interesting choices.
CandyAndy said:
Kind of same feelings here. I have been using modified ROMS and now I realized that some of my text messages don't go through to people. This is kind of bad because I already fired one person from our company because there was misunderstanding cause she never received the message but I didn't believe her cause I got confirmation from the operator that she got the msg
and JUST now the phone just suddenly went blank and now it says that has to reset the device completely. I didn't even touch the phone I just noticed that it had lost the wallpaper suddenly and then tried to reinstall the wallpaper didn't work. Then reset and the phone didn't get on anymore
Luckily after some waiting the screen came and said I can reset the device. Now has to reinstall everything again. Fuuuuck. Would have other things to do than this..
Click to expand...
Click to collapse
Wow dude you honestly owe her an apology. You sound like a total douche for ****ing up your phone and firing someone for it.
I'm just saying man, the rest of her life she's going to remember you as a douche for your own mistake.
i just got my touch pro 2, it was used, but it was still new
it still even has the original plastic on the screen.
ever since ive had the phone though, everything on it is really really slow.
opening up a text, sending a text, going back to the home screen, opening up opera, clicking on the notification tab. EVERYTHING is really slow, or has some kind of lag to it. Why is this happening? What can i do to fix it?
This is really bothering me, and im about to trade for another phone because i cant take it. It takes me 5 minutes to send a text message, after i hit the send button.
ANY help is appreciated, thanks!!
First thing you want to check is which ROM is running on the device. Is it stock or a cooked ROM. Which version TP2 do you have? is there a carrier logo on it? The more information you can provide about the hardware/software on the device the better we can help you.
its the stock ROM. Original T-Mobile branded version. Its pretty much new out of the box it seems.
Since you just got it, and someone may have been using it before. i would suggest hard reset first off to remove any junk the previous user may have installed.
ok thats sounds like a good idea, how would i go about it?
(sorry for some of the questions i have been / will be asking, i just came from android to WinMo, so im completely lost)
1. While the HTC Touch Pro 2 is off, press and hold Talk/Send, End and Power until you see a message on the screen about deleting all data.
2. Release the buttons after the message appears.
3. Press the Volume Up button.
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
nayr1482 said:
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
Click to expand...
Click to collapse
The T-mobile stock ROMs do not have push pages and as such I do not believe it makes use of the Dynamic Proxy.
I came from an Android device (briefly, in between my Wizard to Rhodium). The screen itself is different. This may be part of the lag you are experiencing. I actually prefer the WinMo platform over the Droid one, as it feels more responsive and stable to me. My friends however, who have the the G3 or iPhone hate my Rhodium...so again, I suspect that if, after hard booting your device, it still feels laggy, it may be the differences in how the screen responds versus a Droid screen. The Devs here could explain it in much better techie terms than I.
There is a thread here pushing for a Droid port over to the Rhodium, and I sit here scratching my head asking why. I truly believe that much of it is perception, mine being that Android just isn't for me. You may consider checking out that thread and seeing if the port over is any closer to happening.
In the meantime, I have heard that the Energy roms are quite stable and fast, so you may consider flashing one and seeing if maybe your response issues are handled. Be sure to read up on unlocking/flashing your device first so you don't brick it.
I'm sorry I'm not much help here. I do think though that perhaps some of the issue may be the screen...I could be way off base here too, though.
I am testing out the Dymanic Resource Proxy hack to see if it makes any difference to me. Will let you know what i find, so far idling at about 55%
update:
well, i went ahead and did a system restore, it was faster, but still not to my liking, so iwent ahead and flashed a ROM to make one final test. i went ahead a flashed energy ROM, and i have to say, i very much enjoy it now. ALOT faster, much smoother transition between applications, accelrometer works alot better, an overall greatly improved experience.
thanks to everyone that helped me!
one last question though, after flashing the ROM, my ALT key doesn't seem to work. Any fix? i would do a search, but im already typing a response, so i thought i would go ahead and include it here.
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
b1ck132 said:
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
Click to expand...
Click to collapse
haha thank you, i knew it would probably be somewhere obvious, but i was just responding and figured i would go ahead and throw it in there
http://code.google.com/p/vogue-andr... Priority Component Owner Summary#makechanges
things change fast around here. try reading new threads before post useless request to fix an old problem from march
If your going to daddy me at least leave me a toy.
Wow learn to read. The android n00b thread people are still having these issues. Maybe something has changed but I have seen it. I see two categories of haret users those who work (miracles people who usually are using nand and may have some enviromental difference over us regular sdcard-hare ppl)..
If you can fix my issue fix it, but don't tell me its fixed when nothing says that. Albeit a night of going through all the updates on the different builds may produce results no one has done that in that particular thread (2, or 3, which upon someone coming up and saying this easy has ended up giving up) both threads are a bit different. One was supposed to be look how easy it is , with a few nand resistant fools getting every thing but sound. You sir are a troll... !#@@! @!# @#[email protected][email protected]@!
Seriously if you want new people using android put out a haret build that works... Don't make us n00bs flash our customized **** so we can say oh thats broke, i need that...
sorry if my tone was incorrect. let me try again
The link you posted refers to something that is not a problem any more or was due to old hardware, ie the button physically wasnt working.
k_k successfully used haret to test his build when he was working on the gps. that was the beginning of june
are you trying to say that the link is to YOUR problem? i cannot tell from the post of only a link. it looks like reading through this thread that you got past that problem.
if you need help please list your problem with as much detail as possible so i or someone else can help you.
if you are trying to make a case for haret dev, you should post links or quote more recent attempts and problems
Thanks for the news
Cool. I'll search up on that and post to the threads that I've been going to. It's just email never comes across very personable. People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication. If you see something try to link it, glad I have a user name to search off, but if you can pt a better thread I'll be happy. Either way when I find it, I'll try to boot again maybe in a week or so. I'll be very happy if it does indeed work now, we'll see.. As far as my posting relating to haret, yet you can regain control of your buttons but if you actually read all of the thread you'll see it doesn't get better than that, it then is a sound issue. Either way haret is broken, and my point is that poor user from march is still suffering now, and this time its sound. I suspected that haret became broken due to the development direction towards nand. I.e. whatif system.file is reffed somehow as (NAND0,0):/initrd.gz. I mean droid when from system.img's to partitions so something very generic could lead to both issues esspecially if a user A who can't hear in haret, can hear in a nand install using the same release? See the modules and stuff are going to be the same. I hope your not wasting my time with the k_k bit...
tyler51773 said:
I hope your not wasting my time with the k_k bit...
Click to expand...
Click to collapse
no. he is one exmple of people who have it working. there are others, i just know him off the top of my head.
People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication.
Click to expand...
Click to collapse
your first post was just as indirect. from that post i had no way of know you have been working on it. the specific link you post was probably not the best choice. with out direction from you i have no reason to go 2 links deep. not until you gave more description did i go into the xda thread where have been trying things.
it then is a sound issue.
Click to expand...
Click to collapse
yes there is still the sound issue. you could have gotten much better response if you had put something in the first post to indicate you specifically want the sound worked on.
sound it is.
its just more like a watch me thread for people who care about haret. i posted a bug on vogue-android.. but the drift it haret is broken. been broken. its bad right now. can we fix it? or is it fixed already. you mentioned K_K do you mean this thread http://forum.xda-developers.com/showthread.php?p=6852911 or do you mean kalt_kafee kernel are they same guy? where you saying dpad was fixed versus just sound. I guess I'm going to try his latest update kernel, unless you've seen a better thread. I've already got to goto bed. Maybe that's why the guy never came back on my own thread cause i sent him to a new kalt kernel hehehe..
sound working
Going through the list now. Thanks for the pointer. I'll will soon venture forward.
I got sound on an old androidinstall of unknown origin. it was freezing and unstable. I did not get sound ironically on VaniljEclair , the second install from the old android I also installed to system.img vs sdcard partition. trying warm
Aqtrans' CM-5.07 - nice and stable
warm eclair rls 1 - fast, worked great for a day then force closes all over
Incubus26Jc's SuperE beta 3 - still slow on kaiser
VaniljEclair 5.0.8 out! (not tested by me)
trying myn's warm donut then will try aqtrans'
you may have beaten the pepsi challenge.
DO NOT TRY OCLF, if you can not go to factory reset.
I have read almost all the threads answer etc. on many forums, How many people faced the problem and I think I am latest victim after having OCLF, phone doesn't start anymore, does not go in hard reset..nothing just vibration and 2 lights in bottom nothing else.
It just screwed me, OCLF 2.2, with Z4Root , Android 2.2 froyo on SGS....installed and you are gone. still you want it go ahead, feel free....I am angry on myself not on anybody else but I thought, I better write something to save few people at least, opposed to other people who are also bricked and praised the fix to not to stand alone.
Finally I gave phone back, not sure if I get a new one or get same repaired ( in warranty or I have to pay if they can detect that It was me not the hardware or something else...), will post what happens but for now, its not safe, do not go for it and remember there is very thin line between bravery and foolishness. decide yourself.
There are numerous ways to recover your SGS, all you had to do was have a read on here, don't panic and use the search function.
I'm new to all this and i've been in the same position as you and have thought I had bricked my phone at least 5 or more times. But thanks to others on XDA they have same me and my SGS )
sorry but if you dont know what you are doing, why are you doing it?
and btw there are alot of things you can do to recover your phone, even if its totally bricked.
you saying you read all threads etc? i dont think so cuz then you would know what to do.
and OCLF IS SAFE, if you know what you doing and have to do if its going wrong.
ps: if you need help, pm me i will explain you what to do, but only if you have the phone in front of you.
There should be a big banner in the development section which says "Don't try these if you are a n00b and not willing to read and learn before flashing anything!"
That is a thoughtless, misinformed thread title maligning a good developer's excellent work.
Think hard before you post in future........
doc jpy 7.1, jpx, k12i.
OCLF pertains to the Software Level. I see no reason for the Hardware to be affected. You should always be able to go the Download Mode after removing the battery for sometime.
i just say OMG.. i "bricked" (like you) my device about 7-8 times... no problem! i also BRICKED my device 1 time... no problem! don't panic, sgs is very strong! use search function of forum, the problem is not OCLF itself, is a "dead" sd-card (i don't know exactely, i'm a noob) it's a problem connected with the mount of an internal memory, i personally discovered that it might be also connected with a wrong flash of the csc (personal experience!)
Next time (yes it will be) don't panic there's a solution
No panic, just another way of adding some more info for OCLF
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Tried once to have a bricked phone, my first try actually..
Formated the system by mistake, to high i guess.. LOL..
Non the less, had black-screen ofc, System format, in more than 5 hours, till I tried odin with the org firmware, and brick gone
Sure, thought Sh!!!!!t at first, but then started reading, that was what I've spent the 5 hours on, and 7mins later up and running.. No worries for brick no more
So, think you could have made it your self, instead of returning it, sry
Or maybe you couldn't go into DL mode? I could with formated system?
Just like dhiru1602 wrote, DL mode should be in place, it was on mine like I said
SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
Did u read the info screen that pops up when u first started oclf? I guess u didnt coz there are very clear instructions on what u have to do to apply the lagfix sucessfully...
Edit: btw ockf is on market again he just had to remove the abillity to root...
Sent from my GT-I9000 using Tapatalk
SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
READ!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!!!!! READ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!! BREATH IN!!!!!!!!!!!!!!!!!!!!!!! BREATH OUT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. You didn't read instructions clearly
2. You created a misleading thread title
3. You are now asking for step by step instructions when there is already numerous guides and answers on how to get your phone going again
4. You now look like a lazy, ignorant and upset kid that broke his new toy because he was too rough with it and now expects to be spoon fed instead of actually learning from his mistake.
5. I am not usually this hard on anybody but I am annoyed by this thread
you're funny. maybe you can discuss why it's so bad with RyanZA himself?
herpderp.
If you hadn't have badmouthed his work, you'd have found Ryan extremely helpful, in fact, he's such a good bloke, he'd probably still help you if it was necessary.
doc jpy 7.1, jpx, k12i.
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
its ok now guys, he is new to android and galaxy. Close this thread pls.
pm me if you got your phone back and i still will help you and explain everything.
Just plug it into the computer and use adb reboot recovery. Should work, it did for me.
Sent from my GT-I9000 using XDA App
madfix said:
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
Click to expand...
Click to collapse
@OP (original poster) please change the title or delete the thread.
I installed OCLF about 2 weeks ago on my new Froyo install (!!>after reading<!!) and had no problems at all. I used version 1.1 on Eclair and version 2 on Froyo. Ryanza has made a brilliant tool and does not at all deserve to be tainted like this
A ignorant noob like u dont even deserve the help! Uve read? Where?? In every instruction its writte try this at ur own risk.. I had the same problem..Didnt u read abt the 3 button combo?? Z4root and OCLF dont always work well together! AH m very annoyed cuz i really respect Ryan's work!! READ ----- READ----- then again READ--
no point flaming him too much. just report his post
all i can say is LOL
I only just recently got my Note II and it has got ARHD on it, which I installed because it's a rom based on samsung software with no comptability issues and great battery life.
I also have a Galaxy Nexus and I noticed a few "problems" the Note 2 has and the older Nexus doesn't:
the browser on the Note 2 looks okay but the pointer precision is just very bad. To give an example: if you swipe your finger up or down vertically for a few centimeters, and then you start sliding diagonally (without having lifted off your finger off the screen in the meanwhile), it will only continue to keep scrolling vertically, it won't "follow" your left or right (or diagonal) movement. When you lift off your finger from the screen, retouch it and then scroll diagonal right away it will follow the movement. I find this very annoying, it prevents me of having a smooth browsing experience. My older Nexus with stock android 4.2.2 and stock browser is smooth as butter and follows my swiping movements 1 to 1..
I tested Dolphin browser, Maxthon.. all still bad pointer precision.. Chrome seems to be the least bad of all the browsers, but then on the other hand I find it very choppy.
PS. I already tried an AOSP/CM rom (Sentinel ROM), and there the browser was smooth, yet, non-touchwiz roms are not bugfree and the battery life is nowhere as good as with a samsung based rom.. And especially that last factor is really important to me. (Unless anyone can advise me a bugfree AOSP rom with batterylife that is as good as a samsung based rom).
SOLVED, SOLUTION IN POST #15
Then something else that annoys me quite a bit: when the screen is off and I press the wakebutton, it takes like 1 to 2 seconds until it actually wakes.. I've read I'm not the only one with this problem but I find it kind of unacceptable for a quad core phone with 2GB of ram.. Same problem when you are in an application and you press the homebutton to go to the homescreen, it sometimes takes like a second or more too.. Once again, stuff like that on my simple dual core nexus with half the amount of ram doesn't happen.
UNDERLINED PART SOLVED, SOLUTION IN POST #3 (thanks Kremata)
Then the good stuff has to be said too: homescreen-scrolling is insanely smooth, watching videos is awesome, the camera is great (so is the samsung camera app) and not to forget, the battery life is a revelation to me, I get through the day easily with hardcore use of the phone (that cannot be said of my old Nexus..).
I really like the Note II, but these few problems really crash the party for me.. Also I never thought I'd say it as a Nexus-fan but I generally find Touchwiz pretty cool and suiting on the Note 2.. So I'd prefer to stay on a samsung based rom like ARHD if possible.
Hope there's some experts here who can give me advise on how to handle these little problems.
For the record, I managed installing the AOSP browser, and the bug is still there. So it must be rom/kernel related, not app-related..
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
For the browser thing I don't know. I never felt it was a problem for me.
Kremata said:
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
Click to expand...
Click to collapse
One problem solved already, thanks for that!
I placed a video of the pointing precision problem on youtube. Btw I checked if the touchscreen is ok by using "show touches", and it followed my touches 100% perfectly, so it's not the phone, it's definitely some software problem..
This is the video
Could anyone with a samsung-based rom try to reproduce the above problem and see if it happens or not ? If not, could you tell me what rom + kernel you are using, would be much appreciated..
I repeat that when I tried an AOSP rom on my Note II, this issue did not happen.
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
whisky_ said:
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
Click to expand...
Click to collapse
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
wtr_dhd said:
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
Click to expand...
Click to collapse
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Kremata said:
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Click to expand...
Click to collapse
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
wtr_dhd said:
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
Click to expand...
Click to collapse
I just realized this problem. I'm using Crash ROM, and sometimes it will happen like in the video, but sometimes it work perfectly.
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
wtr_dhd said:
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
Click to expand...
Click to collapse
You must be more picky than most of us as I never noticed this before either.
Kremata said:
You must be more picky than most of us as I never noticed this before either.
Click to expand...
Click to collapse
You don't forget the good stuff of stock android! But the samsung rom has some pretty cool features too..
HOORAY.
With "Chrome Beta" the swiping "bug" is not present! /me happy
Now my Note 2 is "perfect"