• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Negalite-Blurom | 2.95.651.5 | Virgin-Mobile/Sprint | Sense/Apex/Nova | Aroma | 08-10-2013

First off thank you for this amazing rom! Svn is awesome and easy. I wanted to point out a few things to make sure it's not just me. I'm assuming the apex/nova versions are not supposed to have lock screen icons? No big deal if that's intended just want to be sure.

There seems to be animation lag on the notification drop down menu, it stutters on the way down. Nothing too bad but noticeable. I haven't compared it to other roms so I'm not sure if it's normal or not?

There is also a small delay when opening system settings.

I am using apex with a medium overclock and lagfree governors. These are very small things that don't bother me much, would like to see if it's just me though.
 
Upvote 0
I'd still like to know why I have to be stuck on r82. My apps are moved to the sdcard natively through settings. When I update to r94 it says all my apps are there to click on but says app isn't installed upon execution. And in the Manage Apps section of settings it says they are all there but the icon for every one that was moved to the sdcard is nulled and just a basic grey icon. Any ideas? I miss when questions were answered quickly. x[
 
Upvote 0
I'd still like to know why I have to be stuck on r82. My apps are moved to the sdcard natively through settings. When I update to r94 it says all my apps are there to click on but says app isn't installed upon execution. And in the Manage Apps section of settings it says they are all there but the icon for every one that was moved to the sdcard is nulled and just a basic grey icon. Any ideas? I miss when questions were answered quickly. x[

Perhaps you're wiping the SD-ext partition (or whatever it's called) on the SD card through Aroma. I don't move any apps to the SD card, so I can't relate to your issue or even start to help you on this.

I know it's not an actual fix...but if you want to move up to r100 (I strongly suggest that you do)...move all your apps back off the SD card, then make a backup and then install r100...making sure NOT to delete the /data partition in the aroma options. You can move the apps back afterwards if that's how you want to roll.

Perhaps later, someone can actually find a way for you do exactly what you want without having to move the apps over.
 
Upvote 0
I had some trouble with r100. I flashed it today and wiped everything except data. One time, during a wake up, the face recognition failed, and the picture of my face was frozen on the screen for like 15 seconds...then the scren turned off...and the phone ended up rebooting. I of course shrugged that off.

Then, about 30 minutes ago, I went to text someone, and the phone wouldn't turn on. I had to pull the battery, boot to recovery, and restore my r91 NAND.

Do you think I did something wrong with the "dirty flash"? One thing I did differently was I left off one of the optional HTC apps (talkback) when I installed r100...so could there be something in my /data partition that didn't get wiped causing a stink?
 
Upvote 0
I had some trouble with r100. I flashed it today and wiped everything except data. One time, during a wake up, the face recognition failed, and the picture of my face was frozen on the screen for like 15 seconds...then the scren turned off...and the phone ended up rebooting. I of course shrugged that off.

Then, about 30 minutes ago, I went to text someone, and the phone wouldn't turn on. I had to pull the battery, boot to recovery, and restore my r91 NAND.

Do you think I did something wrong with the "dirty flash"? One thing I did differently was I left off one of the optional HTC apps (talkback) when I installed r100...so could there be something in my /data partition that didn't get wiped causing a stink?

r101 has many issues fixed, including working handcent. best to move on ;)

Lol nega, i just got logcat and that stupid handcent crap so see why its crashing on so many roms, it doesnt work on mobsters either, i have zero interest in it but was going to do it for you haha, fck it ;)

haha I beat you to it :p
 
Upvote 0
r101 has many issues fixed, including working handcent. best to move on ;)



haha I beat you to it :p

I can already tell I'm going to have problems with r101 (fingers crossed). Kernel Tuner isn't getting the "Kernel Tuner has been granted SU permission" message like before. I had to go back a version on KT to make r91 stable and I feel there's something different about KT nowadays.

My 2D GPU won't go over 228 no matter what I try.

I'll keep running it until it starts to act up, then it's back to my r91 NAND...or perhaps I'll have to downgrade Kernel Tuner to 4.4.5 and stay on r101.

Is anyone able to get his 2D GPU up to 266? I can lower it to 200, and after closing the slider and accepting the changes, it goes to 200...but then when i try to raise it back to 228, it stays at 200, and raising it to 266 leaves it at 200 still (not 228). WTF?!?!?!


EDIT:

OK, well, the phone lasted maybe an hour...then it wouldn't wake up. S2W worked, as when i hit the menu button, my capacitive lit up. I was also able to take a screenshot of the lockscreen...but the actual LCD wouldn't turn on. So I guess the phone woke up, but the screen refused to turn on. After a battery pull, I am back on my r91 NAND.

I think I'll be forced to side load Kernel Tuner 4.4.5 from now on...and it's totally blowing my mind that I am the only person affected by this.
 
Upvote 0
Have you ever noticed a difference between 200 and 266?

I can't say that I've tested it. Is also not the point.
I have noticed the difference between my phone rebooting on its own and it running smoothly . The gpu issue is merely a symptom. The greater issue for me is that my system is unstable on kernel tuner versions above 4.4.5.

Can you confirm for me your kt version as well as your 2d gpu?
 
Upvote 0
Kernel tuner 4.4.7.1, 2d=266, 3d=320. We seem to be at opposite ends, unlike numerous other people, I have never had any problems with kt losing my settings or any sort of reboot issue with Anthrax. Very strange to say the least. :thinking:
OB

Damnit. I was hoping this wasn't just me. One thing different is our kernels. I am leaving it at buttered toast. Fresh install of r101 with no backed up data (to eliminate variables) and my gpu won'tgo over 228. In addition, lowering it to 200 means I can't raise it back to 228 without a reboot. Again these are all symptoms, I think the main issue is that I don't get the kt had been granted superuser permission message when making changes.

I appreciate your feedback. I was hoping for a sample size greater than 1 but beggars can't be choosers. Enjoy your flawless rom...I'll continue to bang my head against the wall. :p

One thing I just thought of, which superuser are you using? I've always left it at the default which is the last one on the list in aroma. How do the 4 options differ? Why bother having 4 options if they are all identical? Surely they must differ in sombre way.
 
Upvote 0
Well there's the original su by koush, the SuperSU by chainfire and the new superuser by the CM team, not sure about a fourth option. It's a personal preference thing, some people like the open source of the new superuser, I like SuperSU because I seem to have fewer issues than with the original SU. I've been using SuperSU since it was released, why don't you go into your superuser app and tell it to forget kt, then launch kt and give it su permission?
OB
 
  • Like
Reactions: Palmetto Fellow
Upvote 0
Well there's the original su by koush, the SuperSU by chainfire and the new superuser by the CM team, not sure about a fourth option. It's a personal preference thing, some people like the open source of the new superuser, I like SuperSU because I seem to have fewer issues than with the original SU. I've been using SuperSU since it was released, why don't you go into your superuser app and tell it to forget kt, then launch kt and give it su permission?
OB

Here are the 4 options in aroma:

CWM Superuser (Koush)
MIUI Security (MIUI)
SuperSU (Chainfire)
Superuser (ChainsDD)

I'm going to use the one you use as I have absolutely no preference in this regard (well, whichever one works better would be the preferred one)

I've been using Superuser (ChainsDD) this whole time BTW. Gonna try installing r101 again...bone stock without any /data partition backup (full wipe) and see what happens.

EDIT:

Well, Kernel Tuner still isn't giving me that message about SU permission after each change, but I was able to manage getting to 266 on my GPU after a reboot...so that's progress :)
Since I am at a fresh install with a full wipe, I have a good hour or so of tweaking to get back to where I was...actually, I'm probably going to have to restore my r91 NAND, backup my phone log, SMS, and apps...then do a full wipe and start over with r101. In fact, i better check to see if r102 is out before moving forward ;)

I don't want to save my data partition as I want as few variables as possible.
 
Upvote 0
When I go to the link to download the ROM it mentions in instructions that I need to only backup data and if I moved apps to the sdcard I should backup sdext and sdext2. Now that's weird... I don't have a partitioned sdcard. So how would moving my apps to the sdcard natively be the same as backing up sdext and sdext2 in recovery? I don't understand that. I didn't use Apps2SD or Links2SD. Just went into Manage Apps and went to the SDCard Tab and moved all of them except 2. Android Assistant (breaks widget capability) and TiBu, just in case something goes wrong.

As far as I knew Sdext is a whole nother level of where apps are installed and that's completely installing and linking every piece of them there. Natively moving them just moves all the data to /sdcard/Android/data/ right? Am I missing something? Someone please fill me in. I'm still getting used to the partitions on this phone since before I had an Optimus Elite which had an Internal 2Gb sdcard and an /_ExternalSD/ which was the physical one you'd insert. Weird phone I know...
 
Upvote 0
My phone must have a hardware issue. I can't run r101 at all now. It loads just fine, but it won't reboot either normally, or to recovery. Even with the older Kernel Tuner (4.4.5) it doesn't wake up properly all the time...and I have to pull the battery. Just now, I rebooted because WiFi wouldn't turn on...and enabling airplane mode didn't work to break it out of the attempt to turn on WiFi...so I figured a reboot was in order. Well, the reboot isn't working...so I gotta pull the battery. I am going back to r91 (which runs flawlessly BTW)

At this point, since nobody else is having these issues, it must be my phone. I am running it bone stock, with no user data at all. :(

EDIT:

After a battery pull, and 3 successful reboots in succession...I've decided to keep r101 until something else BAD happens. WiFi is now turning on fine...so we'll see.

EDIT again:

I spoke too soon. About 30 seconds after my previous edit, the phone just shut off. It's so odd to me that a bone stock install of r101 can have this much trouble, but my r91 NAND never skips a beat. Looks like I'll be stuck in r91 for awhile...and whenever nega comes out with r105-ish, I'll give that a try.

If it's a hardware issue, why does r91 run fine for me? Does r101 exploit a weakness in my hardware in some way that r91 doesn't?
 
Upvote 0
My phone must have a hardware issue. I can't run r101 at all now. It loads just fine, but it won't reboot either normally, or to recovery. Even with the older Kernel Tuner (4.4.5) it doesn't wake up properly all the time...and I have to pull the battery. Just now, I rebooted because WiFi wouldn't turn on...and enabling airplane mode didn't work to break it out of the attempt to turn on WiFi...so I figured a reboot was in order. Well, the reboot isn't working...so I gotta pull the battery. I am going back to r91 (which runs flawlessly BTW)

At this point, since nobody else is having these issues, it must be my phone. I am running it bone stock, with no user data at all. :(

EDIT:

After a battery pull, and 3 successful reboots in succession...I've decided to keep r101 until something else BAD happens. WiFi is now turning on fine...so we'll see.

EDIT again:

I spoke too soon. About 30 seconds after my previous edit, the phone just shut off. It's so odd to me that a bone stock install of r101 can have this much trouble, but my r91 NAND never skips a beat. Looks like I'll be stuck in r91 for awhile...and whenever nega comes out with r105-ish, I'll give that a try.

If it's a hardware issue, why does r91 run fine for me? Does r101 exploit a weakness in my hardware in some way that r91 doesn't?

Are you arguing with yourself again? Haha Jk. I need to sort the framework out for vm users. You aren't alone in this vm side
 
Upvote 0
As far as I knew Sdext is a whole nother level of where apps are installed and that's completely installing and linking every piece of them there. Natively moving them just moves all the data to /sdcard/Android/data/ right? Am I missing something? Someone please fill me in. I'm still getting used to the partitions on this phone since before I had an Optimus Elite which had an Internal 2Gb sdcard and an /_ExternalSD/ which was the physical one you'd insert. Weird phone I know...
The best way to address your question is by reading the seventh question and answer in the link2sd FAQ.

The sd-ext partition is used by link2sd but the sd-ext2 partition is typically used for a swap file, something that's really not needed on the Evo 3D/V.

ramjet73
 
Upvote 0
I said I don't use Links2SD or Apps2SD. My SDCard isn't partitioned for it. I just go to Manage Apps and move them to the sdcard NATIVELY through Android.
I thought you were looking for an answer to how sd-ext and sd-ext2 are used and when you would need to back them up.

It still might be a good idea to read the Q&A I linked as there are some pretty significant differences between link2sd and the native move app to SD card, and you are more likely to have problems when changing ROM's or mounting the SD card as USB storage using the native facility. With link2sd you can just re-link the apps that have already been installed to the sd-ext partition.

If you are happy with the native apps to SD support and it doesn't cause any problems for you then don't worry about backing up the sd-ext partition since you don't have one anyway. ;)

ramjet73
 
  • Like
Reactions: negamann303
Upvote 0
I thought you were looking for an answer to how sd-ext and sd-ext2 are used and when you would need to back them up.

It still might be a good idea to read the Q&A I linked as there are some pretty significant differences between link2sd and the native move app to SD card, and you are more likely to have problems when changing ROM's or mounting the SD card as USB storage using the native facility. With link2sd you can just re-link the apps that have already been installed to the sd-ext partition.

If you are happy with the native apps to SD support and it doesn't cause any problems for you then don't worry about backing up the sd-ext partition since you don't have one anyway. ;)

ramjet73

I don't think he's 100% happy as he has issues when updating. Any idea what's going on? I speculated that he was wiping the sd card partition in aroma that would hold the moved apps. That doesn't seem to be the case.

Hatred, were you able to locate the moved apps on the SD card? Are they still there?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones