Database Users

Nero V5 BIZARRE Data connection issue

So its impossible to get any sort of input on the Nero 5 thread with 3 posts a minute, so thought its give it a shot here.
Hello all, this is the honest truth. When my vibrant is sitting untouched, it has almost full 3G data with 2-4 Mbs/sec speed. Then when i pick it up within 10 seconds its gone into edge network with .05 Mbs/sec.
I so hoped this was just my imagination, but i played with it for 5 minutes, undesputable results. The action of picking up my cell causes it to loose immediate data reception. If no one else had this issue i will ODIN to stock and reflash. But is this a problem with the rom or kernal?

I'm on nero v5 and I don't have that issue.
Sent from my SGH-T959 using Tapatalk

I don't have this issue either... Your plan to odin back to stock and try flashing Nero V5 again has some merit but you might also try one of the other Radios from the development section. I believe that any of the 2.2 radios will work with Nero V5...

I think its the kernal, I have no data at all. I check under mobile network, it tells me no sim card.
Sent from my SGH-T959 using Tapatalk

It must have been the kernal, i flashed dragon kernal 2.8 with voodoo sound, and WOW, i mean the data connection is stable, but the real catch is voodoo sound. it blew my mind, who knew vibrant was even capable of such greatness. There is an overclocked version and a stock version. I'm running the overclocked and its lighting but you do need to do some car charging to get through the day safely. And questions ask, but i HIGHLY reccomend. dragon kernal 2.8 with Nero 5, perfect combo indeed.

What exactly is voodoo sound?
Sent from my SGH-T959 using XDA App

i also think its the kernel thats why i downgraded back to 4.1 and i'm waiting for v6 with the new ka6 kernel. supposedly that is much better then the ka5 with fast gps locks, but i haven't tested it yet cus i'm waiting for the new nero

bossman137 said:
It must have been the kernal, i flashed dragon kernal 2.8 with voodoo sound, and WOW, i mean the data connection is stable, but the real catch is voodoo sound. it blew my mind, who knew vibrant was even capable of such greatness. There is an overclocked version and a stock version. I'm running the overclocked and its lighting but you do need to do some car charging to get through the day safely. And questions ask, but i HIGHLY reccomend. dragon kernal 2.8 with Nero 5, perfect combo indeed.
Click to expand...
Click to collapse
Glad you found a right combo to your liking and took care of your data issue. I had some bad luck with the Dragon kernal, both stock and oc. The Dragon oc twice soft brick my phone and I had to odin back both times. After that I said hell with it, let me try the stock version. Yep, soft bricked again. I still haven't given up on it. I'll get it one of these days. Maybe it's my specific phone that's not liking it. Lol.
Sent from my SGH-T959 using Tapatalk

I have this problem, too. I thought maybe it was just me...Right after I flashed Nero v5, my data connection went to hell and I've been battling it all morning. Maybe I'll try going back to stock and seeing if that helps.

How many of you are happy with EB13?

I updated my Epic on the day EB13 was released. I used the update.zip using the stock recovery on my stock/rooted DI18 (no data/cache wipes before updating) which kept all my data and apps intact. After the update, the only problems I had were the one related to the camera (video lag in low light and still camera FC in sport mode), but after the kernel fix was introduced (thanks to mkasick) I have had absolutely ZERO, ZILCH, NADA, NO problems. Granted I am still using basically the stock EB13 rooted only with Launcher Pro, but everything has worked as it should (GPS, SMS, MMS, video recording, camera, music player, SD card, etc.). The only issue for me is probably the checkerboarding on the stock browser which is not a big deal for me anyways.
How many of you have been happy with your EB13 upgrade experience?

I am waiting for a custom ROM.

Mine worked good on stock and even better using the genocide kernel.
Sent from my SPH-D700 using XDA App

I'm running a beta build of a custom rom and I couldn't be happier. I'm not having any of the issues reported
Sent from my SPH-D700 using Tapatalk

I've been very happy with the upgrade, I haven't ran into any problems with this build. Now I'm just waiting for the developers to really start pushing out their releases! Dying to get my hands on a official CM6.2 and MiUi!
Sent from my SPH-D700 using XDA App

Already running Midnight rom with the Genocide kernel. Getting great battery life and my GPS definitely feels improved. Haven't dropped signal during nav yet (knock on wood)
Can't wait for more Roms and especially updated Cyanogen and Miui like above.

Running EB13 with midNIGHT ROM 4.1....my phone runs great, better than when it was on a DK28 mod

Mine runs great all stock EB13

raylusk said:
Mine worked good on stock and even better using the genocide kernel.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Whats the genocide kernel? what advantages does it have over the stock eb13 kernel?

shahin26 said:
Whats the genocide kernel? what advantages does it have over the stock eb13 kernel?
Click to expand...
Click to collapse
The Genocide Kernel, is a kernel made my one of the Devs here. You can find it's thread in the Development section for more details.
Sent from my SPH-D700 using XDA App

I was using stock EB13 with no problems..today I flashed the genocide kernel since I figure it can't hurt to have more battery life...
As for checker-boarding on the browser..coming from a TP2..I hardly call that checkerboarding lol

as for the checkerboarding browser, does anyone know if that is only on the stock browser, or others such as Dolphin as well?

Running EB13 stock w/genocide, no complaints. I use the miren browser as my default.
Sent from my SPH-D700 using XDA App

I flashed eb13 with the samsung exe and immediately got root access and changed over to deodexed/ext4 and with the lastest genocide kernel .... close to perfect ... with the overclock and pretty heavy use battery life is darn good, amazingly. My battery app estimates 11.5 hrs @ 58%. I'm constantly picking the thing up and using it today. All apps run fine and now the browser is substantially faster than the wifes laptop! Was just on the gamestop site with a flash game review playing along side a bunch of animated adds and it still played great. 1375/3020 smartbench. This is all the "phone" I'll need for some time to come! Since the camera fix in genocide kernel, all regrets are gone. Plus, if you love video media like I do, you MUST have 2.2 as the video decoding and audio decoding are sgnificantly improved. 2.1 would stutter a bit with very high bit rate stuff. 2.2 makes the best quality video play FLAWLESSLY. Never a dropped frame. Even @2mbit/sec. Watching a movie on my phone is nearly as pleasing as my well calibrated big screen.
Sent from my SPH-D700 using XDA App

EB13 is pretty good. Except for the bt voice dialing not working. If you don't have this issue what update method and what rom are you running???
Epic 4g

I'm happy. the battery is lasting for up to 24 hours now. I even slept through the night without charging it and woke up to a not dead phone. oh the possibilities

stock eb13 w root and cam patch, couldnt b more pleased w my phone

Not me. Its seems much better at first. But when you start getting random fc's here and there it tells you somethings wrong. In all honestly I think 2.1 eclair ran this phone with ease like a current machine would run winxp. No problems and everythings snappy. Works the way its suppose to. Throw win7 in and now youve complicated things by adding in bore instruction sets that might conflict. Not to say that it isn't gonna work well but we can clearly see sprint was full of **** when they said they were thoroughly testing for bugs. Build the is from the ground up with gingerbread. Until that happens were gonna keep getting updates that fix **** instead of updates that turn our epics for the better. Its what this hardware deserves. Next year when tegra 2's are mainstream phonemena hummingbird will be the mid level tier. Even with 2.2 I still think this hardware has more to give.
My 2 cents.
Sent from my SPH-D700 using XDA App

RushAOZ said:
Not me. Its seems much better at first. But when you start getting random fc's here and there it tells you somethings wrong. In all honestly I think 2.1 eclair ran this phone with ease like a current machine would run winxp. No problems and everythings snappy. Works the way its suppose to. Throw win7 in and now youve complicated things by adding in bore instruction sets that might conflict. Not to say that it isn't gonna work well but we can clearly see sprint was full of **** when they said they were thoroughly testing for bugs. Build the is from the ground up with gingerbread. Until that happens were gonna keep getting updates that fix **** instead of updates that turn our epics for the better. Its what this hardware deserves. Next year when tegra 2's are mainstream phonemena hummingbird will be the mid level tier. Even with 2.2 I still think this hardware has more to give.
My 2 cents.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's impossible in all honesty. With the way people were crying about the 2.2 update to build something from kernel up and redo it people would be crying "gingerbread is taking too long" screw Samsung, and Sprint...

i odin'd back to DI18 a day before EB13 and only restored contacts.
once EB13 dropped, i wiped everything 3 times w/ clockwork, upgraded via the update.zip method. Then did the 1 click root, and manually re-installed all my apps etc.
The one thing that really kills the 'new' froyo for me is the bluetooth problems still being present like on DK28. I got so damn irritated w/ DK28's bluetooth problems that i actually went back to 2.1
Now that i'm using EN13, I'm still pretty honked off but it hasn't irritated me enough yet to go back to eclair.. depends on how flaky the bluetooth becomes.
So far, I'm running stock EB13, 1 click root, genocide kernel installed yesterday) and gonna gauge battery life.
I'm really wanting to try out the MIUI and/or cyanogenmod once they're a little less buggy.. the devs are making great progress, but i need a fairly non-buggy phone for work so that's why i'm waiting (not complaining.. i experiment on the weekends w/ ROMs and such)
my .02

[q] eb13 (all roms and kernels) graphical issues

ok guys i was wondering if any one has had similar issues, or maybe an inkling. seems with absolutely ALL eb13 roms i have tried sydicate,bonsai,frankenstein. i have the absolute identical issues which is 3d is INSANELY choppy it spikes high and goes down very very very low 9fps low.
this result can be produced in nenamark,quadrant,livewallpapers (any of them),etc.
i switched back to bonsai 2 and just am using the new acs kernel and the eb13 modem works like a charm... any ideas why?

More info needed
What were previously on? di18 or dk28? how did you update to eb13? OTA or odin.
did you do a factory wipe x3,cache wipe x3, dalvik cache wipe? Did you restore data from a different rom over a fresh flash? running the correct kernel?
Need more info too narrow down the issue. maybe it's a missed step.

I have not had that issue... I haven't tried many 3d games though. I'm going to give gun bros another chance here soon and report back.
Haven't seen that issue with live wallpapers either

This the first I have heard of these issues did u try flashing more than once
1.2ghz super phone

Can't back you up here, man. I'm on Bonsai 3.0.1. 3D is fine. I get just over 50 in nenamark, average for the Epic. Still my games are smooth and awesome.
You either have installed or configured something that's causing this (most likely), or have a hardware problem.
Sent from my mind using telepathitalk

I'm using syndicate frozen rom and it runs perfect graphics for me
Sent from an EPIC 4G FROZEN and Syndicated

[Q] Random Boots When On a Call

I'm getting Random Bootloops when on calls, or that's when I see it most often. Obviously it's a pain to drop calls in this manner then tell the caller I have the new GS4 I'm currently running ForceRom 2.3 which comes with KT Kernel. The problem seemed to start about 1 week ago while I have been running ForceRom without issues since it was released. I have tried installing Stock Kernel but problem persisted. I even DataWiped and restored a backup but problem is still there. I'm going to try to run fully stock un-rooted next, but wanted to know of any other suggestion.

Kingmdm said:
I'm getting Random Bootloops when on calls, or that's when I see it most often. Obviously it's a pain to drop calls in this manner then tell the caller I have the new GS4 I'm currently running ForceRom 2.3 which comes with KT Kernel. The problem seemed to start about 1 week ago while I have been running ForceRom without issues since it was released. I have tried installing Stock Kernel but problem persisted. I even DataWiped and restored a backup but problem is still there. I'm going to try to run fully stock un-rooted next, but wanted to know of any other suggestion.
Click to expand...
Click to collapse
I have the same problem :/

Joe0113 said:
I have the same problem :/
Click to expand...
Click to collapse
I guess that's good to hear. I have seen many other posts around the Web including here about reboots when using camera, but not my issue. I went ahead and restored everything back to TW MDL stock and left un-rooted for now (I doubt root is the problem though). So far no reboots when on calls, but will need more heavy usage over the next few days. Since I haven't installed any apps and still only using fully stock apps maybe issue could be with a downloaded app. 1 Cool side affect is I have tried Samsung's WatchOn while on stock and I must admit it's truly cool to control all my TVs now, it will be a keeper Are you using a custom ROM, which one?

Are you guys undetvolting your cpu or overvolting or messing with kernel settings at all?
Sent from my SPH-L720 using xda premium

Im glad you asked since that was my concern. I have been using default settings on KT kernel which comes with ForceRom. It seemed problem mostly occurred when screen times-out and on Bluetooth. I thought when screen is off KT UC cpu but problem persisted when using stock kernel.
Sent from my SPH-L720 using Tapatalk 2

Something defiantly hung back from the kernel, if the problem doesn't persist since your on stock MDL now I wouldn't worry about it. My guess was undervolting on kernel BC I had the same problem but it went away after I loaded stock kernel settings
Sent from my SPH-L720 using xda premium

Nexus 7 on Cm 11

Hello guys, I currently own a nexus 2nd Gen it's rooted and running the latest cm 11 nightly build. Sometimes it make a buzzing noise while I'm listening to music or watching videos or it froze and restart itself that happen at least 3-4 times a day. I was wondering if that happens anyone else and how to fix it
Sent from my Nexus 7 using xda app-developers app

I've never had the buzzing but I don't use the speakers much.
The freezing and rebooting I have had both on stock and cm11. Best uptime I'd get was ~24 hours.
After flashing the latest Glitch kernel it's been up for ~106 hours. All location services turned on, syncing, google now, same apps etc.
Too soon to tell I guess but definitely an improvement.

I thought I was the only one it's getting really annoying, other roms are fine

I sometimes have buzzing sound for a short period of time. But I am using stock rooted 4.4.2.

I get this too, also happens in games

happened to me only on stock cm11

I ask this everywhere but does OTG work with latest cm11 nightly for flo? It is important for me since I cannot flash any other kernel to get it working
Sent from my Nexus 7 using Tapatalk

yosmokinman said:
I've never had the buzzing but I don't use the speakers much.
The freezing and rebooting I have had both on stock and cm11. Best uptime I'd get was ~24 hours.
After flashing the latest Glitch kernel it's been up for ~106 hours. All location services turned on, syncing, google now, same apps etc.
Too soon to tell I guess but definitely an improvement.
Click to expand...
Click to collapse
Can you tell all your glitch kernel settings?

Buzzing Noise fix
Flash the stock Android 4.4.2 ROM back on your Nexus 7 and the install Xposed.
Why would you need a custom version of 4.4.2 on your tablet that's already running 4.4.2 when the Xposed Framework works just as well.
EDIT - I've had no problems with buzzing noises or freezing on stock rom with unlocked bootloader and rooted.

Yup - same here. I've actually experienced this on both CM 10 and CM 11. The audio distortion out of the speakers is horrible. CM roms are the only ones that have this problem. I wonder if it has something to do with DSP Manager that's included with the CM Roms??
I agree with previous posters in this thread too - Stock rooted 4.4.2 is all you really need. Been flawless on my N7 2013.

I have the same issue
It usually happens when I watch a video from youtube or twitch. My tablet buzzes like kind of similar to someone getting an answer wrong in a game show.
I just need to go back to stock.

Can confirm that there's a buzz sound and a 1-3 second freeze using the CM11-M2 build.
After flashing the Jan 24 CM11 build, and the glitch kernel (using all stock settings except overclock to 1.7ghz cpu and 500mhz GPU), buzz sound is gone and all is well.

It happened to me with latest cm nightlies, and with all of them I had freezes and hangs. I went back to stock rom with elementalx kernel and i don't have any of these issues. I think cm overall is less stable and faster than stock rom. it's good for non nexus devices, but with nexus is better to stick to stock. I've tried other ROMs as well, nothing compares to stock in performance and stability.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Glitch kernel + cm nightlies = awesome mode
Still have more than 30% battery left

I have a problem with play store. It doesn´t load all the app images. Some of them are just blank while browsing apps.
I have tried latest nightlies, clearing app data and I have even tried a factory reset and I am still experienceing the same problem.
Anyone else having this problem?