yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bigrushdog:
I've known for some time this was an issue on the toro builds. But this is the first I've heard of it affecting toroplus. As you might have guessed I don't use bluetooth. Bad news is I have no clue what is causing it, yet. Good news is now I know whatever it is is a shared resource across the tuna family of devices. Guys do some testing. Try different kernels. Try bluetooth tether. Is it only phone audio or a2dp?
[Samsung Galaxy Nexus] nicholishen:
Both in my experience. The audio clips out when playing music and will disconnect but still showing as paired. Same on calls.
[Samsung Galaxy Nexus] tyea:
After a round of all the latest 4.1.2 ROMs, I'm back to eos60. The 10/12 peter Alphonso ROM seems to have better stereo Bluetooth transmission. I noticed the 4.1.2 ROMs that felt fast and fluid were ones that used the sept 10 stock kernel. Thanks for supporting SPH-L700.

SPH-L700, Tapatalk
[Samsung Galaxy Nexus] bigrushdog:
We're actively researching the bluetooth issue. Should have it fixed up soon.
[Samsung Galaxy Nexus] cgrimes5:
Excellent Ram Management

Very impressed with is the Ram management the best I have seen, had it installed on a friends phone we did a comparison and I changed ROM's lovely. I do have a question, maybe I'm missing something and someone can help me.

I use the Darkjelly Theme and some of the transparent features are not working a comment was made about "new aosp commit for contacts" not merged.

Any suggestions or help would be greatly appreciated! Now leaving anyway, just wanted to see if it was quick fix.
[Samsung Galaxy Nexus] bigrushdog:
Is Darkjelly a theme changer theme? If so I can dig around for fresh updates.
[Samsung Galaxy Nexus] cgrimes5:
I don't believe so. Here is the link, if it helps. Thanks for taking the time to answer.

http://xdaforums.com/showthread.php?t=1738312
[Samsung Galaxy Nexus] fallguy0980:
I have installed a couple different roms and really like this one. I have a galaxy nexus, I unlocked, rooted, and flashed it to Cricket. My question pertains to the this rom on the 3g internet. When its on wifi, its great, but whenever I disconnect the wifi, or turn on the screen without wifi enabled. The 3g data takes a minute or longer to initiate, then once it is initiated, a speed test shows its very very slow. Much slower than the phone i just transferred from. 700kps vs 120kps. So what gives? Did I miss some network settings, or not enter an ip address/gateway somewhere? How come this takes so long to initiate a connection, and how come its soooo slow once it does initiate? Any ideas guys? I would really appreciate anyone's input. Thanks again, Gary
[Samsung Galaxy Nexus] Crwolv:
Its a T-Mobile theme chooser theme. actually all of his are pretty much the best themes he has become a friend of mine because when you ask for something in the theme he pretty much does it pretty right quick, great guy awesome themes!!
[Samsung Galaxy Nexus] ajf64:
Try uber jelly is alot better looking to me still a black theme but with a blue glow its really nice i would check it out

you can look at it here one good thing is he added a few different colors to it as well

http://xdaforums.com/showthread.php?t=1741949
[Samsung Galaxy Nexus] bigrushdog:
I got updates for contacts and mms in open. And I saw the theme engine commit for them as well. Ya that's my man UBER I talk with on the N7 board. Maybe he can make an official Eos theme...
[Samsung Galaxy Nexus] ajf64:
that be sweet that is my main theme as of now i love it smooth every thing works be even better if it was made specifically for eos this is by far the best rom i have ever used for any phone to date even CM.
[Samsung Galaxy Nexus] 94SupraTT:
Is anyone else having an issue with Bluetooth tethering? I'm tethering off my fascinate and the connection randomly drops. Also the 3g indicator stays on even though it really isn't on.
[Samsung Galaxy Nexus] slyd0997:
I think bluetooth is a known issue. He's working on it.
[Samsung Galaxy Nexus] 94SupraTT:
Is face unlock force closing for anyone else?
[Samsung Galaxy Nexus] Marescallus:
For some reason my Quick Launch Shortcuts don't show up on my Lock Ring.

:Snarf Snarf:
[Samsung Galaxy Nexus] nibrwr:
Did you save your shortcuts before backing out of the menu?
[Samsung Galaxy Nexus] ÜBER™:
Well that's nice I dont have to advertise my themes others do it for me :D

Well see about that theme. :cool:
[Samsung Galaxy Nexus] ajf64:
:) would greatly appreciate it
[Samsung Galaxy Nexus] Marescallus:
What do you mean save them? They are still there even if i clear the Settings app and re-open it.

:Snarf Snarf:

---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------

I'm pretty sure, because when I clear the Settings app and re-open it; it's still there.

BTW sorry about the blank post.

:Snarf Snarf:
[Samsung Galaxy Nexus] ÜBER™:
Whatever i can do to get rid of those honkering EOS Toggles LOL.. things are an eyesore... couldnt you just review the code for the PowerWidgets from CM? I love those holo toggles. Would keep me from having to use Extended Controls on my N7 :D. BRD? That seem fair enough... (hardly) If you could get the CM toggles put in and i will do a Team EOS theme for ya? :cool:
[Samsung Galaxy Nexus] bigrushdog:
That's the beautiful thing about themes :p any decent theme will change them for you. The naming convention is fully compliant. And, just maybe, you can see my desire for a eos theme :p

And I'd rather have god awful icons than have people think we're just another cm kang build :angel:

Oh: and I'm doing some interesting work with the indicator scheme. Should be fun. Low profile mode and Fat Finger Fix in next nightly
[Samsung Galaxy Nexus] ÜBER™:
Thats alright i should know better than ask somebody to revert or copy somebody else.. i absolutely hate when somebody asks the same of me :silly:. Thanks those toggles are a little gigantic and i guess ill have to look into themeing them.
[Samsung Galaxy Nexus] bigrushdog:
It's interesting you say that. Many have reported they like the larger size as it is easier to press the toggle. You know the drill, can't please everybody. Usually...
[Samsung Galaxy Nexus] zackandethan:
Hey guys, sorry to troll here but seen this in the nexus 7 thread and noticed thru goo manager you had a nexus s 4g ROM . Been running since last night on my ns 4g and I'm blown away . Just wanted to thank team eos for their work !
[Samsung Galaxy Nexus] bigrushdog:
By all means welcome. Is crespo4g still lingering in general? We should have it in a dev thread by now.
[Samsung Galaxy Nexus] zackandethan:
Thanks. I didnt see it in the general section although I may have missed it . Hell of a ROM though !
[Samsung Galaxy Nexus] 94SupraTT:
Face unlock is working on newest nightly. There is an issue however with the signal bars. I am using Bluetooth tethering from my fascinate for data but the 3g indicator is on.
[Samsung Galaxy Nexus] slyd0997:
Just clean flashed 60. and I see 61 is up. The story of my life. :) EVERYTHING I need is perfect.
[Samsung Galaxy Nexus] cgrimes5:
Perfect!

Just flash the update and I can run my favorite theme complete very happy this this ROM!!!! Great Job and Support
[Samsung Galaxy Nexus] cgrimes5:
Unfortunately, System UI has stopped

What is the cause for the message Unfortunately, System UI has stopped. I notice that my wallpaper will disappear for a few seconds and come back, other times I have to reboot my phone, or lock it and unlock. Just wondering what is causing this, it has had a couple of times the last few weeks. Any help would be greatly appreciated.

Thanks in advance!

Nightly 61 and Lean Kernel latest Exp.
[Samsung Galaxy Nexus] umbra6:
The only time I get the SUI crashing is when I use a different kernel after a reboot. If I use the kernel that comes with the rom I never get that message.
[Samsung Galaxy Nexus] riassan:
What kernel are you using?
[Samsung Galaxy Nexus] cgrimes5:
Unfortunately, System UI has stopped

I did see the previous post, I posted the same question on the Lean Kernel Thread, and was advised that it was not the Kernel. I just want to know what are the possible reasons this could happen. I have re-installed everything and will see if I experience the problem again. I'm using the latest exp Lean Kernel, which this ROM was recommended on that thread.
[Samsung Galaxy Nexus] R0axet:
Build 61

Same here system UI just craps every now and then. I thought maybe it was APEX. I removed it. Still pursists. :confused:
[Samsung Galaxy Nexus] bigrushdog:
And... What's the rule if we post about a fc? Yes! Logcat ftw! I use lean kernel and I assure you its not the kernel.
[Samsung Galaxy Nexus] riassan:
Are you using a theme and if so which one. Try it without the theme and see if your outcome is the same
[Samsung Galaxy Nexus] Sharpe351:
Does anyone know if WiFi-direct is working?

sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ajf64:
i use uber jelly for a theme and it works great i highly suggest it
[Samsung Galaxy Nexus] mkonei:
Let me know if this helps any, I have no clue what the hell any of it means....nightly 61 with a Franco kernel. I get them randomly throughout the day, started around nightly 58 i think.

u0_a35@android:/ $ logcat

--------- beginning of /dev/log/main

I/dalvikvm(22888): Turning on JNI app bug workarounds for target SDK version 11...

E/Trace (22888): error opening trace file: No such file or directory (2)

E/Term (22888): onCreate

D/dalvikvm(22888): GC_FOR_ALLOC freed 123K, 48% free 2357K/4483K, paused 10ms, total 10ms

I/dalvikvm-heap(22888): Grow heap (frag case) to 5.208MB for 1048592-byte allocation

D/dalvikvm(22888): GC_CONCURRENT freed 3K, 40% free 3377K/5571K, paused 11ms+1ms, total 25ms

D/dalvikvm(22888): WAIT_FOR_CONCURRENT_GC blocked 9ms

D/Term (22888): TermService started

I/TermService(22888): Activity called onBind()

I/Term (22888): Bound to TermService

I/TermService(22888): Activity binding to service

D/dalvikvm(22888): Trying to load lib /data/data/jackpal.androidterm/lib/libjackpal-androidterm4.so 0x41000950

D/dalvikvm(22888): Added shared lib /data/data/jackpal.androidterm/lib/libjackpal-androidterm4.so 0x41000950

I/libjackpal-androidterm(22888): JNI_OnLoad

I/Term (22888): waiting for: 22918

D/dalvikvm(22888): GC_CONCURRENT freed 92K, 36% free 3740K/5827K, paused 12ms+13ms, total 37ms

D/dalvikvm(22888): GC_FOR_ALLOC freed 10K, 36% free 3835K/5955K, paused 12ms, total 12ms

I/dalvikvm-heap(22888): Grow heap (frag case) to 6.726MB for 1127536-byte allocation

D/dalvikvm(22888): GC_CONCURRENT freed <1K, 31% free 4936K/7107K, paused 11ms+2ms, total 23ms

I/Term (22888): Subprocess exited: 129

E/Term (22888): onCreate

D/Term (22888): TermService started

I/TermService(22888): Activity called onBind()

I/Term (22888): Bound to TermService

I/TermService(22888): Activity binding to service

I/Term (22888): waiting for: 23021

I/Term (22888): waiting for: 23066

I/Term (22888): Subprocess exited: 129

D/dalvikvm(22888): GC_CONCURRENT freed 459K, 32% free 5336K/7811K, paused 12ms+22ms, total 62ms

I/Term (22888): Subprocess exited: 129

E/Term (22888): onCreate

D/Term (22888): TermService started

I/TermService(22888): Activity called onBind()

I/Term (22888): Bound to TermService

I/TermService(22888): Activity binding to service

I/Term (22888): waiting for: 23131
[Samsung Galaxy Nexus] tyea:
EOS61 + Franco 295/384

I noticed the torch toggle inconsistently works. The graphics of the toggle switch indicates torch is on but the light doesn't come on. If I toggle it 3 or 4 times it will eventually come on. There is still noticeably poor signal connectivity with stereo Bluetooth. Close proximity Bluetooth works fine, but it seems like the connectivity is not as stable as some other ROMs. I'm certain the distance I can listen via Bluetooth is less than some other ROMs. Otherwise, the ROM is a pleasure to use. Thanks again.

SPH-L700, Tapatalk
[Samsung Galaxy Nexus] ajf64:
i find the torch has always been finicky and dosnt always work i just stoped using it a long time ago its bad for your flash blub any way
[Samsung Galaxy Nexus] Rooster85:
And how is that!?!? The led on our phones will way outlive the life of the phone its self if ir stayed on constantly!
[Samsung Galaxy Nexus] bigrushdog:
You have managed to find the 2 things keeping me from calling this rom flawless :fingers-crossed: I've been looking into the bluetooth issue and the problem continues to elude me. I think i know why torch is wonky. I'll try to resolve these issues while we wait for KLP to drop.
[Samsung Galaxy Nexus] tyea:
Torch toggle problem also is present in AOKP ROM.

SPH-L700, Tapatalk
[Samsung Galaxy Nexus] bigrushdog:
It has to do with the hacky implementation required for these Samsung devices. There's no function we can just call to turn it on. We actually are forced to create a "fake" camera preview surface, make it transparent, then tell the camera to turn on flash. Also there's no real sure fire way to determine if the flash is actually on or not. It may actually require a custom library to do it right and that is no small task.
[Samsung Galaxy Nexus] ajf64:
was more referring to the heat when used for a long period of time some bulbs give off alot of heat witch can be bad for the bulb and phone also i could just be reading to many horror story's :)
[Samsung Galaxy Nexus] R0axet:
I'm wasn't using a theme.
[Samsung Galaxy Nexus] bigrushdog:
I use Cobalt paid. But could you elaborate?
[Samsung Galaxy Nexus] :
Build 63 running perfectly. I don't even have the issue of the "wonky" torch lol. I don't really use Bluetooth so i cant comment on that. Just wanted to say great work and ive found my new daily.

BTW please do not change the way the notification toggles look, how can people not like them???? i actually really like them a lot lol. ;)
[Samsung Galaxy Nexus] Sharpe351:
62 and 63 have had wonky WiFi. No problems on any other JB build. Other than that working fine.

sent from my Galaxy Nexus
[Samsung Galaxy Nexus] krazyfiend:
+1.. However it might be something in combo of the new LK 4.5 230 kernel w that new wifi while screen off code for myself.
[Samsung Galaxy Nexus] slyd0997:
Pls explain "wonky".
[Samsung Galaxy Nexus] Sharpe351:
Wonky as in won't connect. Sees all the available connections, but won't connect to any. Log cat shows a ton of failed bs when trying to connect to WiFi. It worked fine for a few days after install, but suddenly wouldn't connect. Reboots, fix permissions, etc did not remedy issue. I'm back to another ROM now, that I know has no issues. I have great luck with eos builds on my tf101.

ROM is as installed. Stock kernel, no over clock.

sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ajf64:
im running LK 4.5 exp1 230 and nightly 63 no wifi issues at all works flawlessly now even with screen off instant reconnect i would try a fresh in stall if possible
[Samsung Galaxy Nexus] Sharpe351:
Did that long before posting. Didn't use a different kernel. Chose not to. My thought was that eos might have it already set up.

sent from my Galaxy Nexus
[Samsung Galaxy Nexus] billblack:
build 63 stock kernel. My compass is off 180 degrees. At one point I thought this was fixed (or maybe that is EOS on my Xoom)?
[Samsung Galaxy Nexus] bigrushdog:
I could swear we patched that ages ago. I'll double check. It is a Samsung issue so Xoom should be cool. In the meantime try leankernel and see if that fixes it.
[Samsung Galaxy Nexus] billblack:
Good call BRD. Lean kernel seems dead on.
[Samsung Galaxy Nexus] ajf64:
hey bigrushdog if you want may be we can see about getting lean kernel to be the official kernel of eos i think i can make that happen for you if you would be interested let me know
[Samsung Galaxy Nexus] slyd0997:
Stepped out to try a different rom for a few days but I'm back. This is my favorite.
[Samsung Galaxy Nexus] slyd0997:
google sky map

I'm not sure if this is related to the compass issue but google skymap is not useable. My son and I are both running the nightly 60 with lean kernel. He's on stable. I'm on exp180. When we use skymap, it shakes so badly you can hardly tell what the stars and planets are. I wonder if any one else has seen this. My husband is on rujellin and there are no shakes at all. This is a cool app that I don't use often but if it is rom related I hope it gets fixed.

BTW, I love this rom, I'm moving my husband to this one after 4.2 drops.
[Samsung Galaxy Nexus] ajf64:
you know lean kernel 180 can be flacky some times you ever try the 230 seems to be more stable it might fix your issue
[Samsung Galaxy Nexus] slyd0997:
But my son is on the stable lean and has the same issue. I'll see what the eos 4.2 update does.
[Samsung Galaxy Nexus] ajf64:
cant wait for 4.2 update my self hope we get it soon be great if eos was first to get it up and running on sprint nexus
[Samsung Galaxy Nexus] slyd0997:
May be not appropriate to ask a favor here but maybe somebody not running lean could try google sky map for me? I know it's a lot to ask so flame away if you must but I'm just being lazy.
[Samsung Galaxy Nexus] bigrushdog:
We're not gonna race to be first this time around. But we will race to be the best. Heck maybe we hit both. I think we will have to tread a bit more carefully this time around. I know some featuresa may create conflicts like the dual expanded statbar. We'll have to look.
[Samsung Galaxy Nexus] Anon9mouz:
Right now from what's going on with the new vendors no radio and such. So I got source synced and can't even build until these binaries are sorted out. Probably going to be some old with new

Also I see u in the miui irc a lot if u could help me can't seem to get mine booted after 4.1.2 that be great but won't cluster ur thread so hit me on a pm or talk same as xda

__________________________________________________
[Samsung Galaxy Nexus] bigrushdog:
Ok. I guess I'll sync up and see what's going on. I'm in no rush on this one lol.
[Samsung Galaxy Nexus] Anon9mouz:
I'm not either but be nice to run my first built ROM from source:p

__________________________________________________
[Samsung Galaxy Nexus] bigrushdog:
Almost done syncing. I'm doubling down on my Adderall prescription tonight so I should have a build by about 3am pst lol.
[Samsung Galaxy Nexus] MBQ_:
Just make sure your heart doesn't explode. Hahah,
[Samsung Galaxy Nexus] ajf64:
sweet i knew you guys be all over this ill be staying up to see this drop
[Samsung Galaxy Nexus] bigrushdog:
Just a preliminary observation

