Related
Hi. I flashed a friend's epic with the DK28 update, did the one click root method, and flashed multiple roms (Frankenstein, bonzai, midnight) and they all had the same issue. The screen is very unresponsive to the point where she has to use the keyboard to navigate through the phone. She can't use the touch screen at all. I decided to flash dk28 stock in case the problem was with the roms themselves but it still has the same issue. If anyone can help me with this I'd greatly appreciate it as I've looked through many pages on here looking for a similar issue or a fix but can't seem to find it. Thank you.
wheeziestorphan said:
Hi. I flashed a friend's epic with the DK28 update, did the one click root method, and flashed multiple roms (Frankenstein, bonzai, midnight) and they all had the same issue. The screen is very unresponsive to the point where she has to use the keyboard to navigate through the phone. She can't use the touch screen at all. I decided to flash dk28 stock in case the problem was with the roms themselves but it still has the same issue. If anyone can help me with this I'd greatly appreciate it as I've looked through many pages on here looking for a similar issue or a fix but can't seem to find it. Thank you.
Click to expand...
Click to collapse
I suspect that you issue is not related to DK28. I would suggest that you Odin back to stock.
http://forum.xda-developers.com/showthread.php?t=794138
Start from scratch at the last OFFICIAL release. If it continues while stock, it more than likely hardware related. If it's fine stock, then start over with the DK28 install.
done12many2 said:
I suspect that you issue is not related to DK28. I would suggest that you Odin back to stock.
http://forum.xda-developers.com/showthread.php?t=794138
Start from scratch at the last OFFICIAL release. If it continues while stock, it more than likely hardware related. If it's fine stock, then start over with the DK28 install.
Click to expand...
Click to collapse
Thank you. I'll give it a try.
wheeziestorphan said:
Thank you. I'll give it a try.
Click to expand...
Click to collapse
after putting my phone thru a lot of flashing, rooting, and other things, i occasionally have that issue, where everything works on the phone except the touchscreen. but it never persists.... i can't remember, but i think i usually just let the screen go to sleep and lock, then when i wake it up, it works. if not that, then a reboot usually fixes it. in any case, it had me worried for a minute, but completely went away. that's my experience with that issue anyway....
yogi2010 said:
after putting my phone thru a lot of flashing, rooting, and other things, i occasionally have that issue, where everything works on the phone except the touchscreen. but it never persists.... i can't remember, but i think i usually just let the screen go to sleep and lock, then when i wake it up, it works. if not that, then a reboot usually fixes it. in any case, it had me worried for a minute, but completely went away. that's my experience with that issue anyway....
Click to expand...
Click to collapse
Thanks for your reply. But I've tried rebooting, reflashing roms, flashing back to stock rerooting and reflashing, and I always get the same issue. I know it isn't a hardware issue because it doesn't do it with the original firmware. I guess I'm just going to have to wait for the official update.
Hello.
My Wildfire S has a vary nasty bug - screen is freezing after unlocking. Well, I can wait few seconds if i just want to start gmail app etc. But when the call is finished and i have to press the Red Button, screen is freezed and that's very annoying.
What should I do to get rid of that?
i have same problem some help?
Same problem here...need help<<<<<<
i some time press home button to make it work>>>>>
got a video
I got a video example for those who can potentially help but don't undertand me)
youtube. com /watch?v=IBOCQYZJK9k
And a question - does hard reset do the same as if I flash totally new official firmware? I meen, does HR leaves something after it or only flashing new firmaware can give my phone a totally clean (like just out-of-the-box) memory?
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
I've got bad news. I flashed the phone by myself and that bug still is on. That means only one - we should go to the service centre and they'll have to deal with it
never experienced that bug. I have 1.35.707.3 CL48651 release keys.
Very strange, mine will hang for a second on the odd occasion but it's never that bad. Only bug I've noticed is sometimes when I power it off the 4 buttons at the very bottom stay lit, again that only happens every now and again.
Does that mean it's HTC sense's problem? Some people on 4pda(russian smartphone forum) say that their phones have been repaired in service centre by replacing touchscreen. I can't understand - is this hardware or software problem?
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
dojik said:
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
Click to expand...
Click to collapse
If you mean factory reset with hard reset, only /data and /cache are wiped.
Flashing a new ROM does wipe /system and replace the content with the new one, nothing happens with /data or /cache here, except within the ROM zip is a cleanup script.
Within /data is all userdata stored, settings, apps and so on (standart behavior, with links2sd its different), within cache is like the name says cached data of the system that shortens the system boot time and stuff like this. In most common you have to clear this before using a different ROM cause it could cause faults, but if the whole base of the rom is different you also have to wipe /data cause this can within this case also cause problems.
Sry, for the off-topic.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
nestorkg said:
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
Click to expand...
Click to collapse
Different launchers are only apps, they can't solve this problem when it's related to the lockscreen app, maybe switching to another lockscreen version can solve the problem.
same here, after unlocking left side of screen doesnt work until waiting a few seconds or touching other side
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
nestorkg said:
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
Click to expand...
Click to collapse
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Tectas said:
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Click to expand...
Click to collapse
It is weird that only right side of screen isn't working properly.
Hope it's not a hardware issue.
Cyanogenmod for wildfire s isn't out yet, so i can't try flashing.
Anyone with some definitive solution?
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
greavey said:
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
Click to expand...
Click to collapse
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Ko_Ka said:
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Click to expand...
Click to collapse
This is really doing my head in, its the only thing really ruining my enjoyment of the phone now that I have S-off!
I wiped cache, dalvik cache, sd card everything through clockwork before using the RUU flasher, it has to be software, is there a newer version of the RUU flasher since the 1.30.401.0?
Just a suggestion but temporary remove all your widgets to see if that is what might be causing it.
I found some widgets try to refresh once the phone is woke up even before the screen is unlocked. So I uninstalled any that I did not use.
Also you might try these setting in your build.prop file:
Code:
view.touch_slop = 12
view.minimum_fling_velocity = 30
gsm.proximity.enable=false
debug.sf.hw=1
windowsmgr.max_events_per_sec=80
Hopefully this is the right place to post. I apologize if it's not.
Last week I bought the Samsung Galaxy S2 X from Koodo Mobile. The model # is SGH-T989D and runs the newest version of ICS. 4.04 I believe.
I hadn't had any problems until recently. I was trying to root my phone when I ran into some trouble. I forgot to make a backup of my system, so when I ran into problems, I just decided to try out a couple custom roms. At some point something got messed up badly with my phone. Whenever I turn it off now the lights at the bottom of the screen stay on. Unless I hold the power for 30 seconds to a minutes it won't turn back on. The factory reset has also been a problem. I'll go to reset it, and it formats the usb storage, but doesn't restart. When the phone is on, it seems to work fine.
I finally managed to get a telus stock rom to flash and work. So I have two questions I'm hopeful someone can help me with.
1. Are there any Koodo stock roms for ICS? I've looked on tons of different sites, and it seems it's all either for T-mobile or Telus. Is that because Koodos just came out with their phone? I'm just looking for the exact version that would have been on my phone when I got it. I found one online, but it had no baseband version. If I have to return the phone or send it in for repairs, I'd like it back to stock,
2. My other question is, does the light not turning off, and the turn on problems sounds like a hardware issue? I've been trying to fix this for the last 24 hours and it's driving me nuts. Since I'm a noob I have no idea whether I should keep trying or just send it in for repairs. Does it sound like something that can be fixed? Like maybe I'm flashed a wrong kernel or am using a bad rom? I don't know, but advice would be much appreciated.
Thanks to anyone who answers.
you have various roms made for koodo..2) are you talking about the soft keys? depending on what rom you use they can be different (locationwise) ... if I'm not mistaken all --- This is my personal opinion. Jedi on koddo should be more than sufficient as to suit your daily driver needs. Dev is very helpful and keeps a very organized thread. You can also try darkside, if I'm not mistaken he had a koodo version. i own a hercules so i at give more information... for your best info, go into the thread and ask the ppl i n them for their experience. everyone's needs are different so for what might work for me might not for you Infamous is another one. Just click on the t mobile dev section and you just scroll for what you like.. Hope this help
I guess my main question is about the key lights staying on. I'm pretty sure it means its not shutting down correctly because it also won't turn on again unless I hold down the power button for 30 seconds. So could that be caused by anything I did? Like any of the flashing or customers roms I used, or should I just send it back into Koodo?
Okay download this: http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
And then flash a rom (any one, just pick one)
That is a flash able zip (in cwm recovery) that will completely wipe off every piece of system and rom data (does NOT touch anything on your internal memory or external sd). If your hardware lights are malfunctioning due to software, this will fix it. Then, when you flash your rom, if you still have the issue with your hardware lights, it's likely a hardware issue and you should follow a guide to return to stock everything and send it in for warranty repair.
Also, this is a Koodo based rom if you're interested:
http://forum.xda-developers.com/showthread.php?t=1849748
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Just run the cache wipe again. It will fix that.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
robois88 said:
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Click to expand...
Click to collapse
If you're looking to make a backup of your entire device image, your cwm recovery will do that for you under backup. No other way to do it, you have to do it via a recovery mode.
I don't know why factory reset would be causing that problem since I never use that but it does seem odd.
robois88 said:
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
Click to expand...
Click to collapse
To return exactly how you bought it, you need to first flash the stock ics kernel through cwm. Then flash an Odin tar file through Odin (desktop) which will restore stock rom as well as stock recovery. Unfortunately, I've looked around but could not find an Odin tar file for Koodo stock. Maybe you'll have better luck but in any case that is the process.
You seem competent and willing to learn, which doesn't happen as often as you would think. Let me know if I can help further. Good luck.
yoft1,
Many thanks again for your help. I am extremely green to this type of stuff so I feel like I've been thrown into the deep end here.
I've been looking around for the tar file and can't seem to find one either. But with the amount of people on here, there is probably someone who could upload it right? Would there be a thread or better forum for me to make a request? Or is that poor etiquette on this site?
I've just seen so many different roms, kernels, updates, etc...and I'm thinking somebody might be able to get it on here.
Ok you also said the first thing to do is to flash the kernel. Am I just lookng for any stock ics kernel? I just know I've looked through so many website and threads with different kernels, I just want to make sure I flash the correct one. Like is there a specific one per carrier, or model, or brand?
Again thanks for the help.
I would probably start a thread in the general section to see if someone can compile/upload an Odin flashable tar from Koodo stock. If that doesn't work or if no one responds after a bit, I would PM Mr X (a user on these forums). He is a dev that has uploaded stock roms for Telus and tmobile and he's also a really nice guy. He would probably know where to get one.
As for the kernel, I'm not sure if it matters but I would say with 80% certainty that there is no difference between the stock tmobile kernel and the stock Koodo kernel. On top of that, I would say with 99% certainty that it doesn't matter either way because I highly doubt they would look that closely (if there's anything to find at all) if you send it in for warranty purposes (but no promises of course) . If you get your hands on that tar file for Odin, I'm almost positive that the stock tmobile/Telus ics kernel will do it for ya.
Here is one of MrX's threads so you can PM him if the general forum doesn't work out:
http://forum.xda-developers.com/showthread.php?t=1356739
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
In this thread you can post your experience, questions, and all other stuff that is not directly related to the RE-FLEXxx rom.
I do this to keep the dev thread clean.
Thank you for your understanding.
I will take a look into this thread from time to time but the main goal is so that users of the RE-FLEXxx rom can help out each other and that they can find help from each other in one place.
Regards, civ.
I installed 2.0 on my N5110 (coming from 1.9) and it is working well but the top of my tablet is non-responsive to touch. Happened on other releases but a reboot always fixed it. This time the problem remained, so I tried wiping cache, dalvik, fixing permissions, reboots, and all sorts of combinations. I did finally manage to fix the issue yesterday after one of those reboots but now the problem just reappeared and won't go away. Any suggestions?
Edit: Finally got it resolved with a full wipe of data, cache, and dalvik through cwm recovery. Then I flashed Civz reflexx Rom 2.1 and rebooted. The top of the screen still did not respond to touch, so I rebooted and now everything works perfectly. :thumbup:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
no snote and extended menu all working for me. Maybe you had a bad download? Otherwise try wiping and installing fresh.
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
yes, hd happened to me, I re downloaded and reflashed it again and is OK now..
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
wase4711 said:
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
Click to expand...
Click to collapse
This is my opinion on it.....I usually only wipe the internal card if I am starting completely over with flashing a device. Wiping data/cache is usually all that is needed but if there are a lot of apps that get installed over time their folders get left and every so often I like to wipe it to get rid of all the "orphaned" folders. If you are going to just restore all those apps anyways then it won't make a difference either way. If you are going from the stock rom to a TW custom based on the stock it shouldn't be necessary to flash internal.
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
wase4711 said:
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
Click to expand...
Click to collapse
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
CCallahan said:
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
Click to expand...
Click to collapse
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
wase4711 said:
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
Click to expand...
Click to collapse
Use the terminal command on my rom
su
softkey_on
all info is in rom thread OP.
thanks, I thought I had read every terminal command in the thread, but I guess I didnt!
tun.ko or tap.ko?
I'm trying to get openvpn to work on REFLEX2.0 in tap mode. Looks like I need a tap.ko kernel module for either the stock kernel or the CivZ-StormBorn_Rev2.0-OC kernel. Anyone know where I might find such a thing?
---------- Post added at 03:59 PM ---------- Previous post was at 03:54 PM ----------
I notice the CivZ-StormBorn_Rev2.0-OC kernel has no /proc/config.gz file. That means the kernel was not compiled with the CONFIG_IKCONFIG option. Is there a way to see what options are baked in to the kernel?
Problem with softtouch Key "back"
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
USB Mass Storage Unexpectedly Removed Loop
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
MrAlexey said:
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
Click to expand...
Click to collapse
i have better luck if i tap at the bottom of the softkey. it's almost as if the icon is bigger than the actual location that the press registers.
Chrome screen bug solution
Basically the problem is the notification bar, combined with the lack of on-screen softkeys. In order to fix it, you need the following:
Xposed Framework:
http://mohammadag.xceleo.org/public/Android/XposedInstallerDownloadUnsigned.apk
How it works:
http://forum.xda-developers.com/showthread.php?t=1574401
App Settings manager:
http://mohammadag.xceleo.org/public/Android/Xposed/AppSettings_0.4.apk
I've been using this combination on my tablet for a while now. It lets me change the resolution for individual apps. For instance, I want the tablet mode of Gmail, but I want my tablet to run in phablet mode so that I get the top notification bar and no softkeys.
The Chrome fix is simple. The app settings for the Chrome executable should have the fullscreen option toggled, the DPI set to 160, and the screen resolution set to 800x1200. It then hides the notification bar on top while you're in the browser, and shifts the screen that quarter of an inch where it is offset due to the Chrome bug on tablets without softkeys. If you need to access the notification bar, simply swipe down on the screen from the top edge and it will pop up.
If the print size is too small, you can use the accessibility settings in Chrome to scale up the font size.
acfc81 said:
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
Click to expand...
Click to collapse
Hi,
Please ignore my last message as the issue was using the wrong kernel on my part. Thanks!
Question
I'm thinking of flashing a new ROM having used stock for month or so now. My concern is regarding the apps I have installed and am currently using, specifically FolderMount.
If I flash a new ROM (either civs older 4.1 build or his newer 4.2 one depending on how he is progressing), will I lose the links?
I have about 25GB worth of game obb and data transferred over from my internal memory to my micro SD. I dont fancy using up all my download allowance having to re- download and install all of those (plus the time it takes to transfer them all over). I dont mind losing the layout of my homescreens as I'm thinking of shaking that up anyway.
I've only one past experience of flashing a Rom and that ended up with me having to reinstall and set up all my apps (jump from ICS to JB on my Asus TF101)
flex beam 4.2.2 download unsuccessful
flex beam 4.2.2 download unsuccessful
Please upload