Related
Hi All,
I got my first tablet today, the Acer Iconia A100. I'm no stranger to Android, and figured this would be a good stop-gap tablet until something with middlefield comes out... That being said, I have a few questions:
1) I was reading there is an ETA of "January" for an ICS upgrade, I'm guessing since this is probably one of their lower end models it might not be a top priority for them, but is there a place for me to track their status?
2) I'm located in Canada but it says that my version is EMEA_GB. Is there a way for me to change my version to the Canadian one?
3) Is there anything special I should know about using this device? I am currently pretty versed with a Moto XT860 (Droid 3 CAN version)
Thanks all!
As far as the ICS update, there hasnt been any recent news or tracking. We have been bugging them, and they give us the same gig, keep automatic update checked in settings, and they said its coming, but no date. I hope before the end of January myself.
You can check the updates that have been released, but I think they are the same as far as the regions go.
Its just a standard tablet that has a locked bootloader. We havnt been able to break it yet, and I have yet to root my device. Others have been able to, but something is preventing me from getting it done. It cant do USB hosting yet, but I expect it to be able to host when ICS comes around sometime.
mvan4310 said:
As far as the ICS update, there hasnt been any recent news or tracking. We have been bugging them, and they give us the same gig, keep automatic update checked in settings, and they said its coming, but no date. I hope before the end of January myself.
You can check the updates that have been released, but I think they are the same as far as the regions go.
Its just a standard tablet that has a locked bootloader. We havnt been able to break it yet, and I have yet to root my device. Others have been able to, but something is preventing me from getting it done. It cant do USB hosting yet, but I expect it to be able to host when ICS comes around sometime.
Click to expand...
Click to collapse
Hopefully thing will go the way what u said I dont even care Jan or Feb, just need to confirm A100 will get the ICS, thats all ^^
But for me, i dont think Acer will be update ICS for our A100
danifunker said:
2) I'm located in Canada but it says that my version is EMEA_GB. Is there a way for me to change my version to the Canadian one?
Click to expand...
Click to collapse
Where are you seeing that version information?
(BTW, EMEA stands for ''Europe, Middle East and Africa'')
If it's under Build, mine says: ''Acer_A100_2.007.04_COM_GEN1''
If it's under Flex Version, mine says: ''04_COM_GEN1''
I doubt if your ''EMEA_GB'' will affect your updates or your Market access, but you never know...
danifunker said:
Hi All,
I got my first tablet today, the Acer Iconia A100. I'm no stranger to Android, and figured this would be a good stop-gap tablet until something with middlefield comes out... That being said, I have a few questions:
1) I was reading there is an ETA of "January" for an ICS upgrade, I'm guessing since this is probably one of their lower end models it might not be a top priority for them, but is there a place for me to track their status?
2) I'm located in Canada but it says that my version is EMEA_GB. Is there a way for me to change my version to the Canadian one?
3) Is there anything special I should know about using this device? I am currently pretty versed with a Moto XT860 (Droid 3 CAN version)
Thanks all!
Click to expand...
Click to collapse
Probably already know this, but the battery goes out kind quickly, if you turn off wifi(I use a wifi toggle widget since I dont like going into the settings to turn it off), you can save a ton of battery power.
shadowskater555 said:
Probably already know this, but the battery goes out kind quickly, if you turn off wifi(I use a wifi toggle widget since I dont like going into the settings to turn it off), you can save a ton of battery power.
Click to expand...
Click to collapse
An even easier way to do this is to use the Airplane Mode toggle that is already built in to the notification bar area that pops up. I find it easier than backing out of an app that I am in to turn off WiFi.
How long are people seeing their batteries lasting. I applied the custom build.prop in development and did some tweaks of my own and I can squeeze out a day and a half ...
ntan97 said:
How long are people seeing their batteries lasting. I applied the custom build.prop in development and did some tweaks of my own and I can squeeze out a day and a half ...
Click to expand...
Click to collapse
About the same here with stock build.prop. More than adequate for my needs.
Sent from my Acer Iconia Tab A100 using Tapatalk
I am using it for a lot of hours at a time and it usually lasts me through the day. Sometimes if I'm on it too much I'll have to charge in the evening though.
Sent from my XT860 using xda premium
ive got 4 days straight standby with wifi on...mind h thats no screen on time just it sitting in deep idle.
Sent from my SGH-I897 using xda premium
Yeah... I should clarify I use it a lot too... this would be moderate to heavy usage. I'm using it all the time with customers. So in my opinion that's good... but yeah ie heard some reports of bad battery on this tab but I've seen none of it.
Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
So my turbo just updated to marshmallow, and I'm curious as to whether that opened the door to root and possibly bootloader unlock. BTW the Moto x force thread needs to be moved from this one. They're 2 different phones. I mean they're the same, but anything on Verizon is always going to be different. We all know this. Chime in guys!
blkhrt13 said:
So my turbo just updated to marshmallow, and I'm curious as to whether that opened the door to root and possibly bootloader unlock. BTW the Moto x force thread needs to be moved from this one. They're 2 different phones. I mean they're the same, but anything on Verizon is always going to be different. We all know this. Chime in guys!
Click to expand...
Click to collapse
Too soon to tell if it opened up any possible exploits, best thing is to keep an eye on this thread - http://forum.xda-developers.com/droid-turbo-2/general/root-discussionthink-tank-t3239979
The X-Force question came up before, mods said it's basically the same phone so it's not getting it's own section.
If anything, it patched a bunch of exploits and made it that much harder to root the phone. Unless Motorola does the same thing as they did with the one Moto X on Verizon, I doubt the bootloader will ever be unlocked.
Sent from my DROID Turbo 2
I feel like this could happen one of 4 ways.
1. Good ol diggin round code.
2.Motorola employee helps us.
3.someone me (I've tried) but both Motorola reps and Verizon reps are unhelpful but someone might do better. Maybe get it " escalated"
4. Just hope....
Also I just really think it's possible to get past the people who know nothing about it and find someone willing to help.. Then again maybe just simply wishful thinking.
jayman94fly said:
Also I just really think it's possible to get past the people who know nothing about it and find someone willing to help.. Then again maybe just simply wishful thinking.
Click to expand...
Click to collapse
^^^This. Whoever has had success cracking BLs on Verizon Moto devices in the past might help, or at the very least point you in the right direction. You also might be able to get some of the CM devs that have worked on VZW Moto devices in the past.
I know Verizon has been notorious about locking their phones down for a while now, but can it really be completely locked? There has to be something there that can be cracked right? Nothing is impossible right?
Hey, guys, I haven't checked in for awhile, but would someone be willing to work on it for a bounty? I mean if we could pool together somewhere between $500-$1k wouldn't it be worth it for someone who has a ton of knowledge in this comeover and help?
I'd be willing to donate to that cause even though my sig says otherwise...
Same here I second that, seems the hard part would be setting this up, I mean this is a great phone if devs would come on board
Rooted and installed twrp KINZIE today. Followed a italian tutorial for the Moto X Force. Android 6.0
http://www.androidiani.com/forum/mo...moto-x-force-ottenere-i-permessi-di-root.html
I would pay too if somebody hopped on the developer train for the X-Force !
Blubbking said:
Rooted and installed twrp KINZIE today. Followed a italian tutorial for the Moto X Force. Android 6.0
http://www.androidiani.com/forum/mo...moto-x-force-ottenere-i-permessi-di-root.html
I would pay too if somebody hopped on the developer train for the X-Force !
Click to expand...
Click to collapse
You rooted your droid turbo 2?
Digital DJ said:
You rooted your droid turbo 2?
Click to expand...
Click to collapse
No he has the moto x force it's confusing they shouldn't be posting in this thread they can root this is about obtaining a root exploit. To be honest I don't care that he rooted his phone it's not such a triumph the damn phone is unlocked.
bigv5150 said:
No he has the moto x force it's confusing they shouldn't be posting in this thread they can root this is about obtaining a root exploit. To be honest I don't care that he rooted his phone it's not such a triumph the damn phone is unlocked.
Click to expand...
Click to collapse
That's what I thought. Still not sure why the mod won't separate the threads. It gets stupid and confusing...
Digital DJ said:
Hey, guys, I haven't checked in for awhile, but would someone be willing to work on it for a bounty? I mean if we could pool together somewhere between $500-$1k wouldn't it be worth it for someone who has a ton of knowledge in this comeover and help?
I'd be willing to donate to that cause even though my sig says otherwise...
Click to expand...
Click to collapse
There is a bounty thread started in Q&A
http://forum.xda-developers.com/droid-turbo-2/help/root-droid-turbo-2-bounty-t3339484
I want to change the ugly, unintuitive material design soft buttons.
I know that verizon locks down their phones.
I want to root so that I can get back the old Holo soft buttons (ics, jelly bean, kitkat) and maybe holo blue.
I know from experience that root can make a device much more laggy.
This is my main and only phone that I can use, so I don't want to take many chances.
SecretPotatoChip said:
I know that verizon locks down their phones.
I want to root so that I can get back the old Holo soft buttons (ics, jelly bean, kitkat) and maybe holo blue.
I know from experience that root can make a device much more laggy.
This is my main and only phone that I can use, so I don't want to take many chances.
Click to expand...
Click to collapse
Who told you root makes a phone lag that is 100% false. Anyway there is no root method at this time.
I have a droid razr that I rooted in jelly bean. Since that, it's more laggy and unresponsive. Probably because of the root processes running in the background
There is no such thing as "root process". Root is just about rights to access particular part of the system, run specific commands or applications.
Digital DJ said:
You rooted your droid turbo 2?
Click to expand...
Click to collapse
He is asking for an X-force developer (since there's a lack of roms) so gonna say no.
Zeljko1234 said:
There is no such thing as "root process". Root is just about rights to access particular part of the system, run specific commands or applications.
Click to expand...
Click to collapse
Yea he just doesn't know what he's talking about here, maybe he installed something that was eating away at the CPU or RAM or both, also may have been a bad root method to
jayman94fly said:
Yea he just doesn't know what he's talking about here, maybe he installed something that was eating away at the CPU or RAM or both, also may have been a bad root method to
Click to expand...
Click to collapse
Maybe he's talking about supersu...
As many of you know the Nokia 8.1 is probably not going to get a method for a unlocked bootloader since H.M.D global shut down the exploit/way to aquire it.
I was wondering if there would be any reason that my beloved 8.1 couldn't be rooted by apps like Kingroot when they get the ability to root android PIE.
I didn't realize upon buying the phone that Nokia was so against rooting and im kinda bummed out that as of yet the phone isn't rootable yet. Might even trade it for a Pocophone and take the lack of NFC for granted
Do have mine unlocked and rooted. But the root is a messy task which will most likely take away OTA updates because any tampering is an end to the incremental OTA. Then flashing stock is a tough task too, because the awesome people at FIH Mobile forgot to disable fuse when bl is unlocked. Also, the process is kinda complicated and still under testing Given the complication, I'm sure it won't be freely available because it starts off by using paid tools to trigger debug mode.
I really didn't know that there's almost no way to root this phone when I bought it 2 months ago, but luckily the only reason I've rooted my previous phone (Mi A1) was because of Gcam which is supported out of the box on this one. So it's fine for me, but I do see that no rooting method could be an issue for some people.
Sent from my Nokia 8.1 using Tapatalk
I have already replaced the phone because of lack of root / development for this phone. Hated the stock ROM because lots of things didnt work with it (samsung gear watch, some wireless APs, car navigation, etc etc) and without the development this would never be solved.
Also I have expected better camera for the price of the phone.
WIll never buy any HMD device ever again.
nitko666 said:
I have already replaced the phone because of lack of root / development for this phone. Hated the stock ROM because lots of things didnt work with it (samsung gear watch, some wireless APs, car navigation, etc etc) and without the development this would never be solved.
Also I have expected better camera for the price of the phone.
WIll never buy any HMD device ever again.
Click to expand...
Click to collapse
Really !! this is surprise for me
I must have searched and read all forum on xda before buying this phone.
hope some body will post some steps to root it.
I read somewhere that some guys was able to root it.
hope I do not have to sell it.
looks like not much active forum for our device.
less people with this device.
light.apps said:
looks like not much active forum for our device.
less people with this device.
Click to expand...
Click to collapse
Looks like not many want to ruin their brand new phone.
Nollie8969 said:
Looks like not many want to ruin their brand new phone.
Click to expand...
Click to collapse
XDA is all about root and ROMs
Every one clever would find out first BEFORE buy Nokia phones about the impossibility of rooting those.
I'm sure when root is possible in future ( some geek will find a way, its a phone and not a high end secure government secret thing lol ) more pple will come see this thread.
Mark my words :good:
You're right. At the end of the update cycle I like to install LOS or likewise. Not for the sake for Adaway only.
Nollie8969 said:
You're right. At the end of the update cycle I like to install LOS or likewise. Not for the sake for Adaway only.
Click to expand...
Click to collapse
Agree.
Just like what we're doing at home. We're using Samsung Note 3 (Cyanogenmod rom) as online phone for local line. Before that, the phone with default OS was too lagging and cannot even install the online phone app I need.
andreoide said:
XDA is all about root and ROMs
Every one clever would find out first BEFORE buy Nokia phones about the impossibility of rooting those.
I'm sure when root is possible in future ( some geek will find a way, its a phone and not a high end secure government secret thing lol ) more pple will come see this thread.
Mark my words :good:
Click to expand...
Click to collapse
well said :good:
Motorola/Lenovo seems to be the last castle of root/development.
I was an early adopter of G7 (I bought it on initial release). As soon as BL unlock support added, BAM! rooted!
How easy it was and I am not developer
singhnsk said:
Do have mine unlocked and rooted. But the root is a messy task which will most likely take away OTA updates because any tampering is an end to the incremental OTA. Then flashing stock is a tough task too, because the awesome people at FIH Mobile forgot to disable fuse when bl is unlocked. Also, the process is kinda complicated and still under testing Given the complication, I'm sure it won't be freely available because it starts off by using paid tools to trigger debug mode.
Click to expand...
Click to collapse
Bro, can you please explain about how to root my nokia 8.1