http://xdaforums.com/showpost.php?p=34149245&postcount=53
[Samsung Galaxy Nexus] ajf64:
:( hes trying to steal our glory
[Samsung Galaxy Nexus] mmuzzy:
I'm not racing. I'm sharing. I don't care for your attitude on a forum intended for sharing info. I appreciate that you've got the ability to get beyond the issues we've had but given that I have nothing to gain by getting beyond this it does nothing more than suck the motivation out of others to even bother with this phone. But hey, congrats again.
[Samsung Galaxy Nexus] bigrushdog:
Huh? 10char
[Samsung Galaxy Nexus] mmuzzy:
I was reacting to this post. I'm done venting but I guess you needed clarification on why. Congrats on fixing it. Well done.
[Samsung Galaxy Nexus] myepicyear:
Lol, yeah, I've upped my Dexedrine the past couple days too. ;)

I've been trying to do what you said with telephony framework since last night; I'm not great at some of this though as it is not something I'm really used to doing. I look forward to a resolution. You guys are pros!
[Samsung Galaxy Nexus] slyd0997:
I appreciate all your hard work but after seeing 4.2 on my Nexus 7, I really don't want to go there on my phone, except for the keyboard and the camera.

Edit. I'm so sorry for the above snarky post. I bet you guys will get it looking and working better than it does on my nexus 7. Good luck, this is a hard update for you. Thx for all you do.
[Samsung Galaxy Nexus] myepicyear:
Really? I'm shocked. I have 4.2 completely stock on my N7, and I absolutely love it. It makes me want to get this working on my phone so badly. I think it's a bigger upgrade than it's getting credit for. The touchscreen is finally working properly with 4.2 on the N7. That's one of the biggest things I'm pleased about. 4.1.2 was all weird for me.

Give 4.2 some more time. I think it'll grow on most people.
[Samsung Galaxy Nexus] Anon9mouz:
Hey rush if I get stuck tonight I'll shoot u a pm on this miui problem

__________________________________________________
[Samsung Galaxy Nexus] cvithlani:
Same issue with Skymap here: bad shaking on all angles.. I'm on lean with eos stable 3.0
[Samsung Galaxy Nexus] ajf64:
any news on when we might get 4.2
[Samsung Galaxy Nexus] slyd0997:
BTW skymap us an app issue. In skymap settings change the damping setting. Sorry for bringing it up..
[Samsung Galaxy Nexus] bigrushdog:
I'll drop a build in a couple days. It's been a lot of work merging the entire eos project.
[Samsung Galaxy Nexus] ajf64:
np i totally understand just excited to try out 4.2 and i cant bring my self to change roms lol
[Samsung Galaxy Nexus] gmfeny:
Where can I find the latest version of your sprint tool
[Samsung Galaxy Nexus] bigrushdog:
Get it out of my 4.2 test build. I closed the thread put its in the op. I'll update my app thread soon too.
[Samsung Galaxy Nexus] riassan:
Hey bro pm, gtalk me something. You know what I'm talking bout! :D:thumbup:;)
[Samsung Galaxy Nexus] gmfeny:
I tried it on the 4.2 are you jellin ROM and I keep getting fc. The app opens fine but fc whenever I select something. I know this isnt your ROM that I'm on but i couldn't find a thread with the app. Although I didn't look to hard.
[Samsung Galaxy Nexus] MBQ_:
EOS 4!!! :D :D :D

http://goo.im/devs/teameos/roms/eos4/nightlies/toroplus/EOS-toroplus-20121202-65.zip
[Samsung Galaxy Nexus] epicnegro:
EOS4

Trying it out now. Thanks!
[Samsung Galaxy Nexus] scriptx:
be careful before flashing EOS4. I did something I am regretting..

I flashed EOS-toroplus-20121202-65.zip and my device booted to hang at "Starting Apps". After 10+ minutes, I did a battery pull and went to recovery to restore. the /sdcard contents seem to have been moved to a directory called "0", and clockworkmod recovery cannot find any backups to restore as a result.

I booted the clean EOS3 build, and using adb, I copied the previous nandroid backup from /sdcard/0/clockworkmod/backup/ to /sdcard/clockworkmod/backup. It's restoring now, so we'll see. I think I'll have to manually move the files back though, from /sdcard/0 to /sdcard.
[Samsung Galaxy Nexus] MBQ_:
Thanks for this!! Its a known problem now, and they updated their recovery to detect the /0 stuff. :)
[Samsung Galaxy Nexus] scriptx:
Sure, glad to have helped. If there is an updated recovery, can someone please link to it?

Going back to EOS3 was fairly easy once I restored the clockworkmod directory. The only gripe was after moving /sdcard/0/* to /sdcard, all my pictures got their dates modified, so now my camera's album order is all jacked up.
[Samsung Galaxy Nexus] bigrushdog:
You guys just had to go snooping around lol. The thread will pop up in a day or 2. Also I'll build a fresh nightly shortly. The new build will have MANY bug fixes. But remember it's a WIP for sure.
[Samsung Galaxy Nexus] MBQ_:
Sounds good dude. :)
[Samsung Galaxy Nexus] bigrushdog:
Ok grab the latest build. Remember to update your recovery and grab some gapps.
[Samsung Galaxy Nexus] MBQ_:
Will using the Official GApps be okay?

Also, I'm going to do it anyway. :P
[Samsung Galaxy Nexus] ajf64:
i used the xoom ones provided int he eos4 folder it seemed to work just fine
[Samsung Galaxy Nexus] bigrushdog:
Ouch! The ones called xoom-only? Hmmm. I'd recommend whatever is the Official goo gapps. Later I may up my personal gapps that is uber pimped.
[Samsung Galaxy Nexus] ajf64:
i know i know i thought the same thing but i figured most i woud have to do is just re flash since it was fresh flash but it worked great not one issue with it so idk lol i just went with it btw is it just me or is there no kill all button any more
[Samsung Galaxy Nexus] bigrushdog:
Something like it will come back. Some features won't come back. Just how it goes.
[Samsung Galaxy Nexus] ajf64:
np was just wondering if i missed it some where thanks