• 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

tdevaughn said:
Sounds like you also formatted data in twrp. That option wipes everything from the phone.... Your only recourse is to use adb to push a rom/gapps to your phone
Click to expand...

Well, crap :mad:

I thought to erase the sdcard you had to manually select it. I don't understand how that happened.

I will dig around and see if I can find Scary Aliens instructions on how to push those to my phone...unless someone has the links handy.
 
darkcyber said:
Well, crap :mad:

I thought to erase the sdcard you had to manually select it. I understand how that happened.

I will dig around and see if I can find Scary Aliens instructions on how to push those to my phone...unless someone has the links handy.
Click to expand...

Sorry man...not what I meant by wiping data (wipe data and factory reset are the same things and I listed both...my apologies for not being clear enough!) :o. I do not like how TWRP has them listed in the same "wipe" directory.

Put the ROM files in your sdk tools folder.

From your default directory (should be something like C:/android-sdk/tools):

adb push <path to file on phone> <path to location on device>
For example: adb push file.zip /sdcard/file.zip
 
UBRocked said:
Sorry man...not what I meant by wiping data (wipe data and factory reset are the same things and I listed both...my apologies for not being clear enough!) :o. I do not like how TWRP has them listed in the same "wipe" directory.

Put the ROM files in your sdk tools folder.

From your default directory (should be something like C:/android-sdk/tools):

adb push <path to file on phone> <path to location on device>
For example: adb push file.zip /sdcard/file.zip
Click to expand...

Not your fault. I thought I missed something in the wipe as well because evverything came up when I rebooted after install the new rom. Been a thousand years since I've used sdk tools...fun...fun.
 
OK, a little help here. I have connected in fastboot mode to the computer and run "fastboot devices" and it sees my phone. But when I run adb devices it lists nothing...so I cannot push anything to it. Am I missing something?
 
jhawkkw said:
I believe you have to be in recovery in order to use adb.
Click to expand...

True story :D

I had to do an ADB "pull" to recover pictures off of my Nexus when it wouldn't boot after getting wet. I tried everything and could not get CWM recovery to recognize ADB commands but TWRP did. That was the beginning of the end for CMW on my Nexus.
 
Preliminary results of my battery testing...

I usually test my battery life by monitoring standby usage with my typical apps syncing in the background. I usually give the phone a few days to settle in and in this case, it has only been a day on the official 4.4 (but was running the experimental before that). These results really only mean something to me because you most likely do not have the same things running in the background but here goes:

12:15 PM - 100%
1:00 PM - 92%

Note: I was using my phone during this period. I took 7 pictures which then synced to my Google+ and Dropbox accounts. From 1:00 PM til now, I have not used my phone other than to check the battery.

2:00 PM - 91%
3:18 PM - 88%
4:11 PM - 86%
5:53 PM - 82%

So I am seeing about 2% drain per hour right now for standby usage. 3% is what I consider to be "normal" so anything more than that is bad...anything less than that is good. Was running between 3%-4% on 4.2 Jelly Belly builds.

I will continue to watch it...but 2% per hour is good to see!

Edit: Running stock kernel @ 1,200 MHz Max / 350 MHz Min with interactive governor.
 
Under the topic of camera sounds...I don't know why it's any different that we can manually turn the media volume down and make it go away..I'm not saying anyone's at fault, but really, why would the staties make a big argument over state laws, but still allow us to turn down the camera sounds another way anyway...just let us have our check box, States! lol. And I'm not saying they might not have good reasons or anything, because I know there ARE good reasons. It's like the NYC law against super-sized drinks - but still can refill regular sized cups all day long.

I haven't had a chance to play with the battery stats on mine, JUST wiped stats this morning and am charging back up now, to try to get a start on it. Good to see that you're having a good experience though, and I am sure most will too!

After wayyyyy too much thought on my part, I finally solved my lockscreen questions...while having the Chronus on the screen DOES work, then I had the extra press, to then get to unlock my phone. I was going for simple as could be. So I downloaded Widget Locker (which I haven't used since my Thunderbolt), and that worked fine, other than the default lockscreen clock widget on it wouldn't show me my battery percentage on the lockscreen. So then I got thinking ok, I'll put Chronus on Widget Locker. Which worked. But there was something nagging at the back of my head...and finally it hit me... Why was I bothering with all this tinkering, when I had One More Clock Free sitting there on my homescreen anyway... so I just added that to my lockscreen, and voila! I love simple answers! Now I have my weather, my battery display, all my goodies! Not that I don't like Chronus, don't get me wrong. But I liked having it set so I didn't need WL to run (not that it takes much), and still a simple, one-step unlock process.

AND, anyone notice much difference on 4.4 release versus experimental? So far, my experimental has been rock solid....minus the BT issue still seems to be there for me. Only pops up if I leave my speaker turned on, and walk out of range, and then come back into range with my phone. For some reason, that's when it locks and won't reconnect or turn off until I reboot the phone. And that's freshly paired, too. I just try to remember to manually turn off BT when I get out of the car. Probably will be solved as well when I change my stereo to one with BT built in, which will automatically power off when I get out of the car instead of me forgetting to do so.

Still lovin it!
 
jhawkkw said:
I believe you have to be in recovery in order to use adb.
Click to expand...

When you say I have to be in recovery, do you mean boot up the phone by holding down both volume keys and then the power button and then once it comes up just select "recovery mode"? If not, then do explain please. Been dealing with this off and on all day and the wife is going to kill me if I spend any more time on it :D
 
I hear you on that. I use Beautiful Widgets on my home screen and lock screen. Creates a seamless look. I'm not a fan of the full sized widgets to start...just takes an extra second for the lock screen to initialize.

And no, I haven't noticed any difference between the experimental and release version. Both have been running very well.

I did have a reboot this morning but I booted into recovery and wiped cache, dalvik cache, and fixed permissions. First reboot I've had since any version of 4.4.
 
darkcyber said:
When you say I have to be in recovery, do you mean boot up the phone by holding down both volume keys and then the power button and then once it comes up just select &quot;recovery mode&quot;? If not, then do explain please. Been dealing with this off and on all day and the wife is going to kill me if I spend any more time on it :D
Click to expand...


You're using TWRP right? Just boot into that and then connect your phone to the computer via the USB cable. If you want to test if your ADB connection is working, just type:

adb reboot

That should reboot your phone. If it doesn't, you need to reconfigure ADB.
 
may add kicked in... stopped reading after under the topic :)

the release has a feature where you can add shortcuts to the lockscreen....more tweaks and speed :)
 
tdevaughn said:
may add kicked in... stopped reading after under the topic :)

the release has a feature where you can add shortcuts to the lockscreen....more tweaks and speed :)
Click to expand...

I'll probably go full release sometime this week, no reason not to :) So nice to have such stable platforms throughout!
 
UBRocked said:
You're using TWRP right? Just boot into that and then connect your phone to the computer via the USB cable. If you want to test if your ADB connection is working, just type:

adb reboot

That should reboot your phone. If it doesn't, you need to reconfigure ADB.
Click to expand...

I finally got it working. Problem is I was using sdk-tools from my D:, which fastboot works fine from there, but for some reason adb will not. So, I switched to the C:\android-sdk-windows\platform-tools and adb works from there. In the process of copying the stuff over now and it is copying.

Thanks for all the help everyone! :smokingsomb:
 
Please add the camera sound option back in. Those in states that outlaw it can just leave it checked :)

I'll flash this when I get a moment later. Maybe it's time for a full wipe.
 
jackburnt said:
Please add the camera sound option back in. Those in states that outlaw it can just leave it checked :)

I'll flash this when I get a moment later. Maybe it's time for a full wipe.
Click to expand...

I do believe that it is an option baked into 4.2 AOSP. I'm pretty sure Jelly Belly 4.2 ROMs still had it as an option but I'm not entirely sure.

But I did just check and when the phone is on silent or vibrate, the shutter sound is off. Should be a solution for those who...who don't want to scare the birds away??? :p
 
OK, guys and gals! Just installed 4.4 last night (good job BTW JBS crew!) and decided to try the old photo transfer thing with the wife's Galaxy S3. I have both phones NFC turned on, her phone has S-Beam turned on (it's upgraded to latest Verizon OTA Jelly Bean), and my phone has Android Beam turned on. I was able to beam a photo through Gallery to her S3 with no problems. Hooray, I thought! I can finally impress her with this. Tried beaming a pic from her phone to mine and - what the $%#@! - Google Play Store opens up and tries to receive it with no success!

The faint ripping sound you may have just heard was the last of my hair being torn out! Like many have said, "They make this look so easy on TV".

Any thoughts on why this is happening (the Play Store thing - I know about Samsung's effort to steal Android Beam for themselves)? Is there another app I can use instead of Gallery that may make this work? Am I beating this to death? HELP!

(serenety now, serenety now, serenety now...)
 
joesixpack said:
OK, guys and gals! Just installed 4.4 last night (good job BTW JBS crew!) and decided to try the old photo transfer thing with the wife's Galaxy S3. I have both phones NFC turned on, her phone has S-Beam turned on (it's upgraded to latest Verizon OTA Jelly Bean), and my phone has Android Beam turned on. I was able to beam a photo through Gallery to her S3 with no problems. Hooray, I thought! I can finally impress her with this. Tried beaming a pic from her phone to mine and - what the $%#@! - Google Play Store opens up and tries to receive it with no success!

The faint ripping sound you may have just heard was the last of my hair being torn out! Like many have said, "They make this look so easy on TV".

Any thoughts on why this is happening (the Play Store thing - I know about Samsung's effort to steal Android Beam for themselves)? Is there another app I can use instead of Gallery that may make this work? Am I beating this to death? HELP!

(serenety now, serenety now, serenety now...)
Click to expand...

Having the same issue as you. A coworker in my office has an S3. NFC and S-Beam / Android Beam was all turned on. When I tried to send a picture from my Nexus to her S3, it tried...but kept failing saying "beam did not complete" in the notifications. When I tried sending a picture from the S3 to the Nexus, it sent me to the play store and then said "item not found".

Hmmm...
 
You must log in or register to reply here.
Back
Top Bottom