Hello everyone,
I'm really enjoying these kitkat based roms for the Atrix 2, however I'm having issues loading JBX 3.0 (2/27/14) on roms like liquid smooth and nexus experience. Without the custom kernel, phone boots up fine and everything works. However, the phone does not seem to recognize sim card and has no mobile network with JBX installed. I have tried unticking the 10% battery mod and I believe it's called the xposed framework in different configurations nothing works. Additionally, I have the same issue when I attempt to boot this newer version of jbx over the older version integrated into Gummy. Any help with this issue would be greatly appreciated!
Related
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
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
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Red Devil said:
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Click to expand...
Click to collapse
Thank's for the suggestion...will try one or the other this evening.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Affangta said:
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Click to expand...
Click to collapse
And what is the difference between cm9 and minicm9?
New problems...
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
chrisszz said:
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
Click to expand...
Click to collapse
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
SSKSSK said:
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
Click to expand...
Click to collapse
Tried the multimount app...didn't work...will check 4.3 roms later today.
Thanks for the response
android.process.media has stopped
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
Weekly 7 has some sort of issues.. read the thread before you flash anything. You can try weekly 6.. it doesnt have any known issues.
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
You can try Carbon 4.3 rom or the TriumphHD 4.1 rom as they r stable
Try Carbon 4.3
chrisszz said:
And what is the difference between cm9 and minicm9?
Click to expand...
Click to collapse
not much..cm9 is build for hdpi devices & minicm9 is for mdpi devices so it flies better on our pico.
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
chrisszz said:
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
Click to expand...
Click to collapse
You can try int2ext+.. it works fine.. just backup your apps using titanium backup or helium or similar and reflash the ROM with int2ext
Ok so finally I've managed to make everything work. First I tried to increase the memory using int2ext+ but it got stuck in cm logo loop, or I didn't wait enough I don't now, but then i reflashed using int4ext+ and it worked like a charm . So thanks everyone for the feedback and have a nice day...Cheers!
my experiences for htc explorer roms
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
fromturkey said:
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
Click to expand...
Click to collapse
I don't know why you faced so much issues because for me there are no such problems..only cm9 wifi toggle issue was there before using aries kernel & ofcourse cm10.1 bluetooth toggle issue. I never faced robotic call or freezing problem on any rom.
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Update:
Tried Elemental X, the phone reboots randomly now... And also just googled problem with Nexus 5... it seems like 5.0 and 5.0.1 have TONS of random reboot issues...? Goddamn it Google...
Do any of you have a stable ROM (stock or custom) that doesn't have random reboot issues?
Elementalx
codenamezero said:
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Click to expand...
Click to collapse
i use franco kernel 70 with stock rooted 5.0.1 with no issues. but i don't see any differences between stock and franco. neither performance nor battery life.
This Nexus 5 is just getting worst... it random reboots now.
codenamezero said:
This Nexus 5 is just getting worst... it random reboots now.
Click to expand...
Click to collapse
Sorry to hear that. Could it possibly be a hardware issue since you say it's happening to you across all software? Corrupted storage media could cause random reboots such as that.
I'm not seeing any myself, though I do reboot the phone about once a week just as a precautionary measure with L's RAM management.
Was having this issue with Stock and Custom ROMS ended up going back to KITKAT and no problems. Hopefully they will have this fixed with 5.1 that will be released soon.
Stock one is allways the best choise. You must be aware, that the stock one is build by a lot of good developers and custom ones are made by individual enthusiasts. There is nothing wrong with that, but the pure logic here speaks by itself.
Used a lot of different roms
ordered my nexus on release day, used quite a few different roms and i've never had a random reboot.
Hi guys,
I'm experiencing reboots when I push my phone hard. I typically have reboots when I'm using Chrome to view webpages in desktop mode or when using GPS (Google Maps, Waze). I've used two different roms and a few different kernels, but seem to be experiencing the same reboots across all platforms (and various rom/kernel combinations). Any help would be greatly appreciated!
Device: T-Mobile Samsung Note 5 64GB
Recovery: Philz Touch
ROMs used (COJ5):
Hyperdrive RLS2
Hyperdrive RLS3
fOrEvErLoCo's BrEaKdOwN R3.0.1
Kernels used:
Stock Hyperdrive RLS2 Kernel
Stock Hyperdrive RLS3 Kernel
Stock fOrEvErLoCo's BrEaKdOwN R3.0.1 Kernel
arter97 N920TW8 9.4 Kernel
arter97 N920TW8 X Kernel
SkyHigh N920T TW LL Kernel
Could this have anything to do with SuperSU?
still random rebooting.
and apparently we currently can't downgrade from COJ5? Double
Any help would be very, very appreciated. Thanks in advance!
Have you odin'd to stock + factory reset?
10-K said:
Have you odin'd to stock + factory reset?
Click to expand...
Click to collapse
As of right now I'm on jovy23's COJ5 Deodexed Stock Rooted Rom, installed after a fresh wipe of cache, dalvik, data, system, etc.
I seem to have found what was causing the reboots. I think it's giving Lastpass accessibility rights.
All throughout the initial installing of apps, the phone never randomly rebooted. Shortly after I got all my apps up and running, the reboots would begin to happen (sometimes twice in 15 minutes.)
Even on this fresh install of the deodexed stock rom, I had one random reboot. Since turning off Lastpass in Settings > Accessibility, I have experienced zero random reboots.
Did anyone else experience this? I'm wondering if it's specifically Lastpass that's giving the phone issues or Accessibility as a whole.
Will try to see if turning off Lastpass on the other kernels and ROMs helps next week and will post an update.
Thanks everyone!