Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel
Related
I Know this should be in the Developer section, but I don't have enough posts. (Since you have to have at least 10 to do so...)
BUT, I installed a kernel from Blades which is the 1.6ghz with the latest version of CWM. The problem is that whenever I try to boot up the device it just stays on the first startup screen, and it also makes a weird popping noise from the speakers about every 10 seconds. I did wipe Dalvik Cache and I also made a back up before installing the new kernel. I've tried restoring but it does the same thing every time. Before installing the kernel I was running PRIMEORDIAL! v3.1...
Any help would be greatly appreciated....
Thanks
cdp
Hi Mate, You are not the only one. Unfortuantely 3.0.1 kernels don't work too well with 3.1 roms as you have discovered.
Not to worry though as this is an easy fix.
Simply flash the 3.1 stock kernel and you're up and running again. You can get it from here... http://forum.xda-developers.com/showpost.php?p=14283676&postcount=94
Wow, I didn't even realize that kernel was only for 3.0.1 lol. THANK YOU! Flashed it and it started right up! C:
You may now have wifi problems, since the kernel update will have installed a different module to the one you need, if this is the case just reflash whatever rom you are using.
Okay cool, I'm on wifi now and it seems to be working fine. So thanks again! :]
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Elbob10s said:
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Click to expand...
Click to collapse
Going from 7.0.3 to the new nightlies is a big jump. They've changed from Gingerbread 2.3.3 to 2.3.4 as well as several kernel changes, and tons of other stuff. In this case it's probably best to do a full wipe before installing the nightly. Then restore your user apps in Titanium, however DON'T restore system data, as this will cause big problems. Any ROM settings that you customized in 7.0.3 (in Settings or CyanogenMod settings) you'll have to manually set again.
edit: One thing to note, if you're a heavy corporate Exchange email user, you'll want to hold off on the nightlies for now. There is an email issue that seems to be occurring on the Inspire only, that causes all email apps to crash when viewing messages on an Exchange server. The problem's been around since nightly 88 and hasn't been fixed yet. However, if this is no big deal to you, then the nightlies have otherwise been working well.
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Elbob10s said:
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Click to expand...
Click to collapse
If you flash a new nightly you'll definitely want to upgrade to the newer LorDModUE kernel as well. It is specifically designed for the newer nightlies.
edit: He's got a new smartass2 cpu governor in v4.0 so be sure to check it out.
+1 for LorDMod UE kernel on CM7 nightlies! Kicks butt!
@Elbob10s,
One more thing I forgot to mention. Once you've installed the new nightly, then it's usually OK to flash subsequent nightlies directly on top of the previous one without wiping. When you do this, you'll need to reinstall LorDMod again, since the kernel will get overwritten back to default.
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Elbob10s said:
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Click to expand...
Click to collapse
Yes that was a known issue on LM 5.x kernel on the newer nightlies. You want to move up to LM UE kernel, the link is in my sig. It was designed for the newer nightlies.
The UE with smartass2 is working great. I fixed the contact icon issue by adding my phone number in the phone settings.
Everything seems to be working great now.
I've had my phone up and running on AOKP Milestone 1 and a custom kernel (can't remember the name now) for a few months now. I decided to replace the kernel with Lean Kernel since my phone's been crashing recently, and it was mentioned that the kernel could be the problem (this thread: http://forum.xda-developers.com/showthread.php?t=1842971&page=135).
After installing the kernel and wiping the cache/Dalvik cache, my phone rebooted but would not let me past the lockscreen. I then pulled the battery and attempted to reboot into recovery, but now my phone won't turn on at all. I'm currently charging my phone but no light is coming on, so kinda worried.
Any advice/solutions would be appreciated!
EDIT: I should also mention that if I pull the battery and put it back in, I get a "battery charging" symbol on the screen for a few seconds.
Download mode?
Sent from my SCH-I535 using Tapatalk 2
Did you install the proper LeanKernel? If you are on AOKP milestone 1 that is 4.1 based. The newest LeanKernel is 4.2 based. Could be the problem. There are also distinctions between AOSP and TouchWiz kernels. Do you know which version you flashed?
Regardless, if you can get into download mode like hank said, you should be ok.
Can't Boot into recovery with three button method?
Tried getting into download mode?
Well I feel dumb but after some searching around, people recommended just blowing on the battery contacts. This solved it, so case closed! Thanks for all of the advice though.
And yes, the lean kernel was for TouchWiz roms, which got me into this mess in the first place.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based