Related
How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
robuser007 said:
How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)
Click to expand...
Click to collapse
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?
gmanfuzing said:
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?
Click to expand...
Click to collapse
Becuase I found one on ebay for $45.
babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
If they're looking for testers I'm game. I'm no stranger to all that stuff coming from Vogue.
mrkite38 said:
Becuase I found one on ebay for $45.
Click to expand...
Click to collapse
hmm 45 dollars isn't bad then. Still i wish the tilt 2 was out when i got mine. its what the phone should've been like in the first place seeing as the processor isn't even better.
All nonsense aside, whats the status of nand support?
the0ne.john said:
All nonsense aside, whats the status of nand support?
Click to expand...
Click to collapse
See post #2.
babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
Agreed - the only things I 'expect' to work reliably before flashing to nand are calls and data. Everything after that is gravy.
And bt audio works on cupcake and donut for vogue, but not on eclair. And the vogue's camera is just crap, regardless of os.
arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
I agree. I've been a full time Android user for the last two and a half months . No complaints here.
any news?¿ will be an android rom some day? or we shouldn´t expect that
There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?
volcan123 said:
There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?
Click to expand...
Click to collapse
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861
we can learn from Vogue,it has opened source. http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
Guys, believe me, WHEN the team wants to make it a ROM for NAND they will do it easily.
So just wait.
up！
I agree. I've been a full time Android user
hope the ROM for NAND，flash it
rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
Click to expand...
Click to collapse
Yup, thats what I am talking about. I wonder if the chefs for XDANDROID know about this?
rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861
Click to expand...
Click to collapse
These threads are about how USERS can put an NAND build on their phone..
Okay I'm going to tell you guys this just once.
First the developers have to get everything finished so that we don't need the few bits from WinMo we still do.
Then they can make a NAND build.
And BELIEVE me, they know how to do it. It just won't work at the current state of things.
And the XDAndroid team knows just as much about porting as the Vogue guys. The only difference is that we got more advanced phones and therefor it takes a LOT more time to make a port.
x2 right now the biggest thing is drivers. since there were never any drivers made for the touch pro/fuze for android, none exist.
since none exist, we must use winmo to initalize alot of the hardware that android uses.
once the drivers are sorted out (they are being worked on) and we don't need winmo to initalize everything for android, android can be moved to nand.
I DID IT!!!!!
I sat down for a few hours and tweaked CM7 to run on the C. EVERYTHING runs so far. You need to make no changes, just flash it.
If you have a recovery menu you know how to do it. Menu will be out very soon too.
Uploading now
port of someone elses dirty port
Still has traces of metroPCS i will clean up
http://tomp90xjourney.blogspot.com/
download it there
Congrats! See if you can get the XDA folks to give you your own section. It should bring more attention to the port.
cricket is a good carrier
r0bot said:
Congrats! See if you can get the XDA folks to give you your own section. It should bring more attention to the port.
Click to expand...
Click to collapse
Yeah? How would I go about getting it that kind of attention?
And thank you
rebel101150 said:
Yeah? How would I go about getting it that kind of attention?
And thank you
Click to expand...
Click to collapse
Keep programming, maybe post some pictures and what not and they would probably add an optimus c section i bet.
You are a Godsend. My buddy has an Optimus C. I found instructions for rooting, but was having a hard time scaring up ROMS. Any chance of some screen shots? Does this have an OC kernel?
ST3ALTHPSYCH0 said:
You are a Godsend. My buddy has an Optimus C. I found instructions for rooting, but was having a hard time scaring up ROMS. Any chance of some screen shots? Does this have an OC kernel?
Click to expand...
Click to collapse
No unfortunately it doesn't. Screenshots i'm working on (it saves them all in PNG which the site won't recognize).
An overclock kernel is being worked on, the base of this is the standard kernel. We do have one working but it's not ready for release yet.
So they will be up soon.
make sure he has the custom recovery menu. It won't flash properly without it. We worked a few days on that as well.
rebel101150 said:
No unfortunately it doesn't. Screenshots i'm working on (it saves them all in PNG which the site won't recognize).
An overclock kernel is being worked on, the base of this is the standard kernel. We do have one working but it's not ready for release yet.
So they will be up soon.
make sure he has the custom recovery menu. It won't flash properly without it. We worked a few days on that as well.
Click to expand...
Click to collapse
If you're using Shoot Me, you can set the prefs to save as jpg.
By custom recovery, do you mean the one in the stickied post or CWM?
Biggest thing is the speed of the default device, I'll keep an eye here and get serious when the OC kernel is ready.... I think I'll need a pretty compelling argument to get him to root. Thank you for all your hard work in this area.
ST3ALTHPSYCH0 said:
If you're using Shoot Me, you can set the prefs to save as jpg.
By custom recovery, do you mean the one in the stickied post or CWM?
Biggest thing is the speed of the default device, I'll keep an eye here and get serious when the OC kernel is ready.... I think I'll need a pretty compelling argument to get him to root. Thank you for all your hard work in this area.
Click to expand...
Click to collapse
http://tomp90xjourney.blogspot.com/
Just use that to download it
Just curious since I didn't see any screenshots (he hasn't given me the nod yet, either) What kind of overclocks have you gotten and how is your battery life?
EDIT: Nevermind, I just saw it on the blog (read past it at first). 850 MHz? That's almost a 50% OC! The battery life at that speed question still remains. Also, don't see the FAQ link, or is it not up yet? Thanks a bundle. I've gotten fairly proficient with things on my Inspire, but the Optimus looks to be a slightly different monster.
mattrb said:
cricket is a good carrier
Click to expand...
Click to collapse
I agree, except that it costs more money then VM. The Optimus V also has more support by devs.
IM kinda scared of rooting my phone
Ventus_zx said:
IM kinda scared of rooting my phone
Click to expand...
Click to collapse
I'm kinda scared of jellyfish. How are you supposed to avoid them when you can't even see them??
has anybody asked the dev of safestrap, or even tried it out yet? the locked bootloader is the next big problem, i assume. and as far as i get it the "fire os" is the same on "fire"-devices.
forum.xda-developers.com/showthread.php?t=2556677
meningitiscerebrospinalis said:
has anybody asked the dev of safestrap, or even tried it out yet? the locked bootloader is the next big problem, i assume. and as far as i get it the "fire os" is the same on "fire"-devices.
forum.xda-developers.com/showthread.php?t=2556677
Click to expand...
Click to collapse
JCASE demonstrated booting unsigned code from USB... so we dont NEED to unlock the bootloader although it would be nice.
What we really need is a custom recovery and a way to boot it.. perhaps JCASE will chime in now that the root is out..
last i saw his signature says he is away for an undetermined amount of time :crying:
wavrunrx said:
last i saw his signature says he is away for an undetermined amount of time :crying:
Click to expand...
Click to collapse
lol his sig has said that for an undetermined amount of time
May be we can write custom recovery using dd an then boot it?
I would think anyone that is willing to test unknown methods either has money to burn or a hardware flasher.
Just checked safestrap, no luck.
May be we can port loki. Platform looks similar for me, but offsets is different.
Sent from my LG-D802 using XDA Free mobile app
iRet said:
Just checked safestrap, no luck.
May be we can port loki. Platform looks similar for me, but offsets is different.
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
Looks like a few people have been looking into this, but haven't seen much activity recently. Just chiming in to see if there have been any advances on this front? Either progress, or a determination that it's too difficult at this point?
drumst1x said:
Looks like a few people have been looking into this, but haven't seen much activity recently. Just chiming in to see if there have been any advances on this front? Either progress, or a determination that it's too difficult at this point?
Click to expand...
Click to collapse
So I was thinking about 2nd-init and getting SafeStrap working. I need to keep looking and figure out the best place to start the 2nd-init.
rbox said:
So I was thinking about 2nd-init and getting SafeStrap working. I need to keep looking and figure out the best place to start the 2nd-init.
Click to expand...
Click to collapse
Thanks for answering Happy to hear that people are still trying this. I'm wondering, once Android TV is released, the hardware on this device seems to be pretty powerful and it might be a great experience, if we can figure out how to get it on there.
Good luck, rbox! And thx for the xposed mods
Just be aware that the first thing that will stop working with an unlocked bootloader will be Netflix HD. I don't have Prime so can't comment on that.
You will be limited to 720x480 resolution - 1750kbps.
drumst1x said:
Thanks for answering Happy to hear that people are still trying this. I'm wondering, once Android TV is released, the hardware on this device seems to be pretty powerful and it might be a great experience, if we can figure out how to get it on there.
Good luck, rbox! And thx for the xposed mods
Click to expand...
Click to collapse
I was able to find the best spot to do the 2nd init, and it seemed to be working, but unfortunately I'm having some problems getting TWRP to actually display even though I'm doing exactly the same thing I did with clockwork. Luckily it's a long weekend, so I should have some time to debug it.
rbox said:
I was able to find the best spot to do the 2nd init, and it seemed to be working, but unfortunately I'm having some problems getting TWRP to actually display even though I'm doing exactly the same thing I did with clockwork. Luckily it's a long weekend, so I should have some time to debug it.
Click to expand...
Click to collapse
thank you for the work u put into this device. i got it a few days back and have it decked out i hope by the end of summer this device will have a working recovery and maybe a rom or 2
CLran619 said:
thank you for the work u put into this device. i got it a few days back and have it decked out i hope by the end of summer this device will have a working recovery and maybe a rom or 2
Click to expand...
Click to collapse
Summer only has a couple of weeks left... I also hope we can crack the bootloafer or at least get boot strap or something similar working, but I am not going to hold my breath. I AM very happy with how well it is working though, especially as an xbmc/kodi box! Hope we can get the mic button working in kodi.
The lollipop roms are great but it'll be fantastic if there is a marshmallow ROM for the E980.
Anybody knows if there's any?
Well, if you make it, there will be. There is a long discussion about marshmallow on this device, and all ended with "it needs too much work".
ShadySquirrel said:
Well, if you make it, there will be. There is a long discussion about marshmallow on this device, and all ended with "it needs too much work".
Click to expand...
Click to collapse
Lolol well said. My device is just sitting in a box now and I occasionally use it as a universal remote as it is running the stock OS. I now have a nexus 6 and an Amazon Fire 7 (5th gen) that I use as my daily devices. I honestly haven't touched my G Pro in months now.
rjmxtech said:
Lolol well said. My device is just sitting in a box now and I occasionally use it as a universal remote as it is running the stock OS. I now have a nexus 6 and an Amazon Fire 7 (5th gen) that I use as my daily devices. I honestly haven't touched my G Pro in months now.
Click to expand...
Click to collapse
I got mine back today after family member brought it to repair center to get damn USB fixed... and guess what? repair center just made it worse They replaced only USB connector and messed up flat cables connecting that board to mainboard... So it's sitting on my desk now, charging slowly, waiting for me to order parts to finally repair it. It still looks great and feels great, but I miss fingerprint scanner now, lol.
ShadySquirrel said:
I got mine back today after family member brought it to repair center to get damn USB fixed... and guess what? repair center just made it worse They replaced only USB connector and messed up flat cables connecting that board to mainboard... So it's sitting on my desk now, charging slowly, waiting for me to order parts to finally repair it. It still looks great and feels great, but I miss fingerprint scanner now, lol.
Click to expand...
Click to collapse
Lol that sucks. Hopefully you fix it. I tried to get my e980 unlocked by AT&T, but they led me on a wild goose chase and I never ended up getting it to happen.
rjmxtech said:
Lol that sucks. Hopefully you fix it. I tried to get my e980 unlocked by AT&T, but they led me on a wild goose chase and I never ended up getting it to happen.
Click to expand...
Click to collapse
That's kind of ass-holish from them, TBH... our providers give you code after your contract for that device is over (usually after 2 years) after you request it. But still, had similar thing happening with work phone (provider didn't want to unlock it after contract, and later required 80€ fee) but just brought it to your neighbourhood mobile shop(tm) and guy cracked that lock with a box in like 5 minutes, for 1/10th of price provider requested.
I'm repairing this one, that board is 4$, and need to find a good battery and voila, great secondary phone, not some crappy Lenovo.
ShadySquirrel said:
That's kind of ass-holish from them, TBH... our providers give you code after your contract for that device is over (usually after 2 years) after you request it. But still, had similar thing happening with work phone (provider didn't want to unlock it after contract, and later required 80€ fee) but just brought it to your neighbourhood mobile shop(tm) and guy cracked that lock with a box in like 5 minutes, for 1/10th of price provider requested.
I'm repairing this one, that board is 4$, and need to find a good battery and voila, great secondary phone, not some crappy Lenovo.
Click to expand...
Click to collapse
I have a feeling that we have PM'd back and forth before, am I correct?
rjmxtech said:
I have a feeling that we have PM'd back and forth before, am I correct?
Click to expand...
Click to collapse
Yeah, yeah, same issues and rom developement, back then in 2016 Cheers.
ShadySquirrel said:
Yeah, yeah, same issues and rom developement, back then in 2016 Cheers.
Click to expand...
Click to collapse
Good to see you again haha. In regards to fixing your device, last year I unbricked my Asus TF300T by swapping in a new motherboard, and it had been bricked for 2-3 years by then. Luckily the almighty @timduru is still developing a 7.x ROM for it (and doing a great job at it too) so that device works great despite Nvidia ceasing development of GPU blobs for it ?.
rjmxtech said:
Good to see you again haha. In regards to fixing your device, last year I unbricked my Asus TF300T by swapping in a new motherboard, and it had been bricked for 2-3 years by then. Luckily the almighty @timduru is still developing a 7.x ROM for it (and doing a great job at it too) so that device works great despite Nvidia ceasing development of GPU blobs for it .
Click to expand...
Click to collapse
Eh, when I remember how much I've managed to do on marshmallow before device decided to stop collaborating with me... Gah. Had a quick fix few weeks after I bought new phone, but same problem occured few weeks ago and I decided to take it back and fix it. Part is ordered, probably will come in next 10-15 days. No plans for development, to be honest, I'm puting my prepaid SIM in that device and planning to use it as dash cam/navigation after I fix port, just to be able to charge it while in car... kiwi is there for messing around
ShadySquirrel said:
Eh, when I remember how much I've managed to do on marshmallow before device decided to stop collaborating with me... Gah. Had a quick fix few weeks after I bought new phone, but same problem occured few weeks ago and I decided to take it back and fix it. Part is ordered, probably will come in next 10-15 days. No plans for development, to be honest, I'm puting my prepaid SIM in that device and planning to use it as dash cam/navigation after I fix port, just to be able to charge it while in car... kiwi is there for messing around
Click to expand...
Click to collapse
ugh, so I am trying to put the latest TWRP back on this device because I am going to have to use this when I replace the battery in my nexus 6 soon, but I have no idea how to do so. Would you mind helping me out lol? I haven't touched this device since October.
rjmxtech said:
ugh, so I am trying to put the latest TWRP back on this device because I am going to have to use this when I replace the battery in my nexus 6 soon, but I have no idea how to do so. Would you mind helping me out lol? I haven't touched this device since October.
Click to expand...
Click to collapse
Root it (jellybean or kikat root), use Freegee to flash original twrp, then use Flashify to flash updated one. That was my procedure last time I flashed, somewhere ~ august 2015
ShadySquirrel said:
Root it (jellybean or kikat root), use Freegee to flash original twrp, then use Flashify to flash updated one. That was my procedure last time I flashed, somewhere ~ august 2015
Click to expand...
Click to collapse
I have the dreaded boot certification error right now due to flashing an unlokified TWRP image using DD lol, so I am spinning up my windows VM in virtualbox so I can see if I can restore it with LGFlashTool.
rjmxtech said:
I have the dreaded boot certification error right now due to flashing an unlokified TWRP image using DD lol, so I am spinning up my windows VM in virtualbox so I can see if I can restore it with LGFlashTool.
Click to expand...
Click to collapse
Looks like I'm only one who can get that working without issues, lol.
Synced Lineage 14.1 to build for my kiwi while I was at work this morning, and took a look at my e988 just sitting there... ugh, tempting. Got it a new LG certified battery yesterday, waiting for port to arrive... there will be some fun, lol.
ShadySquirrel said:
Looks like I'm only one who can get that working without issues, lol.
Synced Lineage 14.1 to build for my kiwi while I was at work this morning, and took a look at my e988 just sitting there... ugh, tempting. Got it a new LG certified battery yesterday, waiting for port to arrive... there will be some fun, lol.
Click to expand...
Click to collapse
I got it running again. I'm using the Cantana ROM. I found it to be the most stable for the e980.
rjmxtech said:
I got it running again. I'm using the Cantana ROM. I found it to be the most stable for the e980.
Click to expand...
Click to collapse
Mine is still on stock. Did some investigating this morning, and got an idea to build a complete new tree based on kitkat (instead of jellybean) but I'm too lazy to experiment... it's much easier when you have unlocked bootloader.
ShadySquirrel said:
Mine is still on stock. Did some investigating this morning, and got an idea to build a complete new tree based on kitkat (instead of jellybean) but I'm too lazy to experiment... it's much easier when you have unlocked bootloader.
Click to expand...
Click to collapse
I like Cantana tbh, it is actually stable and fast, like really fast.
A little squirrel I know has been working on digging up some Marshmallows for us. Hopefully he didn't misplace them ?
Lineage 13 - boots. Now to see will AOSP RIL work and fix some mess with LMK
No chance for a jump to Lineage 14.1 instead of 13 ? Don't get me wrong we all appreciate your work I'm just curious would it be the same amount of work to go on newest version of linage?
As per a statement posted on XDA, the OnePlus Nord OOS11 beta should be coming sometime this week, though the builds for the 7 series are still delayed as OnePlus is finally confronting the dreaded decryption issue that has plagued the series since its inception. This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP along with more custom ROM development on the way. This is very good news for the tinkering community. Hope more is to come in the near future.
I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.
gboybama said:
I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.
Click to expand...
Click to collapse
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?
You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.
Lossyx said:
You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.
Click to expand...
Click to collapse
On a good note it seems a couple more roms have come about
SenyorMauricio said:
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?
Click to expand...
Click to collapse
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!
gboybama said:
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!
Click to expand...
Click to collapse
Yeah, I'm hoping for the best. In the original article, it says that had to team up with Qualcomm to begin fixing the issue, so I'm thinking it's both a hardware-software problem, but I wouldn't know since I'm not very literate when it comes to technical issues like encryption. But we shall see! I really just want Oxygen OS on Android 11 since most of the ROMs right now have bugs (as far I've seen—haven't been able to find a ROM that doesn't irritate me in one way or another).
I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it
rob420p said:
I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it
Click to expand...
Click to collapse
For them yes.
But here's the thing.
Let's assume it's the same issue.
They probably broke or implemented encryption differently on a hardware level, hence contacting Qualcomm to help them workaround (not fix) the issue. We as in users, don't know what broke or is different, and since we don't have the source code we can't possibly know how OnePlus worked around it to decrypt data.
Let's hope something else was broken / implemented differently and not in a hardware level, then maybe it's fixed.
In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!
谷歌原生 said:
In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!
Click to expand...
Click to collapse
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.
Are we even getting the beta at this point, it's 20th Jan
[QUOTE =“ gboybama，：84324093，：1342510”]
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.
gboybama said:
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.
Click to expand...
Click to collapse
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.