You are right...it's awful quiet around here (and elsewhere), which is a pretty good indication that any rumored soak test hasn't begun (that is of course, if there really IS a soak test on deck...
) Just saying...DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
FoxKat's Razr/Maxx Jelly Bean Leak Classroom W/MattyP & Friends
- Thread starter FoxKat
- Start date
You are right...it's awful quiet around here (and elsewhere), which is a pretty good indication that any rumored soak test hasn't begun (that is of course, if there really IS a soak test on deck...
) Just saying...It's been a week since an exciting soak chatter.Here aren't thoughts:
Moto was NOT fully ready to deploy the Christmas release. It had minor bugs and now it's become a major deployment issue.
Moto now has to get folks back from Xmas JB to move forward. They probably can't ID Xmas users,, so now they must figure out how to deploy an update for all users.
Perhaps the soak email was to get an idea of how any folks are using different versions???
Prior Moto soas never asked so many preliminary quests as to,what's using what!
So, I believe last week's soak meal was a scouting mission to ensure that Moto is ready for some sort of release at a later time.
Think about this: How do we know if the soak email was sent to every registered user, 98%90%,80%,50%,or lower among of users?
It's a great way for Moto to assess and prepare during the next 4 weeks!
Just my opinion:biggrin:
Moto was NOT fully ready to deploy the Christmas release. It had minor bugs and now it's become a major deployment issue.
Moto now has to get folks back from Xmas JB to move forward. They probably can't ID Xmas users,, so now they must figure out how to deploy an update for all users.
Perhaps the soak email was to get an idea of how any folks are using different versions???
Prior Moto soas never asked so many preliminary quests as to,what's using what!
So, I believe last week's soak meal was a scouting mission to ensure that Moto is ready for some sort of release at a later time.
Think about this: How do we know if the soak email was sent to every registered user, 98%90%,80%,50%,or lower among of users?
It's a great way for Moto to assess and prepare during the next 4 weeks!
Just my opinion:biggrin:
REDSNK95 ,
Found this in another TOPIC, so I don't know if true or false. Just thought you may want to follow-up on this FOX FI tidbit|
"Compatibility Check
*New! FoxFi is now part of PdaNet+. PdaNet+ contains everything in FoxFi plus the capability to connect in USB mode. Use the following table to verify if your phone's Android version is supported in WiFi mode. If your phone is not supported please use Bluetooth mode or USB mode instead in PdaNet+.
*If you have one of the following models, the latest Android update has broken WiFi mode but it may still be possible to support it in future FoxFi updates: Samsung Epic Touch (Sprint), HTC Rezound (Verizon), LG Lucid (Verizon), T-mobile Galaxy SII and Samsung Proclaim.
The list below may not be complete or accurate.
Verizon
Model Supported Not-Supported Note<br />
Motorola Razr 4.0 4.1 or later Do not update to Jelly Bean<br />
Motorola Razr Maxx 4.0 4.1 or later Do not update to Jelly Bean<br />
Motorola Bionic 4.0 4.1 or later Do not update to Jelly Bean Motorola Droid X 2.3 Motorola Droid X2 2.3 Motorola Droid 2 Global 2.3<br />
Motorola Droid 4 4.0 4.1 or above Do not update to Jelly Bean Motorola Droid 3 2.3 Motorola Droid 2 2.3 Motorola Droid Pro 2.3<br />
Motorola Droid 1 not supported<br />
Motorola Razr M 4.0 4.1 or above Do not update to Jelly Bean<br />
Motorola Razr Maxx HD 4.0 4.1 or above Do not update to Jelly Bean Samsung Charge 2.3<br />
Samsung Galaxy S III 4.0 4.1 or later Do not update to Jelly Bean<br />
Samsung Galaxy Nexus 4.1 4.2 Do not update to Jelly Bean Samsung Fascinate 2.3 Samsung Stratosphere 2.3 Samsung Continuum 2.2 Samsung Illusion 2.3<br
HTC ThunderBolt not supported<br />
HTC Incredible 2 not supported<br />
HTC Rezound not supported<br />
HTC Incredible not supported HTC Incredible 4G LTE 4.0 LG Vortex 2.2 LG Ally 2.2 LG Spectrum 2.3 4.0 (?) LG Lucid 2.3 4.0 (?)<br />
LG Revolution not supported<br />
LG Enlighten not supported."
Sent using Tapatalk
My guess is that there are a few million Razrs in use. The number of users who even know what a soak test is, likely thousands. So I think your percentage is way high.
I'm pretty sure they have a way to know what build you are on. How would the "check for updates" work otherwise?
I doubt anyone on the Christmas update will be reverted backwards. It's more likely they will push 2 versions.
Worst case, if you have the Christmas JB and get the wrong update it will fail. This would cause lots of calls to tech support.
Those of us who use these forums are a fraction of the total users of the devices.
If there is a delay in starting the soak test it's just that, which I'm guessing would be nothing new.
My opinion.
Sent from my DROID RAZR using Tapatalk 2
Just in case someone was actually interested I'll update. I did FDR just for fun. superuser (i would assume SuperSU also but since i dont have it can't say for sure) and safestrap (and I'm pretty sure bootstrap as i did have it originally and pretty sure it didn't get removed) were not removed with an FDR. I did have to go back and reupdate superuser before it rerooted me but after that all was fine. Reloaded titanium backup and reinstalled my saved system/apps data and all was good to go. I didn't temp unroot with voodoo or anything just left it as it was and FDR from the recovery menu.
I was able to remove SS 3.07 through the app itself and my phone no longer boots into SS. I plan to Temp unroot with voodoo once an update comes through.
Well I took the plunge last night, reverted back to .211, upgraded to job and the process couldnt have been anymore flawless. Had a couple of worries here and there due to some hangs in the reverting process but other than that I couldn't be happier. I do have a couple of questions though. When I drag widgets to my home screen after going through the process to get the circles widget it always brings up another window kind of like the one where it asks which program I want to run a file or open a link with. Is this normal or is it a back from the ported apps and home screen apk? Also, is there anyway to turn off this darn haptic feedback while inputting text or is that baked into jb? I turned off the vibrate on touch option but it's vibrating while I text. Also, while reverting back to stock I opted to do the FDR at the end, do I have to do it again or am I safe as far as a clean install goes and good to proceed with training my battery meter? Thanks in advance, and thanks to matty , foxkat and the rest for putting together this detailed thread. As well as the ones who helped save the thread. I was almost heart broken when I couldn't open the link to this thread from the previous class. Lol
Settings--language&inputs. In there is a setting (circular gear looking symbol) for the keyboard you are using..foe the vibration will texting.
One FDR should be fine..but its based off of your preference..some do two and some just do one.
Not familiar with the circle widget.. so can't answer that question.. maybe when official JB rolls I'll have the same question.. Lol.
Much appreciated!! I would have waited for the official version to roll out at well, but i was just so tired of looking at ICS and would have had to revert back anyway. Had the extra time on my hands so i figured, why not?
drivinfocused
Member
he may have wanted to go to the Leaked JB and root.
On the battery side..i havnt noticed a big difference in the battery life. (also no FDR before or after)
On the battery side..i havnt noticed a big difference in the battery life. (also no FDR before or after)
Hi
It's normal, I get it too, it's having you make the selection again through the HD launcher. If that makes sense. Check Ur settings for the keyboard. I'm not using stock keyboard so I'm unsure, maybe an option in Ur text app, if Ur not using stock one??
Sent from my DROID RAZR MAXX using Tapatalk2
Well I took the plunge last night, reverted back to .211, upgraded to job and the process couldnt have been anymore flawless. Had a couple of worries here and there due to some hangs in the reverting process but other than that I couldn't be happier. I do have a couple of questions though. When I drag widgets to my home screen after going through the process to get the circles widget it always brings up another window kind of like the one where it asks which program I want to run a file or open a link with. Is this normal or is it a back from the ported apps and home screen apk? Also, is there anyway to turn off this darn haptic feedback while inputting text or is that baked into jb? I turned off the vibrate on touch option but it's vibrating while I text. Also, while reverting back to stock I opted to do the FDR at the end, do I have to do it again or am I safe as far as a clean install goes and good to proceed with training my battery meter? Thanks in advance, and thanks to matty , foxkat and the rest for putting together this detailed thread. As well as the ones who helped save the thread. I was almost heart broken when I couldn't open the link to this thread from the previous class. Lol
It's normal, I get it too, it's having you make the selection again through the HD launcher. If that makes sense. Check Ur settings for the keyboard. I'm not using stock keyboard so I'm unsure, maybe an option in Ur text app, if Ur not using stock one??
Sent from my DROID RAZR MAXX using Tapatalk2
Makes perfect sense actually, i figured it was either a bug or part of the HD Home screen. Thanks for confirming that, i'm glad i am not the only one. What's the difference between the different keyboards anyway?
Preference, more options. Example: skins, adjusting key sizes, etc.
Sent from my DROID RAZR MAXX using Tapatalk2