Database Users

[Q] DL30 --> EB01 worth it?

Does anybody know exactly what the difference is between DL30 vs EB01? There was another thread asking a similar question, but at best had a vague response of "bugfixes and such".
Does anybody have an idea of what is changed?
Or more specifically... I am currently using a RubikS DL30 ROM. Is it worth the trouble going to an EB01 ROM like BlackHole? Will I notice any difference whatsoever, besides the fact that 20 minutes of my life is gone?

Yes.
In my situation EB01 superclean fixed a few bugs I had.
GPS now works for me.
ALL messaging works for me now too. I had a bug where videos being sent to me did not work and I could not send large (160char+) texts to nonVerizon users.
Plus there are a few more options in the SuperClean build.
So far nothing else seems broken. I'll update if I find different, only had SC2.4 since last night.
EDIT: also I am not on voodoo as I don't see the need to. Phone is already working fast.

Although it is unfair to the EB01 rom, here is my concise list:
+ Flash 10.1 support
+ louder navigation speaker volume
+ auto orientation toggle at top
+ support for real skype - bluetooth still confined to phone dialer only without A2DP or unreliable software hacks
+ cool drag-able cursor in text entry
+ seems a bit smoother than stock, about as good as a custom ROM
+ Bing isn't as bad or as obtrusive as it used to be
- inaccurate clock bug (slow), alarm sometimes fails
- WIFI sucks battery while screen off
- various bugs that are hard to reproduce or avoid, yet generally easy to resolve
- reinstall kernel and flash modem to un-brick if you decide to restore back to DL09
Swyped w/ XDA App. When in doubt, mumble.

Yes!! Noticable battery life improvement. Plus EB01 is the new standard now. Themes and mods will be based on EB01.
I actually like my Fascinate

Absolutely, DL30 was really buggy. Not in a obvious way all the time, but just little things that didn't work as they should. EB01 has been rock solid for me.

bionix-v - all sounds stop working randomly

Hello, I'm hoping someone can help me with this issue. I have been running stock 2.2 for a while, but decided to flash a new ROM today and chose bionix-v. I had been running Nero previously and was very happy with it except for this random problem that would occur once in a while. Randomly, I would lose all sounds (notification sounds, sound when changing volume, shut down, etc) and rebooting would immediately cure. After installing bionix today at lunch, this has happened twice to me today. I checked all volume levels with this occurs, switch in and out of silent mode, but need to reboot to get sounds working again. Never had this problem when running stock ROMs.
Any help/advice greatly appreciated as I love this ROM but need sounds to work normally. Thanks.

gatorbob said:
Hello, I'm hoping someone can help me with this issue. I have been running stock 2.2 for a while, but decided to flash a new ROM today and chose bionix-v. I had been running Nero previously and was very happy with it except for this random problem that would occur once in a while. Randomly, I would lose all sounds (notification sounds, sound when changing volume, shut down, etc) and rebooting would immediately cure. After installing bionix today at lunch, this has happened twice to me today. I checked all volume levels with this occurs, switch in and out of silent mode, but need to reboot to get sounds working again. Never had this problem when running stock ROMs.
Any help/advice greatly appreciated as I love this ROM but need sounds to work normally. Thanks.
Click to expand...
Click to collapse
Its not just bionix, i think it has to do with KB1 based roms
I have read reports of people on trigger having this issue
Im on Axura and have experienced it a few times and i agree that it is very annoying however easily fixed by going into settings and reselecting the notification sounds or rebooting.

I had been starting to think it was just me since I could not find much of anything when searching.
So besides the reboot, what exactly do you need to do to fix without reboot? Just change your notification sound under Settings | Sound?

I have not had this issue what so ever,have you tried reflashing?
Using Bionix V-1.3 w/a Splash of Color,Bionix Dark Market,Linda's voice,& few more fantastic mods from the worlds greatest Devs @ XDA

gatorbob said:
I had been starting to think it was just me since I could not find much of anything when searching.
So besides the reboot, what exactly do you need to do to fix without reboot? Just change your notification sound under Settings | Sound?
Click to expand...
Click to collapse
thats exactly what i do. tho rebooting is often the easiest for me one button press and im back up and running in a couple seconds.

carlcj5 said:
I have not had this issue what so ever,have you tried reflashing?
Using Bionix V-1.3 w/a Splash of Color,Bionix Dark Market,Linda's voice,& few more fantastic mods from the worlds greatest Devs @ XDA
Click to expand...
Click to collapse
Have not since I had the same problem with Nero too. Had been running stock 2.2 until yesterday without the problem. Even went back to stock JFD before flashing bionix.

Nexus 4 Lockscreen Lag

I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?

nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much

brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.

Flash a custom kernel. You'll be less likely to experience lag

Don't get any lockscreen lag on my stock Android.

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?

nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.

username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?

Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.

username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.

I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?

Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.

for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.

if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!

sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag

I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?

I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4

Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?

Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip

meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.

[Q] Vibration Intensity Continually Decreases

Hi all,
I have a Galaxy S4 which I have recently flashed CM 10.1 onto, having used another JB custom ROM until then. I have a problem with the vibration. It seems to be working fine after every reboot, but then as I start typing messages and using other functions the intensity of each vibration seems to die a little bit more until it stops vibrating altogether (haptic, notifications, everything). A reboot will cause it to get back to normal again but the same thing seems to happen.
I can't recall if this was happening before first flashing/rooting the phone, so I'm not sure if it's a straight hardware issue. Any pointers?
Thanks

Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?

That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)

Te3k said:
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Click to expand...
Click to collapse
emckai said:
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
Click to expand...
Click to collapse
I'm still new to this so it's a slow and somewhat painful process, but I just reflashed stock today and there doesn't seem to be an issue at all.
I stumbled across this thread where it appears it's a CM10.1 problem. Suggested fix is to disable haptic, reboot, enable haptic. When I get the patience to re-flash and set up my device again I'll give it a shot.

Freezing issues/Best ROM similar to RR?

Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.

Latiken said:
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Click to expand...
Click to collapse
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.

B!Gguy said:
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
Click to expand...
Click to collapse
What kernel do you use for it? I'm gonna go ahead and try it.

Latiken said:
What kernel do you use for it? I'm gonna go ahead and try it.
Click to expand...
Click to collapse
No custom kernal. Stock one's good enough.