Related
I am just wondering if a newer official ROM looks like it might be released in March to address some of peoples' issues, or if I should just continue my research and preparation to flash what I assume is still available OTW although not OTA. Only thing really holding me back is the prep and the desire to hopefully not do anything riskier than necessary if something else is around the corner (I would do a total Samsung tool flash, by the way to hopefully start clean).
I can't speak for others, but flashing, and Odin, and roms and kernels use to scare the hell out of me. With that said, I used Odin and flashed a clean froyo, did the camera lag kernel fix and my phone is EXCELLENT now. Not a single thing wrong with it. Its fast, the GPS works, and now, I feel comfortable with ODIN.
Before, I was terrified to even start up odin, scared to even put my phone in download mode. Now, I've flashed to Froyo, messed that up, flashed back to Eclair, then flashed to Froyo again, and not a single hiccup along the way. For me, Froyo is worlds better than Eclair.
Thanks for the vote of confidence. Unfortunately the relationship of my Epic to my computer is like a woman's freaking menstrual cycle. I don't even know how I managed to root months ago and clockworkmod never even ended up on there and I have no idea why. So I have to really read, read read this place and do things very methodically before taking the leap. I just saw that there is supposedly yet another Froyo build on Sprint's site today but waiting for another may be pointless right now or close to it.
my last phone was a g1. i thought it was easy to load a custom rom on there, but the process for the epic is downright fool-proof.
you probably didn't get permanent root back on di18, but now they have a pre-rooted eb13 rom you can load through recovery after updating and using the same one click 2.5.5 method. nothing to fear!
v3rk said:
my last phone was a g1. i thought it was easy to load a custom rom on there, but the process for the epic is downright fool-proof.
you probably didn't get permanent root back on di18, but now they have a pre-rooted eb13 rom you can load through recovery after updating and using the same one click 2.5.5 method. nothing to fear!
Click to expand...
Click to collapse
I rooted, and am very grateful for the many benefits of it. However this involves much more than rooting--it involves data backup and restore, flashing, etc. so even if it's easier on Android phones than say that old ugly Windows Mobile, it still requires some skill and smarts. XDA is a heck of a tech crew though!
It appears to me that those who wiped everything and started fresh don't have problems. Those that tried to preserve their things are having issues.
dmanwithnoname said:
It appears to me that those who wiped everything and started fresh don't have problems. Those that tried to preserve their things are having issues.
Click to expand...
Click to collapse
What we have been trying to say is that ODIN or Heimdall is the way to go for changing OS's around. You can always get your contact data back through the OS. Your call data and SMS data is easy to get back with Backup to Gmail. Your programs are easily restored with Titanium Backup ($ version) or MyBackup Pro (just don't restore any system data).
Top Nurse said:
What we have been trying to say is that ODIN or Heimdall is the way to go for changing OS's around. You can always get your contact data back through the OS. Your call data and SMS data is easy to get back with Backup to Gmail. Your programs are easily restored with Titanium Backup ($ version) or MyBackup Pro (just don't restore any system data).
Click to expand...
Click to collapse
Can you please precisely define "system data" and why it shouldn't be restored? I use MyBackup Root and they claim that everything it backs up can be restored pretty much trouble free, even across different ROMs. I'd also like to use CWM and Nandroid (so all eggs aren't in one basket) but have to manage to get the things working first.
DroidApprentice said:
Thanks for the vote of confidence. Unfortunately the relationship of my Epic to my computer is like a woman's freaking menstrual cycle. I don't even know how I managed to root months ago and clockworkmod never even ended up on there and I have no idea why. So I have to really read, read read this place and do things very methodically before taking the leap. I just saw that there is supposedly yet another Froyo build on Sprint's site today but waiting for another may be pointless right now or close to it.
Click to expand...
Click to collapse
"amen to that BROTHA!" lol
ehh things can be tricky at timkes, but they always seem to work out. unless you have a problem like this.... http://www.youtube.com/watch?v=vvosH8UZrWw
a system app is anything that you didnt install yourself. its all the apps in /system/app folder. if you download something from the market it gets saved to /data/app. hope that helps. btw is eb13 considered our official froyo? did they finish pushing it ota?
So, maybe some of us are just tired of the burnout from waiting for the now-"discontinued" Froyo. But is there any word on a possible "ECxx"? I'm almost afraid to ask, heheh.
@dog316
I agree froyo is great but im just woundering if your browser dosnt get the checker box when your trying to pinch to zoom. That's the only problem I have with it, but I think it kinda a big problem
Sent from my SPH-D700 using XDA Premium App
castro08 said:
@dog316
I agree froyo is great but im just woundering if your browser dosnt get the checker box when your trying to pinch to zoom. That's the only problem I have with it, but I think it kinda a big problem
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Well I am glad that I am not the only one to run across that problem. I thought that was an 'upgrade'. I am looking at several different browsers right now as most of the time I can't read the tiny type.
George
Yeah that's the only/biggest problem I have
And well have you tried dolphin brower?
Sent from my SPH-D700 using XDA Premium App
Yes - that is the one I like the best right now
George
Sent from my SPH-D700 using XDA App
What's the big deal with odin. I flashed two epics at ones to eb13 on my 4 year old sony vaio its my workhores laptop I flash everthing with my sony, subaru ecus, hondas, phones, any thing I'm moding with custom FW hacks.
The only time it did not work for me was a asus p4c800-e dx mobo's front usb ports
Sent from my ComBadge..
Im gonna try to make this short because im sure alot of people have expirienced this.
Almost every Epic rom i ever flashed sooner or later i get "process com.google.process.gapps has stopped unexpectedly" or "Android.process.acore" fc or some similar bull**** that has to do with Google Frameworks usualy.
Like today i started getting Frameworks fc,so i cleared date/cache for almost all apps trying to fix it.I rebooted and now on top of Frameworks fc i get Android Acorn fc and Gingerbread MTF fc!
So im like fck it im just gonna do system restore(which i was trying to avoid).
Did system restore wiped data/cache/sdcard/dalvic cache 3 times and what happens?I get same damn Google Frameworks/Acorn/MTG fc's after reboot!
Only way to fix this problem is to reflash the rom.
What causes it?IDK,i suspect its bacause my girlfriend(bacause it happens mostly when she has it) lets the phone's battery die while txting/calling but my roms are Journaled so that shouldnt be a problem,right?
Anyways is there a fix/prevantion for this sht without having to reflash?
Just when i think i found the right rom it happens again.This happens sooner or later on any rom,or is this something that android users gotta live with?
Update:
WTF i just reflashed and now im stuck at Samsung logo,i guess its Odin time and hate to say this but might be WP7/WebOS/iPhone time.
Don't mean to be a deuscher or anything but have you tried deodexed stock? Never had those issues on my heavily modified stock before.. (Might as well be my own cooked rom, though changed/tweaked realtime with my cell on) lol. =)
Shinydude100 said:
Don't mean to be a deuscher or anything but have you tried deodexed stock? Never had those issues on my heavily modified stock before.. (Might as well be my own cooked rom, though changed/tweaked realtime with my cell on) lol. =)
Click to expand...
Click to collapse
Thanx,im might try that.I think it might be ext4 that does it because i dont think i had them problems on rfs-i cant even remember last time i used rfs.
I kange my own roms too but i always prefered to use lightweight roms like Syndicate for foundation.But if stock rfs is more stable than it will be a good trade.
I always get gapps errors when I copy something to the system\app folder. I have started to use flashable zips instead and clear Dalvik before booting and have not seen that problem again. It doesn't sound like you are doing any of that but any theme or mod that is flashed and doesn't wipe Dalvik may cause this as well. Hope this helps. You may also just have a finicky phone...lol.
My phone isn't rooted and I got that. Fo me it had to do with the gmail app sync. Once I stopped that no more fc. I use the samsung email app that on the phone now.
Sent from my non-rooted Epic 4G using the free XDA App
I blame my girlfriend too.
Sent from the future.
Take this how you want. I had this problem span over 5 nand backups one day, 5 that I knew where all good when I did a backup (and had restored before with no FC's. Then one day on eg22 all hell broke out, I was doing so much that day I can't narrow down what happened. Then I restored a backup,,, what, still getting framework fc's; Tried another, then another. 5 times same problem. I odined back to DI18 and let it OTA, then installed cwm and restored my laszt backup. Everything has worked since.
I have this problem every so often on srf. Only fix I know is to reflash the rom then restore a backup. This usually happens when my phone reaches 0% and dies. Has happened over 10x
Sent from my SPH-D700 using XDA App
lviv73 said:
i suspect its bacause my girlfriend(bacause it happens mostly when she has it) lets the phone's battery die while txting/calling but my roms are Journaled so that shouldnt be a problem,right?
Click to expand...
Click to collapse
Journaling isn't a panacea.
When there's sudden power loss (battery pull or death) on a journaled file system, the file system should be in a consistent state on bootup, but individual files can still become corrupt.
If that happens, doing a "Clear data" on all apps that force close should fix it. In the worst case, a "Factory data reset" should work as well, without having to resort to a reflash.
I don't know if RFS does full data journaling or not, but I suspect it does. Anecodtally, these types of issues appear to be much rarer on RFS, which is part of the tradeoff to RFS suffering from additional lag (to ensure writes happen timely).
As general advice, if you are going to run ext4, journaled or not, avoid power loss as much as possible.
puff601 said:
I have this problem every so often on srf. Only fix I know is to reflash the rom then restore a backup. This usually happens when my phone reaches 0% and dies. Has happened over 10x
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Just as i suspected.It happens on rfs too or just ext4?
I would think thats what Journaling was for so something like this wouldnt happen.
So this is a problem on any android phone i take it,google needs to fix this.
What regular nontech people supposed to do?System restore everytime their phone dies?lol.
mkasick said:
Journaling isn't a panacea.
When there's sudden power loss (battery pull or death) on a journaled file system, the file system should be in a consistent state on bootup, but individual files can still become corrupt.
If that happens, doing a "Clear data" on all apps that force close should fix it. In the worst case, a "Factory data reset" should work as well, without having to resort to a reflash.
I don't know if RFS does full data journaling or not, but I suspect it does. Anecodtally, these types of issues appear to be much rarer on RFS, which is part of the tradeoff to RFS suffering from additional lag (to ensure writes happen timely).
As general advice, if you are going to run ext4, journaled or not, avoid power loss as much as possible.
Click to expand...
Click to collapse
Thats exactly how i tried to fix it,wiping data and cache on all system apps and all that got me was even more unfixible fc's.
For example:After i cleared cache for frameworks i started getting more anoying Gingerbread MTF fc every 20 seconds,lol.Yeah i tried clearing Gingerbread MTF cache/data and i still got the fc's even after system reset.
Now i see why Android is not doin good in corporate world,people need something reliable.
lviv73 said:
Thats exactly how i tried to fix it,wiping data and cache on all system apps and all that got me was even more unfixible fc's.
For example:After i cleared cache for frameworks i started getting more anoying Gingerbread MTF fc every 20 seconds,lol.Yeah i tried clearing Gingerbread MTF cache/data and i still got the fc's even after system reset.
Now i see why Android is not doin good in corporate world,people need something reliable.
Click to expand...
Click to collapse
How many 'Berrys on corp accounts do you see that are as heavily modified as our androids??? And to be fair, the Epic still really isn't even 'done'... by the time they released EC05, it was pretty obvious that they were already planning GB, so maybe after GS2 launch, we will get source, CYM, Miui, etc... and a stable stock rom of course... then i can feel comfortable giving this to my GF when I get a GS2 I love my epic, but I hate her intercept more than any phone I have ever witnessed. Point is, kind of a bad phone to use as reference for relating it to business phones, also as we are on a hack site, most companies either prefer or insist you dont **** with their phones. I think it has been said that android will be getting more and more stable... by what, everyone? You just happen to have an early adopter phone, we are the guinea pigs who pay for R&D and find the flaws. The way the android world is shaping up, it looks as if its only getting better. I love that I was in work training, for a relatively technical position, and all but 2 out of 12 people had androids, the others had iphones and little to contribute to the BS discussions.
ungovernable1977 said:
How many 'Berrys on corp accounts do you see that are as heavily modified as our androids??? And to be fair, the Epic still really isn't even 'done'... by the time they released EC05, it was pretty obvious that they were already planning GB, so maybe after GS2 launch, we will get source, CYM, Miui, etc... and a stable stock rom of course... then i can feel comfortable giving this to my GF when I get a GS2 I love my epic, but I hate her intercept more than any phone I have ever witnessed. Point is, kind of a bad phone to use as reference for relating it to business phones, also as we are on a hack site, most companies either prefer or insist you dont **** with their phones. I think it has been said that android will be getting more and more stable... by what, everyone? You just happen to have an early adopter phone, we are the guinea pigs who pay for R&D and find the flaws. The way the android world is shaping up, it looks as if its only getting better. I love that I was in work training, for a relatively technical position, and all but 2 out of 12 people had androids, the others had iphones and little to contribute to the BS discussions.
Click to expand...
Click to collapse
Easy man,lol.Im only stating an article that i read on one of the android sites about android os not doing good in corprate world and ios and bb beating them at it.
Lviv, did you read everything in the rom's you installed? I'm pretty sure as someone mentioned in this thread somewhere it said turn of sync. These rom's are built on leaked sources. Unless your on froyo none of gb rom's are built on an official release.
Sent from my SPH-D700 using xda premium
edfunkycold said:
Lviv, did you read everything in the rom's you installed? I'm pretty sure as someone mentioned in this thread somewhere it said turn of sync. These rom's are built on leaked sources. Unless your on froyo none of gb rom's are built on an official release.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
They all froyo.This just happened to me on Revolution rom which is really nice if not the best i used so far.It also happened to me on few Syndicate roms and Bonsai and few more.
Plus i always have my sync off or just background data on,i never leave auto sync on because it drains battery.
Like someone said on here its brobably because phone's battery reaches zero while performing some task or Sprint spyware removal might have something do with it or ext4.
Im gonna try rfs and stock and see what the problem is.
Its just rediculous because my roms never lasted for more than two months without this happening,and as someone stated before that it happened to them even on stock unrooted phone.
There are threads all over the internet on this problem with different fixes that mostly dont work.
I experianced the same thing with two different roms this week and went back to acs bamboozle with eho6 modem and its all working perfect now.
Sent from my SPH-D700 using xda premium
When i send texts on my phone it will say send untill i restart phone is their a fix for this
sent using my cup phone nukka
deisel said:
When i send texts on my phone it will say send untill i restart phone is their a fix for this
sent using my cup phone nukka
Click to expand...
Click to collapse
Don't wipe level 2 ram
Sent from my SPH-D700 using XDA App
marcusant said:
Don't wipe level 2 ram
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Why not? I do it all the time.
I have this problem too, I think certain apps can cause it as well as certain thing crashing on your phone. Other times it just sprint. I have learned to deal with it and explain it to those I trying to message. Or just call them.
Sent from my un-rooted Samsung Epic 4G with XDA Premium
Thanks i wiped 1$level ram reboot phone and instantly fixed my phone was text hangin for a week now was about to smash a sprint employee in the face w the phone
sent using my cup phone nukka
R3537L1F3 said:
Why not? I do it all the time.
I have this problem too, I think certain apps can cause it as well as certain thing crashing on your phone. Other times it just sprint. I have learned to deal with it and explain it to those I trying to message. Or just call them.
Sent from my un-rooted Samsung Epic 4G with XDA Premium
Click to expand...
Click to collapse
You have that same problem because you wipe level two ram. Literally it is the cause of the problem. Reboot, send text, it works, clear level 2 ram, sendtext, it fails.
Don't clear level 2 ram is the fix.
Sent from my SPH-D700 using Tapatalk
At the end of the day, we're all responsible for our own phones, though when the op is given advice, its probably best to give your feedback in a slightly different approach as opposed to the defensive, "why not? Yada yada yada"
Yes. RAM 2 clears background and aggressively closes active apps, it even says so before you clear it, lol. When it comes down to it, I think we're all right at certain parts of this story. I for one and as well as many others can fix such a simple issue, but not everyone has the patience to do so, thus, it was stated to not clear level 2 ram. Which is fine, but the other posters saying "why not" shouldn't take it into account that he's talking to every single last epic owner. He's not. And for those that say they believe other apps can cause this issue, you are indirectly correct-- in a sense, other apps could be a factor, but also, does not apply to every single last epic user. With this said, op, all I have to add is this, if you can avoid clearing level 2 ram, please do, if you feel like clearing it, go right ahead. Clearing level 2 ram consistently does more harm than good though, so keep that in mind. I personally only clear level 2 ram only if I rape my epic with too many apps running, the most vital processes will continue to return. Anyway, I hope all of us were helpful in one way or another, good luck.
Exactly Shiny. It depends on what you are clearing level 2 RAM with. If you use a task killer with an ignore list, and you have system apps on that list, clearing level 2 might not interfere with texting. But blindly clearing all level 2 will at some point cause this.
Shinydude100 said:
At the end of the day, we're all responsible for our own phones, though when the op is given advice, its probably best to give your feedback in a slightly different approach as opposed to the defensive, "why not? Yada yada yada"
Yes. RAM 2 clears background and aggressively closes active apps, it even says so before you clear it, lol. When it comes down to it, I think we're all right at certain parts of this story. I for one and as well as many others can fix such a simple issue, but not everyone has the patience to do so, thus, it was stated to not clear level 2 ram. Which is fine, but the other posters saying "why not" shouldn't take it into account that he's talking to every single last epic owner. He's not. And for those that say they believe other apps can cause this issue, you are indirectly correct-- in a sense, other apps could be a factor, but also, does not apply to every single last epic user. With this said, op, all I have to add is this, if you can avoid clearing level 2 ram, please do, if you feel like clearing it, go right ahead. Clearing level 2 ram consistently does more harm than good though, so keep that in mind. I personally only clear level 2 ram only if I rape my epic with too many apps running, the most vital processes will continue to return. Anyway, I hope all of us were helpful in one way or another, good luck.
Click to expand...
Click to collapse
I didn't say clearing it fixed the problem. I was asking why not because its never seen it cause an immediate problem. My text would do what the op's does before I clear anything. I was asking why not because it clearing that is causing further damage I would like to know. Since I see no immediate problems I see it fine for me to do it continuesly but if there is some underlying thing I would like to know before I continue doing it.
Sent from my un-rooted Samsung Epic 4G with XDA Premium
R3537L1F3 said:
I didn't say clearing it fixed the problem. I was asking why not because its never seen it cause an immediate problem. My text would do what the op's does before I clear anything. I was asking why not because it clearing that is causing further damage I would like to know. Since I see no immediate problems I see it fine for me to do it continuesly but if there is some underlying thing I would like to know before I continue doing it.
Sent from my un-rooted Samsung Epic 4G with XDA Premium
Click to expand...
Click to collapse
Yes as I stated clearing everything in level 2 is known to cause texts sitting at "sending".
Sent from my SPH-D700 using XDA App
R3537L1F3 said:
I didn't say clearing it fixed the problem. I was asking why not because its never seen it cause an immediate problem. My text would do what the op's does before I clear anything. I was asking why not because it clearing that is causing further damage I would like to know. Since I see no immediate problems I see it fine for me to do it continuesly but if there is some underlying thing I would like to know before I continue doing it.
Sent from my un-rooted Samsung Epic 4G with XDA Premium
Click to expand...
Click to collapse
I never said that you had specifcially said clearing level 2 ram would have fixed the problem. It doesn't create an immediate problem, but it can. And same here, on being in the op's situation before, and yes clearing it too often isn't optimizing your user experience, Android manages apps and processes on its own without anyone's help by default, that includes prioritizing what is important, as well as re-prioritizing at a given time-frame, while also of course, giving us the human right to terminate apps we are not actively using. Just because you don't see the immediate problem, doesn't mean your phone is performing the way it properly should be. If you think wiping level 2 ram continuously is healthy for your epic, you might as well wipe your battery stats continuously while you're at it.
P.S. if you knew about programming and how things work, you'd understand that everything has a life-cycle, pre-maturely ending life-cycles gives birth to all sorts of hidden bugs.
Just a question. I've been flashing my phones for years now but I have a question which has only come up now because I've never had a phone for as long as this MyTouch4G which I love... Is it basically accepted that at some point after several months, a ROM will begin to malfunction? Is it inevitable that at some point things just start acting wonky maybe with downloading and deleting of apps and media and so on? Or am I just experiencing crashing and slow downs for no reason?
Opinions? Thoughts?
I don't have issues with crashing, but in my experience ROMs started to slow down after a few days and it just gets worse with time. A Cache and Dalvik Cache wipe can help, but after awhile I just have to start fresh.
I'm sure that some of my crashing has to do with apps on the sd card. It's funny, ont the mytouch 3g slide the big concern was running out of room on the phone cause you couldn't transfer apps to the sd card. Now that you CAN use the sd card, half the apps cause problems not running from the phone. Ridiculous.
Anyway, more to the point then, you don't think the ROM causes any kind of crashing at all?
tinpanalley said:
I'm sure that some of my crashing has to do with apps on the sd card. It's funny, ont the mytouch 3g slide the big concern was running out of room on the phone cause you couldn't transfer apps to the sd card. Now that you CAN use the sd card, half the apps cause problems not running from the phone. Ridiculous.
Anyway, more to the point then, you don't think the ROM causes any kind of crashing at all?
Click to expand...
Click to collapse
Not if it wasn't at the beginning. Not for me, anyway. You have to maintain your phone im much the same way you do a pc to prevent junk from building up and bogging it down. Get rid of bloat and unnecessary apps, clear caches, delete folders, etc.
Sent from my HTC Glacier using XDA App
tinpanalley said:
Just a question. I've been flashing my phones for years now but I have a question which has only come up now because I've never had a phone for as long as this MyTouch4G which I love... Is it basically accepted that at some point after several months, a ROM will begin to malfunction? Is it inevitable that at some point things just start acting wonky maybe with downloading and deleting of apps and media and so on? Or am I just experiencing crashing and slow downs for no reason?
Opinions? Thoughts?
Click to expand...
Click to collapse
Well I was using core droid since it came out and never had a problem with it. But yesterday it froze while watching a youtube video. I took out the battery and put it back in and i got a bricked phone.... I'm not sure if its because i used it for a while or because my eMMC died or something.
Geez... so, what, these phones are MADE to only last like a year and a half now? Lord...
None of the ROMs I've flashed have had any issues... My Glacier is amazing
Sent from my Infernalized Glacier!
-Team Inferno
saranhai, what do you mean in your instructions that "A custom recovery, 4EXT is recommended"?
Nevermind, I know what 4EXT is now. Only problem is that I'm so comfortable with the linux look of CWM that I don't feel good using anything else.
tradejak66 said:
Well I was using core droid since it came out and never had a problem with it. But yesterday it froze while watching a youtube video. I took out the battery and put it back in and i got a bricked phone.... I'm not sure if its because i used it for a while or because my eMMC died or something.
Click to expand...
Click to collapse
If you can still get into recovery and hboot, your phone is not bricked
tinpanalley said:
saranhai, what do you mean in your instructions that "A custom recovery, 4EXT is recommended"?
Nevermind, I know what 4EXT is now. Only problem is that I'm so comfortable with the linux look of CWM that I don't feel good using anything else.
Click to expand...
Click to collapse
I just said that you needed a recovery image like cwm or 4ext to flash. Well to each his own opinions
Sent from my Infernalized Glacier!
-Team Inferno
You really like the Revolution mod?
eqjunkie829 said:
If you can still get into recovery and hboot, your phone is not bricked
Click to expand...
Click to collapse
Sorry I wasnt clear enough. The phone won't turn on whatsoever. No recovery, No hboot. T-mobile tried getting into recovery and they failed. Its it bricked. not soft bricked.
tinpanalley said:
Geez... so, what, these phones are MADE to only last like a year and a half now? Lord...
Click to expand...
Click to collapse
Well, the technology evolves so rapidly they aren't really all that much use after 2 years.
Sent from my HTC Glacier using XDA App
"the technology evolves so rapidly they aren't really all that much use after 2 years"
Well, that's subjective. There is nothing that the newest phones can do that I need. My media uses are significantly less than the average person though. I don't watch video or listen to music on my phone.
tinpanalley said:
You really like the Revolution mod?
Click to expand...
Click to collapse
what mod?
the ROM?
yes, Official Android Revolution HD is AMAZING.
I'm sorry I misspoke. The ROM. I knew it sounded dumb when I typed it.
Hey, does anyone happen to know if any of the Sense 3.5 ROMs have the stock Sense version without any color edits or custom themes made by people? I just want it the way it originally looked.
tinpanalley said:
Hey, does anyone happen to know if any of the Sense 3.5 ROMs have the stock Sense version without any color edits or custom themes made by people? I just want it the way it originally looked.
Click to expand...
Click to collapse
Official ARHD:
http://forum.xda-developers.com/showthread.php?p=22694501#post22694501
everything's stock. ROM itself is smoother than butter
I did try it but is there any way you can get the Quick Launch widget from Bliss for it?
Sent from the XDA App
Reset in recovery mode and TWRP have a much....
Mainly in file folders. Its normal?
Enviado de meu Nexus 7 usando o Tapatalk 2
fgenari said:
Reset in recovery mode and TWRP have a much....
Mainly in file folders. Its normal?
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
Really? It's a recovery. You're only going to see it at most a few times a day. Yes, it is obviously going to be laggier than the android OS.
Keion said:
Really? It's a recovery. You're only going to see it at most a few times a day. Yes, it is obviously going to be laggier than the android OS.
Click to expand...
Click to collapse
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Yes, i get a bit of lagginess. Not in file folders, but when it opens. When booting into recovery, mine will sit at the twrp splash screen for upwards of 30 seconds. All versions i have tried does the same. My other two N7s dont do it. So far, nothing more dramatic has occured, so i am not to worried yet.
Sent from my Nexus 7 using xda premium
rebel1699 said:
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Yes, i get a bit of lagginess. Not in file folders, but when it opens. When booting into recovery, mine will sit at the twrp splash screen for upwards of 30 seconds. All versions i have tried does the same. My other two N7s dont do it. So far, nothing more dramatic has occured, so i am not to worried yet.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Vey thanks guys!!!
rebel1699 said:
Yes....really. The lagginess on one or a few devices could be a sign of a future problem. A bad flash, a bad download........ Please realize that even a problem you consider small may merely be a symptom of something bigger. Now, back to the original question....
Click to expand...
Click to collapse
I don't think that's how it works.
Read a book, eggnog.
Keion said:
I don't think that's how it works.
Read a book, eggnog.
Click to expand...
Click to collapse
Thats exacy how it works. Certain behavior can be indicitive of software, or even hardware failures, or either in the future. That is the entire point of TROUBLESHOOTING. Either way, questions like this are the point of the sub forum. It is what it was made for. Hence the name Q&A. And yes, I read books. It was kinda required while attaining my electronics engineering degree. If you dont have a constructive response to an honest question, just move on.
And as Forrest Gump says- "And thats all i got to say about that"
Op- If the problem persists or gets worse, you may want to redownload twrp and reflash to make sure you did not have a bad flash last time. If that does not work, then erase the recovery partition through fastboot to make sure there are no partition errors. Then while still in fastboot, flash twrp again. Its no sure thing, but it will eliminate repairable partition problems. Mine browses the filesystem very quickly and smoothly. Just gotta try different things till you find the root issue.
Sent from my SAMSUNG-SGH-I727 using xda premium
rebel1699 said:
Thats exacy how it works. Certain behavior can be indicitive of software, or even hardware failures, or either in the future. That is the entire point of TROUBLESHOOTING. Either way, questions like this are the point of the sub forum. It is what it was made for. Hence the name Q&A. And yes, I read books. It was kinda required while attaining my electronics engineering degree. If you dont have a constructive response to an honest question, just move on.
Click to expand...
Click to collapse
No it's not. If you got a "bad" recovery, then it simply won't work. Smoothness of the thing won't be impacted.
Moreover, if it works, and flashes stuff fine, then there is no reason to troubleshoot. This really should be obvious, especially to someone with an "electronics engineering degree".
What, you gonna freak out about a bad flash, everytime your device drops a frame?
Step it up, kouhai.
Keion said:
No it's not. If you got a "bad" recovery, then it simply won't work. Smoothness of the thing won't be impacted.
Moreover, if it works, and flashes stuff fine, then there is no reason to troubleshoot. This really should be obvious, especially to someone with an "electronics engineering degree".
What, you gonna freak out about a bad flash, everytime your device drops a frame?
Step it up, kouhai.
Click to expand...
Click to collapse
An error in a filesystem can indeed cause shudder. Perhaps you can explain why his lags in the file browsing, yet mine does not. Maybe why mine spends 30 seconds at twrp splash, and almost all others do not. Considering you never asked any questions before you decreed his problem was nothing invalidates you automatically. How long is the lag? 1 second? 2-3 seconds? Even longer? What version of twrp is he running? Has he tried a reflash? You told him he had no issue with 0 info. It was just plain lazy. And yes, a bad flash or small errors can indeed still allow the recovery to run, but with glitches. Devs resolve alot of problems here by identifying a bad flash. It is one of the most common issues. One bit out of place during a flash can cause it to run, but with strange and undesireable behavior. You really need to educate yourself.
Now, impart your invaluable knowledge to the questions above, and then maybe ill take you seriously. Considering he ignored you, that should tell you something. Btw, does file browsing lag in twrp for you?
But to be fair, I am running a custom multirom version, further customized by the added timur kernel to allow host mode charging while in recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium