Hi there, Merry Christmas to y'all everywhere( We don't have Christmas here in my country, anyway.
Ok. Here we go:
I wanted to give my Mi A2 to someone else( completely working and smooth like it should be, has AICP Rom for long time), since that person doesn't like totally vanilla ROM, I decided to flash a more feature packed ROM on mi a2(in this case Pixel Experience), I do this, clean flash,following the usual procedure since I'm used to flashing ROM and stuff
after booting up, everything is sluggish and laggy, even in Phone Setup Wizard, started using phone, setup the apps needed, still laggy and sluggish.. Until that person starts complaining that phone is seriously slow, I say "OK, maybe I did something wrong or maybe this ROM has problems that I'm not aware of" I flash another ROM (Lineage OS), I do the previous stuff, still sluggish, just like previous ROM, exactly same scenario, it doesn't even matter if I have installed apps or just flashed phone, still lags.
Frustrated, why A2 became like this? Did it hit number of flashing rom attempts?(LOL, such thing exists? Flashing cant slow down the phone unless that ROM has problems) decided to go back to stock ROM, successfully flahed stock, boot up, still sluggish and laggy.. I don't know wth is going on...
My mind is racing:
"what is happening?"
"The phone was just fine when on AICP, after flashing, what happned?"
"Is it my fault? "
"Should I have just used factory reset instead of flashing ROM?"
Guys, there is something wrong
,will update the post with logcat and recording if needed and I have the time to do it. Feel free to ask questions.
TIA
Encrypted? Maybe encryption has some problems.
Kernel? Tried to flash just another kernel?
And how about frequencies? Are they ok? Phone is getting hot?
It's risky, but the last thing to do is to reflash other partitions too, like vendor or others (if you have them), maybe one of them get corrupted.
Ps: I'm currently on Android 12 DerpFest (Build of 26Nov) and I can tell you that after 2 months of usage my UI is getting really laggy and I'll change ROM soon. Maybe it's because Android 12, but I'm just letting you know.
Related
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Dr. Falken said:
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Click to expand...
Click to collapse
a bit noobish myself, but I think I can answer a bit regardless, anyone feel free to correct me...
1: if everything is working, great! if you dont feel comfortable, and dont mind resetting everything up, go ahead, do it again, cant hurt. whenever reflashing/new flashing, Dont Forget to make a nandroid and wipe! (and you can rename the backups in USB disk mode so you know which ones are what, otherwise go by the embedded date in the autogen'd title. in the nandroid folder on your SD card btw)
2: as far as I know, leave it?
3: HUGE fan of Darchs work, cant go wrong... keep in mind it does not have VisVoicemail in it, fix flash needed.
4: reboot into recovery, make a nadroid backup, WIPE!, flash the new one according to cookers intructions! done! (if ya dont like it, buggy, nandroid restore back to your last good one you did like!)
well I reinstalled the rom and wiped first...and everything is running way smoother than last time. I don't know what in the world happened or what was going on but I'll take it as it is
My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.
Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...
Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.
I tried both CandySeven (7.0) and Resurrection Remix on my m7, and I can receive sms just fine, but I cannot send it. Is there a fix for this or should I try a different rom?
I wish I had an answer. As far as I've seen, every Marshmallow and up ROM has the SMS issue. My guess is that once that's fixed for one, the others will be able to follow suit.
Ugh, that's really unfortunate. I could go back to stock but it is quite slow. I've got an iPhone coming due to this whole Note 7 situation (wouldn't be dealing with this m7 if it weren't for that), but it's not going to be here for a few weeks. Guess I'll just deal with this issue until then. Not so sure I want to switch back to iOS but for me it's either that or a v20... I don't really trust LG and I didn't want another Samsung phone. Really frustrated with my phone situation overall right now.
garnerlogan65 said:
Ugh, that's really unfortunate. I could go back to stock but it is quite slow. I've got an iPhone coming due to this whole Note 7 situation (wouldn't be dealing with this m7 if it weren't for that), but it's not going to be here for a few weeks. Guess I'll just deal with this issue until then. Not so sure I want to switch back to iOS but for me it's either that or a v20... I don't really trust LG and I didn't want another Samsung phone. Really frustrated with my phone situation overall right now.
Click to expand...
Click to collapse
If you don't mind running Lollipop, this ROM is a really fast, stable custom ROM that I run as my daily. Everything works on it, but it is a little tricky to flash (hint: fastboot flash the boot image after flashing the ROM).
coal686 said:
If you don't mind running Lollipop, this ROM is a really fast, stable custom ROM that I run as my daily. Everything works on it, but it is a little tricky to flash (hint: fastboot flash the boot image after flashing the ROM).
Click to expand...
Click to collapse
Actually I'm about to flash this, thanks. I'll let you know how it goes.
I bought my first phone when i was 16, i worked my ass off during summer for it. And after 2 weeks i decided to flash the custom rom, i remember my hands were shaking and sweating because i knew there is possibility of completly bricking it (not to mention how back in the days, flashing custom roms was like defusing a bomb, old school flashocolics will know )
It all went good at the end, unfortunately my phone fell in the water 2 days after flashing, and i could only use it as a paper weight
what was your experience like?
I too bought my first android phone when I was 16. It was a Samsung galaxy young S6310. After tinkering with it for a month I got bored. I tried more than 500 apps in that period. Some of those apps required "Root access" to work. I didn't know what it was at that time. When trying to learn about root, Google introduced me to the term "custom ROM" even though I didn't really understand how to get or install one. I rooted the phone with framaroot. That was the easy part. I messed up a lot of things with my unlimited power and had flash stock firmware using Odin several times. Then I learned about cwm recovery and it's nandroid backup feature. This was the point at which I understood how to install a custom ROM. I found a cyanogenmod based custom ROM for my phone. But it was worse than original ROM (my phone didn't have any actual development going on). It was too slow and crashed always. I switched back to Samsung's ROM never tried anything else ever on my galaxy young.
My first experience was with my mom's phone , when I was 13. I installed CM for her after the stock firmware turned out to be extremely buggy and almost unusable with constant freezing... It was scary af, but fun nonetheless. Unfortunately she gave away the phone , after even CM couldnt fix the issue. Turned out to be faulty DRAM .
After that, my second experience was with my Xperia Z3 Compact , which I got when I was 15 It was fun and we finally got actual custom ROMs (Like Lineage and other stuff) this March. Until then I was using SliMM and other roms that were based on the stock rom with some extra features (We did have custom roms, but the camera wasnt working, or unusable in them)
My first android which I rooted/(flashed custom ROM on) was a Micromax, running an MTK processor. Idk why I had the habit of replacing the CWM Recovery with stock recovery after flashing the ported ROMs :stupid:
Well i am a HUGE fan of AOSP, cyanogenmod in general, but samsung is a stupid *****, because of them we xan't have camera as good as on stock camera yo be on cyanogenmod rom, that is why i am on boring touchwiz
I mean yes cyanogenmod is awesome, but camera is one thing that i was looking up when buying a phone...
My first phone was Samsung galaxy star pro GT-S7262 and it was slow as hell so I decided to flash cm or aosp to improve its performance. Unfortunately there were no cm or aosp roms for the device at that time, just one themed lollipop rom. I was so scared while flashing mainly because it wasn't an official rom plus the device was slow so I thought I'd brick it. And just when I was getting comfortable, the dev jokingly decided to add a line at the end of the updater-script " BRICKING YOUR DEVICE" I was complete noob so I thought I did something wrong and almost dropped my phone. but it turned out to be a fast and stable rom and to this day I still have it installed (though I don't use the device anymore)