Got some spare time at the moment so I've decided to attempt to tackle this one. As far as I can see a windows 8.1 Jailbreak is already out of the question. To many people have tried and failed so tbh I'm not even going to attempt it!
Downgrading to windows 8 on the other hand does seem plausible.
What I have already discovered:
The Surface RT 8.0 image will boot and BSOD.
The cause of the BSOD is down to both storage and display drivers , a modified WIM with the surface 2 storage drivers will allow the os to install and boot to a BSOD with graphical glitches relating to the display driver.
Booting without video drivers and forcing the standard VGA compatible driver causes no output after the surface logo however it does not seem to BSOD, the system keeps on running providing both USB power and power to the typecase. Plugging in an external display also has no output but the monitor does detect a device.
I already have an original RT downgraded to 8.0 that I can use to aid development.
From what I can tell the main issue of getting display output is down to the Tegra 4 VGA driver not being compatible with windows 8, probably down to driver signing. I already have a few ideas on how to tackle this.
Its been over 6 months since I looked into this and I have since sold my surface 2 but I've decided to order a used one to continue with the project, I feel there is still some life left in the hardware and I would like to be able to use it to its full potential.
If I've missed anything or if anyone has any ideas please let me know. As soon as I have the surface 2 I will be continuing with this and will hopefully have a test image in the coming months
Related
So, now that windows phone 7 is out, is there any chance of us getting a port for the rhodium? I realize every windows phone 7 phone has a snapdragon and the os is pretty resource extensive, but is it possible, mindful of the performance degradation?
As has been said in the dozen other threads on the same subject...no.
kanwal236 said:
So, now that windows phone 7 is out, is there any chance of us getting a port for the rhodium? I realize every windows phone 7 phone has a snapdragon and the os is pretty resource extensive, but is it possible, mindful of the performance degradation?
Click to expand...
Click to collapse
You're kidding; yes? It makes no sense to try; however maybe the HD2.
tbh the OS is very complex and idk how itll behave on a storage card if youre talking about a port like XDANDROID, its very possible but itll need some serious time to optimize and be able to run flawless on our TP2s
Logical Answer (No Point)
Even if it were possible for developers to dedicate their time to yet another major long-term project, why would they when the hardware necessary to use WP7 isn't supported on Windows Mobile devices or if they found a work-around it wouldn't work as good.
I think the fact that we have Android is good enough, WP7 is a fresh OS and deserves better. — It's the same mentality as people who use OSX Visual Styles on their Windows 7 machines, it makes no sense or the people who use the iPhone or now WP7 overlay app on their device.
As much as I love the touch pro 2 for it's solid build quality and amazing keyboard; let's be honest, the smudgy resistive screen isn't nice compared with a capacitive AMOLED screen and many other reasons why WP7 wouldn't be as glamorous as on a new device.
*Also, look how long it took the team to get Android to run to a usable/enjoyable point, by that time Froyo was already released and you could have made enough money to go out and buy a brand new Android device. — With WP7 the project will be even longer in my opinion, as there are more components to think about in regards to how the OS operates and functions. (No 'expandable' SD-card, can only sync via Zune software and many other barriers)
*-No disrespect to any of the XDAndroid team you all did an awesome job, just pointing out the fact that delays and issues are to be expected, so WP7 would just be an even greater headache which isn't worth it, might as well start a WP7 project fresh with WP7 hardware then the fun can begin.
Hi All,
Just wondering if anyone can help me diagnose a battery drain issue.
I've found mention of the bluetooth driver causing issues on the preview, but this doesn't seem to be what I'm seeing.
Just in case, I've left bluetooth switched on.
I've just received a batch of 26 Surface RTs under the deal that Microsoft was recently running for education.
I'm just trying to decide on the configuration that we will initially run with in the classroom, and have been testing Win 8.0 and also 8.1 RTM on two different tablets.
Both have touch covers, and are connecting to the same 5GHz Wireless N access point.
Obviously, battery life is really important to us, as we need to achieve a whole day of reasonably heavy classroom usage.
Right now, the WIn 8.0 Surface is beating the pants off the 8.1 device.
They both have the same applications installed, and I'm at a loss as to why the 8.1 is so bad.
I fully charged both devices yesterday, and overnight the 8.0 unit lost 4% charge, whilst the 8.1 lost 21%.
I've attached a sleepstudy report from the 8.1, and was wondering if someone could cast their eye over it for anything obvious.
I should point out that battery life was poor on the 8.1 even before I started installing apps, so I'm not convinced that any one app is particularly to blame.
Both units have the latest available updates installed on them.
Thanks,
Andy.
I've been running RTM on my RT for about 3 weeks and it's really hurt my experience with the device so far. From a features standpoint it is quite a step up, but no word about when/if the battery issue will be fixed. I have searched and not found any explanation the change yet. My sleep study stuff didn't really turn up anything to my eye but I'm not much of an expert in this realm.
Interestingly it only drains badly in sleep on some days. I don't really do anything different with it on those days that I've noted either, as I pretty much exclusively use the device to take notes in classes and study them.
Every post about trying to get to the bottom of the issue mostly results in people posting about the Bluetooth bug =)
Glad to hear it's not just me.
I googled and searched on here extensively before posting this thread.
I've checked my sleepstudy report, and I'm not seeing activity in the UART driver area that characterises the bluetooth issue, so I can only conclude that I've got a different issue.
It's a real issue for me, as having Outlook was one of the main reasons we opted for the RT's. I can't go back to 8.0, and I can't roll out with 8.1 as the battery life is so dreadful.
I'm hoping that once it's released officially (tomorrow, I think), then fixes will start flowing.
I have had similar bad experience after upgrading to 8.1 a while ago (not Preview 8.1). Sporadically battery life would tank and for no apparent reason battery would drain while the RT was in sleep mode. This never happened on 8.0. I could let it sit for days without a problem.
On my desktop system I've seen that the mail app is often using up a lot of CPU time (Communication Service) . I can see this draining the battery on the RT.
Since I received a firmware update three days ago and all the updates yesterday it seems to be better on the RT. It is still almost fully charged since my last charge last night. I will only know for sure in a few days of course. Hope this is fixed quickly. And yes, it has nothing to do with the BT fix.
In your case I definitely suggest contacting Microsoft directly. I assume with 26 purchased RTs you will get appropriate support.
Let's hope this will be a problem of the past soon.
cheers
edit1: another day and still going strong. No issues with battery drain so far
I thought it was fixed after updates on release day as it went well.... Had a drain day yesterday. Maybe improved...
I have the BT off and I still not using Outlook. That said, I don't notice any issues with my battery and comparing with another friend of mine we both believe we have about the same or a little better battery life.
I have now noticed the same thing. Left my surfaced on over the night and my drain was HORRIBLE! came back to use it today and it had gone from 80% to 25%! I'm done all the latest updates and am on 8.1
Globalrebel said:
I have now noticed the same thing. Left my surfaced on over the night and my drain was HORRIBLE! came back to use it today and it had gone from 80% to 25%! I'm done all the latest updates and am on 8.1
Click to expand...
Click to collapse
I came back to post mine has been good with no drain for 3 days now. I'm not convinced it isn't going to randomly betray me again though.
I left mine sitting since last night and will check it when I get home. Lets see how good this works.
Known Surface RT upgrade issue from 8.1 Preview to 8.1 RTM
I just wanted to let you know that there's actually a known battery drain issue when upgrading a Surface RT (doesn't affect Pro) from 8.1 Preview to 8.1 RTM. Upgrades directly from 8.0 to 8.1 RTM won't see the issue.
You can fix the issue on affected devices by following the instructions on the Surface support page (Sorry I can't post a link, bing for "Surface RT and Surface 2 battery and power" and you should find it).
I'll copy them here for reference.
Surface RT only: Battery issue when updating from Windows RT 8.1 Preview
If you updated Surface RT from Windows RT 8.1 Preview to Windows RT 8.1, you may notice a decrease in battery life. During the update, the wireless adapter power policy isn’t migrated. Instead, the power policy is set to a default value that consumes more power both during use and in the connected standby state.
To restore the wireless adapter power policy to the correct settings, open an administrator command prompt:
Step 1: Swipe in from the right edge of the screen, and then tap Search.
(If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.)
Step 2: In the search box, enter command prompt.
Step 3: Touch and hold (or right-click) Command Prompt to bring up the context menu. Tap or click Run as administrator.
Step 4: On the User Account Control dialog box, tap or click Yes.
Step 5: At the Administrator: Command Prompt, enter the following:
powercfg -setdcvalueindex SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 3
Step 6: Then enter
powercfg -setactive scheme_current
Click to expand...
Click to collapse
kf_man said:
I just wanted to let you know that there's actually a known battery drain issue when upgrading a Surface RT (doesn't affect Pro) from 8.1 Preview to 8.1 RTM. Upgrades directly from 8.0 to 8.1 RTM won't see the issue.
You can fix the issue on affected devices by following the instructions on the Surface support page (Sorry I can't post a link, bing for "Surface RT and Surface 2 battery and power" and you should find it).
I'll copy them here for reference.
Click to expand...
Click to collapse
Here is the thread on the surface support site: http://www.microsoft.com/surface/en-us/support/hardware-and-drivers/battery-and-power
Note that this is Surface RT specific, not applicable to the Pro, nor other RT devices.
Thanks,
--randy
Hi!
I have a couple of older (5-pin) MIDI keyboards and a USB-to-MIDI "cable/dongle". I'm fairly (99%) this is class compliant, since it works perfectly on my Mac and my iPad without any drivers. I have, however, not confirmed this. But I'm actually very sure that iPad required class compliant hardware to work at all.
Anyway. When I connect this cable to my Note 8.0, my software (Synthesia, full unlocked version) does NOT recognize the keyboard(s) at all. The same software and hardware works perfectly well with my Sony Xperia Z Ultra however, so it should not be Android-related.
Question is, has Samsung disabled SO MUCH of the Android functionality on their devices that they've "accidentally" also disabled this? (Since they HAVE disable using USB-to-Ethernet devices, even class compliant ones.)
Each device is running with latest official ROM, but I'm willing to flash a custom ROM if that does away with the problem. I highly suspect that it will.
I have given up trying to contact Samsung themselves about ANYTHING, since their attitude towards tablet-customers is pretty much "hugemiddlefinger.jpg"
ps. I have ordered a USB-to-SamsungTablet cable and when it arrives I'll try with my P1000 and P6800 tablets and will let you know if these work.
Now that Google has officially brought the Play Store to Chrome OS, do you think that Google might bring Chrome OS to the Pixel C through an update?
Personally, I think they should, given the fact that the Pixel C was originally intended to be a Chrome OS device.
EDIT: Forgot to mention that I would want them to make it so you could dual boot between Android and Chrome OS. Obviously if they replace the OS completely I would not be too happy about it.
I am thinking why would I want Chrome OS, I hope not.
I also doubt it would happen with the Pixel C, maybe something in the future but not the Pixel C.
I think at this point, it is highly unlikely Google will do anything to drastically change the layout of the Pixel C. However, they do need to better optimize Android for tablet usage and overall make it more feasible as a desktop-like OS. Sure, there's multiwindow support supposedly coming with Android N, but they really need to make it generally easy to use if Google hopes to attract more people to devices like the Pixel C.
While I love my Pixel C, I also would have no real use for it without my desktop as well. Android as an operating system is great for devices more geared towards entertainment media consumption, but they have a long ways to go if they hope to be any form of effective productivity machines. While they have since officially denied rumors of merging Chrome OS and Android, I do hope they create some form of format for the Pixel C that is similar to Chrome OS, as well as iron out some of the ever-present bugs as well.
Now if only Google would make a Pixel Phone.....
ChromeOS is getting more Android goodness with better integration than the ARCWelder. So that argues that larger tablets should come with ChromeOS for better multitasking and run Android apks where ChromeOS may be lacking.
However given so few Pixel C sold, it doesn't make sense for Google to productise a ChromeOS ROM for the Pixel C, but rather for its successor.
My Chromebook (based on Intel) I put into developer mode, install Ubuntu via Crouton, then installed Virtualbox and run a Windows VM, hence I got ChromeOS, Ubuntu and Win7 all in one $400 large screen full backlit keyboard with trackpad and a $30 128GB SD card. I tend to stay in ChromeOS unless I got an unsupported media to play then use Ubuntu, and for the odd Windows app I boot that.
Compare to Pixel C.... expensive, no expandable storage and one OS (Android).
These devices are the same weight, just different robustness and from factor.
I got my Pixel as a replacement for my desktop and I would love to have ChromeOS on it, instead of Android, or the ability to switch between the two on the fly depending on whether or not it's docked to a keyboard or not.
I doubt it'll come as an automatic update. It's not 'right' to force people who bought an Android device to switch them to a completely different OS.
May be as an optional update with a lot of warnings but the Google will have then to support 2 different firmware lines for the same device.
I know I'd like that but I have very little hope.
Agreed, it would most likely come in the form of a custom ROM.
Sent from my Pixel C using Tapatalk
Hello everyone, it is possible to receive custom ROM "Android O" for our Zenfone 2 ???
O was just announced, we're going to have to wait a little longer before we can know if it's possible, and a lot longer before it's actually built.
adobrakic said:
O was just announced, we're going to have to wait a little longer before we can know if it's possible, and a lot longer before it's actually built.
Click to expand...
Click to collapse
It's a good thing you answered first. I would not have been as diplomatic. Lol
Sent from my ASUS_Z00A using Tapatalk
Here comes ETA posts
Yes, it is posible but first need the sources and the sources are released after the official version is pushed to Nexus devices, maybe in October September will have and alpha version of Android O
Completely possible, thru custom ROMs
Sent from my Zenfone Max on AOKP N
mrichiem said:
Completely possible, thru custom ROMs
Sent from my Zenfone Max on AOKP N
Click to expand...
Click to collapse
I wouldn't say completely. Google is laying out minimum hardware requirements for stuff like audio, vr and ar which our old phone may not mean.
But do I have confidence that our devs will make everything else work? Yes, completely. Although it's gonna take a long time. I will be elated if N hits stable.
Since the question of this topic can't really be answered, someone knows how long statistically can a device be supported by custom roms? I mean maybe Android Z is too far fetched, but android P for example?
distant_thunder_89 said:
Since the question of this topic can't really be answered, someone knows how long statistically can a device be supported by custom roms? I mean maybe Android Z is too far fetched, but android P for example?
Click to expand...
Click to collapse
Same answer as before, it all depends on hardware requirements
Sent from my ASUS_Z00A using Tapatalk
Thanks all for different opinions and answers
blazzer12 said:
I wouldn't say completely. Google is laying out minimum hardware requirements for stuff like audio, vr and ar which our old phone may not mean.
But do I have confidence that our devs will make everything else work? Yes, completely. Although it's gonna take a long time. I will be elated if N hits stable.
Click to expand...
Click to collapse
well my current daily driver is an AOKP 7.1.1 Nougat on my Zenfone Max ZC550KL with no bugs so we can hope the same for O when Lineage OS releases its own version.
Sent from my Zenfone Max on AOKP N
kenbo111 said:
Same answer as before, it all depends on hardware requirements
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Hardware is the least of our problems, considering the one in Zenfone 2 (ZE551ML for example) is more than adequate.
Google making up it's own hardware requirements is nothing more than pandering to the idea of planned obsolescence to be honest so that they can sell newest phones.
I think that if the devs can get their hands on viable drivers that support the hardware in our devices and are compatible with Android 8, then technically, it shouldn't be an issue.
For Oreo, google would be pushing certain updates (fixes, etc.) not as a standalone feature, but something that would work in the same way as Windows and MacOS system updates do within the same OS version.
We know Windows updates usually work on a variety of hardware if the Windows as an OS is the same... the only thing that you also need are drivers to properly support the hardware in question (which can be difficult if the hardware is ancient, but I doubt this would apply to Zenfone 2) - this especially applies to upgrading from say Windows 7 to Windows 10 for example as some features like a microphone might stop working if the hardware in question was say from 10 years ago. Works on say Windows 7 for example because Vista drivers were made for the hardware in question which were compatible with Windows 7 to a point, but for Windows 10, compatibility between drivers for older Windows was not maintained and new drivers need to be written.
So, large OS replacement would likely depend on hardware drivers support and updating the OS sequentially shouldn't be an issue if the drivers exist - if they don't... then it's a problem.
Manufacturers tend to stop supporting hardware after a certain time... OEM's are even worse.
If we can find drivers independently from a company that produced it, then it might be possible to find more recent drivers that work.
In case of GPU's (or any other hardware inside your PC), you wouldn't rely on the OEM for drivers. You'd go to AMD's or Nvidia's websites to download latest drivers.
issou la chancla ?
:highfive: