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

[Verizon] [rom]jbsourcery v5.4-lte[06/07/13] jb4.2.2 The Final Call

Check the file sharing on the laptop, try making sure it is set as if you are on a public connection. I seem to remember reading that somewhere before.
 
That could be the problem. I also tried (for fun) using the wife's Bionic and FoxFi. App setup fine but got the same error. It may not want to connect to Adhoc connections.
 
One more thing, what do you have the connection labeled as and what color is it? Some people have said they had to rename the Network SSID and then the name changed colors from red and worked.
 
I haven't seen anyone else with an issue with waking the phone up with either power or volume rocker. It reminds me of my book colors sleep of death. I was on 4.0 and just updated to 4.1(cache wipe only) right before this post. Hopefully something had changed to fix this. If I were to get a logcat with alogcat, what settings would I need to use?
 
AndroidKris said:
I haven't seen anyone else with an issue with waking the phone up with either power or volume rocker. It reminds me of my book colors sleep of death. I was on 4.0 and just updated to 4.1(cache wipe only) right before this post. Hopefully something had changed to fix this. If I were to get a logcat with alogcat, what settings would I need to use?
Click to expand...
hmm..not had that issue myself....
 
Gonna do a re-wipe tonight I think, since I found myself with an interesting one. Not entirely sure how it happened, but I had went to install the addon.zip and the camera bitrate increase one. Seemed to install fine, but as soon as the phone restarted, realized that now I cannot access the JB Control Center. It just black screens. I get the shell message at the bottom, and it just sits there. Messages comes up about once a minute, and just repeats that, no matter what I do, until I restart the phone. Unfortunately, I have no idea how to possibly correct that, other than just wipe and start over (I only had put a few apps back on, and hadn't made any big enough changes that I needed to make a backup for yet).

Weird. gonna get it back up and set, and then see if I can replicate it.

EDIT: Hmm...seems to have affected anything requiring root. TiBu is doing the same thing, sitting at "asking for root rights" and every 30 seconds or so, flashing the permission message again, and loops that way. So...that's a bummer. Looks like I'll lose some info along the way. ugh. Well, whatever...
 
CharlzO said:
Gonna do a re-wipe tonight I think, since I found myself with an interesting one. Not entirely sure how it happened, but I had went to install the addon.zip and the camera bitrate increase one. Seemed to install fine, but as soon as the phone restarted, realized that now I cannot access the JB Control Center. It just black screens. I get the shell message at the bottom, and it just sits there. Messages comes up about once a minute, and just repeats that, no matter what I do, until I restart the phone. Unfortunately, I have no idea how to possibly correct that, other than just wipe and start over (I only had put a few apps back on, and hadn't made any big enough changes that I needed to make a backup for yet).

Weird. gonna get it back up and set, and then see if I can replicate it.

EDIT: Hmm...seems to have affected anything requiring root. TiBu is doing the same thing, sitting at "asking for root rights" and every 30 seconds or so, flashing the permission message again, and loops that way. So...that's a bummer. Looks like I'll lose some info along the way. ugh. Well, whatever...
Click to expand...

Try "Fix Permissions", sounds like a permissions issue to me.
 
CharlzO said:
Gonna do a re-wipe tonight I think, since I found myself with an interesting one. Not entirely sure how it happened, but I had went to install the addon.zip and the camera bitrate increase one. Seemed to install fine, but as soon as the phone restarted, realized that now I cannot access the JB Control Center. It just black screens. I get the shell message at the bottom, and it just sits there. Messages comes up about once a minute, and just repeats that, no matter what I do, until I restart the phone. Unfortunately, I have no idea how to possibly correct that, other than just wipe and start over (I only had put a few apps back on, and hadn't made any big enough changes that I needed to make a backup for yet).

Weird. gonna get it back up and set, and then see if I can replicate it.

EDIT: Hmm...seems to have affected anything requiring root. TiBu is doing the same thing, sitting at "asking for root rights" and every 30 seconds or so, flashing the permission message again, and loops that way. So...that's a bummer. Looks like I'll lose some info along the way. ugh. Well, whatever...
Click to expand...
dirty flash rom/gapps/// sounding like you have lost root access, possibly.. very odd.. this should correct it though
 
tdevaughn said:
dirty flash rom/gapps/// sounding like you have lost root access, possibly.. very odd.. this should correct it though
Click to expand...

It might have, but I took it as the prime chance to go to JBS 4.1 instead :) BT issue seems to be a range thing, so now I can at least remember to turn off the speakerphone before I leave the car. Only other random thing I had happen, was after the BT hung on Turning off, I restarted the phone, and the wallpaper I had set (one of the Sourcery ones), shifted. Normally static in the placement, it seemed almost like it had scrolled a page. Just reset the wallpaper and was fine. No biggy, and likely a random one-off.

Toyed with the 2nd user, but didn't feel like making up a guess Google Account while on the road driving, but still, I can see where it might come in handy.

Again, loving the work! Loving my new phone again :)

Can't wait to see what you guys have planned next!
 
Thanks Team Sourcery and Happy Holidays to you all as well! May our New Year be filled with Google/Moto X phones, unlocked bootloaders and Key Lime Pie Sourcery :D


Sent from my Galaxy Nexus using SwiftKey Flow
 
I hate to beat a dead horse, but I'm still having proximity sensor issues! After a random number of calls, the screen goes blank when I make a call and will not come back until I push the power button to end the call (I have it set so the power button ends the call because I had no other way of hanging up), and then press it two more times to get back to the lockscreen. The only thing that resets the sensor is a reboot with a battery pull. The problem repeats itself after a few calls, so it's really becoming annoying!

I don't think the sensor is defective, and I don't have one of those GNexes that was built August-September 2012. I've recently tried using prop modder to change the proximity sensor delay to zero, but I'm not sure that setting is going to hold.

This started to become a recurring problem when I installed 3.1 wth the updated gaaps on your site. The previous release I had (2.3.5) I used the gaaps released 07-26-2012, and that was the last time the proximty sensor worked without fail.

Is there any way to use an older stock dialer on Jelly Bean 4.2.1 than the one in the standard gaaps file on your site? I tried to find one on the web, but don't have the tech saavy to get the right one. I'd like the one that had a white backround. That's the last one I had where the proximity sensor worked correctly.

Hope I'm not being annoying, but I really love your ROM and don't want to have to go to another one because of this. PLEASE HELP!
 
tdevaughn said:
I always say, try a lot of different roms.. find what works best for you and the way you use your phone. Sourcery is my fave, but there are many great roms out there!
Click to expand...

Well it has to be. You are their PR guy. Wouldn't be right it you were running aokp or something. :rolleyes:
 
joesixpack said:
I hate to beat a dead horse, but I'm still having proximity sensor issues! After a random number of calls, the screen goes blank when I make a call and will not come back until I push the power button to end the call (I have it set so the power button ends the call because I had no other way of hanging up), and then press it two more times to get back to the lockscreen. The only thing that resets the sensor is a reboot with a battery pull. The problem repeats itself after a few calls, so it's really becoming annoying!

I don't think the sensor is defective, and I don't have one of those GNexes that was built August-September 2012. I've recently tried using prop modder to change the proximity sensor delay to zero, but I'm not sure that setting is going to hold.

This started to become a recurring problem when I installed 3.1 wth the updated gaaps on your site. The previous release I had (2.3.5) I used the gaaps released 07-26-2012, and that was the last time the proximty sensor worked without fail.

Is there any way to use an older stock dialer on Jelly Bean 4.2.1 than the one in the standard gaaps file on your site? I tried to find one on the web, but don't have the tech saavy to get the right one. I'd like the one that had a white backround. That's the last one I had where the proximity sensor worked correctly.

Hope I'm not being annoying, but I really love your ROM and don't want to have to go to another one because of this. PLEASE HELP!
Click to expand...

If you put in another dialer, you will lose the custom portions of the dialer that we have baked in...
 
I have just started noticing the sensor issues as well. I had the issue after I bought my phone in December of 2011 and it went away at some point around the spring I guess. But it has just reared it's ugly head. For me, it is most annoying when I need to use the dialpad or perform other tasks with the phone during a call. As soon as my finger touches the screen, the display turns off. It's like the sensor is set too sensitive.
 
Quick question that hopefully someone has a quick answer to...I've recently purchased movies from the Google Play store. Is there anyway to get them working on a custom rom? When I use the Play Movies & TV app it says something about a licensing server. I assumed because I'm rooted and on a custom rom. Any work around?
 
Movies from the playstore should work on our 4.1 release. We have a mod in the mods section to enable DRM for apps like HULU to work, at the expense of playstore movies.
 
You must log in or register to reply here.
Back
Top Bottom