Related
Now, using my Archos 70IT machine,
After bootup, I need to run z4root (temp root) to root the machine,
then, I open up the setcpu to check the CPU frequency profiles,
repeating the steps again and again for each boot up...
Heard that it is hard to root as the system files are protected using a squashfs compressed image (with encryption?)
Cannot touch the system files make me feel sad
- I want to modify the hosts file to bypass all the advertisements
- I want to remove not-used system apps
- I want to modify the init.rc (maybe lagfix?)
- I want to apply wifi ad-hoc fix
- bla bla bla....
So, I would like to ask for the progress of rooting? Any news? Anything I can help to speedup the investigation?
Many of plenty of thanks to all those rooting gurus ~~~ !
I also have same problem. Can anyone advise how to resolve. Many thanks.
I think, though I can very easily be wrong, the problem right now is gaining write access to the partitions, the main system partition is mounted Read Only.
I'm trying to find time to look at this but I don't think I'll be able to get any time untill the weekend.
DougEdey said:
I think, though I can very easily be wrong, the problem right now is gaining write access to the partitions, the main system partition is mounted Read Only.
I'm trying to find time to look at this but I don't think I'll be able to get any time untill the weekend.
Click to expand...
Click to collapse
Yeah, from following a bit of the action over at archosfans.com forums it seems the system is mounted as a read only SquashFS image.
As soon as I get my A101 I'll dig deeper into this problem. Hopefully we'll get a working solution
chulri said:
As soon as I get my A101 I'll dig deeper into this problem. Hopefully we'll get a working solution
Click to expand...
Click to collapse
Yes, I've been holding my order for the Archos 70 to see if root would seem plausible and I just ordered it now. A section at XDA together with Archos release of the source should help us in search for enlightenment
Delivery in 2-4 days, final exam for some electronics course next week and then I've got 30 days off Uni to spend on this...hopefully
I have an A70IT 8 GB and have yet to successfully get z4root to work on it. I'm using the latest version (downloaded today).
I look forward to hearing how some people are successfully doing it, at least I get the impression on the fan site, they are doing it successfully. If anyone knows or has the time / desire to help a fellow Archos user out, please feel free to contact me.
Bert Moshier
BGMArchos said:
I have an A70IT 8 GB and have yet to successfully get z4root to work on it. I'm using the latest version (downloaded today).
I look forward to hearing how some people are successfully doing it, at least I get the impression on the fan site, they are doing it successfully. If anyone knows or has the time / desire to help a fellow Archos user out, please feel free to contact me.
Bert Moshier
Click to expand...
Click to collapse
I had the same problem with Z4Root not working. I found that powering off (complete power off, no suspending or rebooting) the device and starting it back up again did the trick. I also found that I have better success getting Z4Root to run if its the first program I run after a fresh power up. Don't run anything until you Z4Root.
Let me know if this works for you or not.
I've been having inconsistent results, but just stumbled across something that might help.
set airplane mode
turn off unknown sources
turn off usb debug
power off
power on
reset airplane mode off/on (doesn't look like it is really on on reboot)
turn on unknown sources
turn on usb debug
run z4root
wait.
seems to be working more consistently. I think these tablets don't save the state of things like unknown sources and usb debug (and airplane mode) very cleanly.
does this proxy app work with z4root ?
http://forum.xda-developers.com/showthread.php?t=766569
i really would like to use the wifi at my university with my archos.
I've been using it for some time. The only trick is that you need uncheck USB Debugging and recheck every time you run the z4Root app. Doesn't matter if its currently on, uncheck/re-check and you'll be good.
kenyu73 said:
I've been using it for some time. The only trick is that you need uncheck USB Debugging and recheck every time you run the z4Root app. Doesn't matter if its currently on, uncheck/re-check and you'll be good.
Click to expand...
Click to collapse
Shouldn't it be possible to write a simple app that does this automatically on each startup after launch?
Tasker probably can. I haven't installed it to test yet.
Edit: Scratch that. USB Debug toggle is still on Tasker's to do
hosts file is now temporary editable: http://forum.xda-developers.com/showthread.php?t=866104
https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en
Has anyone managed to make it work? I've been trying using Easy UMS but no luck. Has anyone had any success and if yes please shed some light
Jonous said:
Has anyone managed to make it work? I've been trying using Easy UMS but no luck. Has anyone had any success and if yes please shed some light
Click to expand...
Click to collapse
Hi I'm the developer of DriveDroid.
I've been mailing some people who also have trouble with the Galaxy Note 2 and booting their PC with DriveDroid. Some background: the option 'USB Mass Storage' in DriveDroid sets the USB-mode to "mass_storage" (which is needed for your PC to be able to boot from your phone). The default USB-mode for Galaxy Note 2 devices is "mtp". This is no problem on most devices I've tried. Those devices also have a default setting of "mtp", but DriveDroid can change that and it'll work for most of them. Even after reconnecting the USB cable the settings will stay like it is.
However on the Galaxy Note 2, when the cable is reconnected (or the PC is rebooting) the setting will be forcefully set by the Galaxy Note 2 rom: it overrides the setting that is set by DriveDroid. You can check this by going to the preferences of DriveDroid -> check USB Mass Storage -> leave the preferences screen -> unplug and replug your usb cable -> go back to the preferences: you'll see that the option is now unchecked. Usually that option should be remembered across disconnects of USB.
This is quite annoying when you want to boot from your phone, since it'll reset the setting right after your PC has rebooted (which is when your bios needs the USB device to boot from).
I'm working with someone else on a hacky way to work around this problem, but we'll have to see whether it is actually solvable.
FrozenCow said:
Hi I'm the developer of DriveDroid.
I've been mailing some people who also have trouble with the Galaxy Note 2 and booting their PC with DriveDroid. Some background: the option 'USB Mass Storage' in DriveDroid sets the USB-mode to "mass_storage" (which is needed for your PC to be able to boot from your phone). The default USB-mode for Galaxy Note 2 devices is "mtp". This is no problem on most devices I've tried. Those devices also have a default setting of "mtp", but DriveDroid can change that and it'll work for most of them. Even after reconnecting the USB cable the settings will stay like it is.
However on the Galaxy Note 2, when the cable is reconnected (or the PC is rebooting) the setting will be forcefully set by the Galaxy Note 2 rom: it overrides the setting that is set by DriveDroid. You can check this by going to the preferences of DriveDroid -> check USB Mass Storage -> leave the preferences screen -> unplug and replug your usb cable -> go back to the preferences: you'll see that the option is now unchecked. Usually that option should be remembered across disconnects of USB.
This is quite annoying when you want to boot from your phone, since it'll reset the setting right after your PC has rebooted (which is when your bios needs the USB device to boot from).
I'm working with someone else on a hacky way to work around this problem, but we'll have to see whether it is actually solvable.
Click to expand...
Click to collapse
Many thanks for your very informative reply. I hope you can find a workaround. I guess we have to thank Samsung for all this trouble they have caused both users and devs by doing away with the mass storage option. Anyway good luck and i'll surely buy you a beer once you're there .
FrozenCow said:
Hi I'm the developer of DriveDroid.
Click to expand...
Click to collapse
Hey, FrozenCow, thanks for the realisation of the awesome idea! As a sys. admin, I find this feature really usefull. Shame it's not working on my Samsun S3. I have OTA JB update, rooted.
The problem as you said is dropping UMS when PC reboots, it's not like it's droping back to MTP, but it's just disconnecting from PC when PC reboot, and BIOS wont see my UMS drives, I managed few times to see them in BIOS setup, so I even managed to configured them, but any time I do reboot, it's lost. Some how there is should be a workaround to make this UMS persistant as a normal flash card.
Or probably it's me doing something wrong.
Looking forward to see this awesome piece of software got an update. Just can't say how cool it would be to just hold collection of bootable flash cards in my pocket which is always with me.
hmepas said:
Hey, FrozenCow, thanks for the realisation of the awesome idea! As a sys. admin, I find this feature really usefull. Shame it's not working on my Samsun S3. I have OTA JB update, rooted.
The problem as you said is dropping UMS when PC reboots, it's not like it's droping back to MTP, but it's just disconnecting from PC when PC reboot, and BIOS wont see my UMS drives, I managed few times to see them in BIOS setup, so I even managed to configured them, but any time I do reboot, it's lost. Some how there is should be a workaround to make this UMS persistant as a normal flash card.
Or probably it's me doing something wrong.
Looking forward to see this awesome piece of software got an update. Just can't say how cool it would be to just hold collection of bootable flash cards in my pocket which is always with me.
Click to expand...
Click to collapse
You could try to enable UMS from DriveDroid and reboot the phone. I've heard on Reddit that that seemed to have worked for them. However I do not know whether this could also be ROM related, but it is worth a try.
Here is the thread about the SGS3: reddit.com/r/Android/comments/1865c5/drivedroid_boot_a_pc_using_isoimg_files_on_your/c8c4pa6
(I'm not allowed to post urls)
FrozenCow said:
You could try to enable UMS from DriveDroid and reboot the phone. I've heard on Reddit that that seemed to have worked for them. However I do not know whether this could also be ROM related, but it is worth a try.
Here is the thread about the SGS3: reddit.com/r/Android/comments/1865c5/drivedroid_boot_a_pc_using_isoimg_files_on_your/c8c4pa6
(I'm not allowed to post urls)
Click to expand...
Click to collapse
Well somehow it's worked (did UMS in DriveDroid settings, then Rebooted). Not any time it's works, sometime my PC just hangs while trying to initialize USB Storage, not on every PC it's works at all, but yeah, even if it's works sometime its good to have that feature in the pocket incase i'll be caught offguard in need to fix something.
Thanks for the tip and for software.
I will try this tonight. Will report back asap.
Regards
Axelman
Sent from my GT-N7100 using xda app-developers app
Hmm, so it's still not stable. It's an annoying problem. What rom are you (all) using? It might be good to know whether you're running stock or something like CyanogenMod. I suspect the stock rom of doing extra stuff (like resetting USB settings) when USB is connected , but I need some confirmations on that .
FrozenCow said:
Hmm, so it's still not stable. It's an annoying problem. What rom are you (all) using? It might be good to know whether you're running stock or something like CyanogenMod. I suspect the stock rom of doing extra stuff (like resetting USB settings) when USB is connected , but I need some confirmations on that .
Click to expand...
Click to collapse
Model number: GT-I9300
Android 4.1.1
Baseband version: I9300XXELJ2
Kernel
3.0.31-500022
[email protected]#
SMP PREEMPT Thu Nov 29 11:12:09 KST
Build number
JRO03C.I9300ZSDLK4
I think i upgraded it once over the air, then i rooted it by CF Auto Root so auto update not works atm says phone is modefied. So its yeah, stock rom with root.
Most of the time I am pretty happy with it. You suggest me go on the loose and flash some custom roms in which DroidDrive should works better?
This app looks incredily interesting and usefull. I have so many bootable usb flash drives for different purposes that I can't quite keep track of them all I hope it can eventually be made fully functional with the Note II/S3, until then - d'oh @ Samsung!
-Mac
Sent from my GT-N7100 using Tapatalk 2
Great app ! Many thanks for your job.
Bad luck for I9300 users. I also have one. I will try asap your app. Maybe when using EasyUMS it could be able to boot a PC from phone.
I'll give you feedback soon.
Before I had this thing:
http://www.amazon.fr/gp/product/B00...SIN=B0069UVAHW&linkCode=as2&tag=amazon0d16-21
with Acronis true image, UBCD, DSL, Ubuntu, and WinPE. Working great.
But if my S3 can do the same think, it could be wonderful.
PS 1: @FrozenCrow: If you need french translation, I'm your man !
PS 2: Your app NEED to be on XDA Portal
DriveDroid should do somewhat the same what EasyUMS does with the UMS-checkbox in DriveDroids preferences. The problem I think is timing/resetting state that some devices seem to be doing. It resets and does it too slow, so the bios is already loading before it is done resetting. (Completely made up, I haven't tested such a device myself)
I've considered translations before, but didn't go through with it, since I was afraid releases would get stalled by incomplete translations (not sure how it works exactly though). Anyway, I want DriveDroid to be somewhat more stable/feature-complete for people before doing translations.
Good idea about XDA portal. I'm going to release a new version soon. I'll tip xda-developers after that version has proven to be stable.
FrozenCow said:
DriveDroid should do somewhat the same what EasyUMS does with the UMS-checkbox in DriveDroids preferences. The problem I think is timing/resetting state that some devices seem to be doing. It resets and does it too slow, so the bios is already loading before it is done resetting. (Completely made up, I haven't tested such a device myself)
I've considered translations before, but didn't go through with it, since I was afraid releases would get stalled by incomplete translations (not sure how it works exactly though). Anyway, I want DriveDroid to be somewhat more stable/feature-complete for people before doing translations.
Good idea about XDA portal. I'm going to release a new version soon. I'll tip xda-developers after that version has proven to be stable.
Click to expand...
Click to collapse
Dude, firstly thanks for the JEWEL program!
I wonder if you can create NTFS partitions to install Windows 8 or any other alternative?
I think if I do that, will win MANY thousands of followers.
Thanks again
Well, NTFS is a closed and complex filesystem. There are tools/modules that support NTFS, but those will be hard to use from DriveDroid since they are native (depending on arm/x86). Implementing it myself in Java is quite an undertaking.
You can just format a blank disk through Windows with any filesystem you want. This is what I've done to get a Windows install disk running from DriveDroid: http://softwarebakery.com/windows-install-on-drivedroid
What I'm working on atm is support for true CDROM emulation. It should allow you to use all ISOs as-is, since the bios/OS sees the device as a normal CDROM drive. This way you don't have to convert the ISO to a format that is compatible with USB (so formatting with NTFS will not be needed). The problem is that this requires a kernel patch to allow DriveDroid to enable CDROM emulation and another patch to fix a incompatibility that caused BIOSes to not recognize the CDROM drive correctly. This patch was just accepted 4 days ago for CyanogenMods kernel for the i9000.
When I've added support for this in DriveDroids menus, I can try to apply the patches to kernels of other devices, let some people test the kernel and submit the patches to CyanogenMod. Hopefully the more popular devices can get support for true CDROM emulation that way. It *should* be better than letting DriveDroid format images if it all works as planned.
FrozenCow said:
Well, NTFS is a closed and complex filesystem. There are tools/modules that support NTFS, but those will be hard to use from DriveDroid since they are native (depending on arm/x86). Implementing it myself in Java is quite an undertaking.
You can just format a blank disk through Windows with any filesystem you want. This is what I've done to get a Windows install disk running from DriveDroid: http://softwarebakery.com/windows-install-on-drivedroid
What I'm working on atm is support for true CDROM emulation. It should allow you to use all ISOs as-is, since the bios/OS sees the device as a normal CDROM drive. This way you don't have to convert the ISO to a format that is compatible with USB (so formatting with NTFS will not be needed). The problem is that this requires a kernel patch to allow DriveDroid to enable CDROM emulation and another patch to fix a incompatibility that caused BIOSes to not recognize the CDROM drive correctly. This patch was just accepted 4 days ago for CyanogenMods kernel for the i9000.
When I've added support for this in DriveDroids menus, I can try to apply the patches to kernels of other devices, let some people test the kernel and submit the patches to CyanogenMod. Hopefully the more popular devices can get support for true CDROM emulation that way. It *should* be better than letting DriveDroid format images if it all works as planned.
Click to expand...
Click to collapse
Phenomenal idea, my friend ... Very good indeed!
I asked about NTFS disk size for Windows 8 is greater than 4 GB, making it impossible to use in DriveDroid since he only accepts partitioning Fat (3999MB).
One suggestion, why not create an official thread on XDA here the program to provide support or get help with other people?
Your program is VERY helpful and make sure the buy!
Thank you immensely!
Yes, FAT32 isn't great. I've formatted my external SDcard with ext4, so I can put Windows 8 on it (installed my PC with DriveDroid+UEFI recently). Problem with this approach (on CyanogenMod at least) is that it doesn't automatically mount the SDcard anymore, so I have to go to the terminal to mount the filesystem agian after every boot of the phone. Not ideal, but could be a workaround for you too.
Well, I'm not familiar with posting on xda, what subforum do you suggest to post in?
FrozenCow said:
Yes, FAT32 isn't great. I've formatted my external SDcard with ext4, so I can put Windows 8 on it (installed my PC with DriveDroid+UEFI recently). Problem with this approach (on CyanogenMod at least) is that it doesn't automatically mount the SDcard anymore, so I have to go to the terminal to mount the filesystem agian after every boot of the phone. Not ideal, but could be a workaround for you too.
Well, I'm not familiar with posting on xda, what subforum do you suggest to post in?
Click to expand...
Click to collapse
Well, I recommend that you create a new topic in this link> http://forum.xda-developers.com/forumdisplay.php?f=530 explaining about the program and inviting staff to test it and help in its development. There's plenty of people here who will be able to help you in major problems and suggest possible solutions.
Any questions, see some other topic to understand more or less how it works, but it is easy, do not worry!
When you create, post the link here for me to put on the favorite and follow!
Good luck friend
Hi im using drivedroid since today (Samsung GT-I9000B) and its great but it doesnt work with ISOs i donwloaded (xmbcubuntu and geexbox from the download option) when i selected the iso it doenst mark it as mounted and i cant see it on the pc .
Althougt on the background it does seems to work, here a logcat :
drivedroid: > (echo "" > "/sys/devices/platform/s3c-usbgadget/gadget/lun1/file"); ERROR=$?; echo; echo "###$ERROR"
drivedroid: <
drivedroid: < ###0
drivedroid: > (cat "/sys/devices/platform/s3c-usbgadget/gadget/lun1/file"); ERROR=$?; echo; echo "###$ERROR"
drivedroid: <
drivedroid: < ###0
drivedroid: > exit
drivedroid: > (echo 0 > "/sys/devices/platform/s3c-usbgadget/gadget/lun1/ro"); ERROR=$?; echo; echo "###$ERROR"
drivedroid: <
drivedroid: < ###0
drivedroid: > exit
drivedroid: > (echo "/emmc/images/geexbox-3.0-i386.iso" > "/sys/devices/platform/s3c-usbgadget/gadget/lun1/file"); ERROR=$?; echo; echo "###$ERROR"
drivedroid: <
drivedroid: < ###0
drivedroid: > (cat "/sys/devices/platform/s3c-usbgadget/gadget/lun1/file"); ERROR=$?; echo; echo "###$ERROR"
drivedroid: < /storage/sdcard1/images/geexbox-3.0-i386.iso
drivedroid: <
drivedroid: < ###0
drivedroid: > exit
drivedroid: > (getprop sys.usb.config); ERROR=$?; echo; echo "###$ERROR"
drivedroid: < mass_storage,adb
drivedroid: <
drivedroid: < ###0
drivedroid: > exit
So for what i understand should have worked but the usb icon doesnt change and on the Pc i cant see it
But not all is lost , i add the 'images' of /sdcard and /emmc ( pionting to /dev/block/vold/179:X ) and that worked ok so now i can mount and unmount sdcard and emmc at will ,usb icon on app show ok for this
¿what can i be doing wrong? i suppose that the iso i downloaded (from the app itself) are on the right format or not? i will be doing some check on the ISOs later (im at work right now)
Thanks for your work!
FrozenCow said:
What I'm working on atm is support for true CDROM emulation. It should allow you to use all ISOs as-is, since the bios/OS sees the device as a normal CDROM drive. This way you don't have to convert the ISO to a format that is compatible with USB (so formatting with NTFS will not be needed). The problem is that this requires a kernel patch to allow DriveDroid to enable CDROM emulation and another patch to fix a incompatibility that caused BIOSes to not recognize the CDROM drive correctly. This patch was just accepted 4 days ago for CyanogenMods kernel for the i9000.
When I've added support for this in DriveDroids menus, I can try to apply the patches to kernels of other devices, let some people test the kernel and submit the patches to CyanogenMod. Hopefully the more popular devices can get support for true CDROM emulation that way. It *should* be better than letting DriveDroid format images if it all works as planned.
Click to expand...
Click to collapse
Verizon Galaxy Note II
Hello,
I'm trying to use this with the stock, deodexed, rooted ROM for my Verizon Galaxy Note II. I tried disabling/reenabling UMS, rebooting the device, the SGS3 Easy UMS app to no avail.
I have a BIOS password set on my laptop, that actually may/may not be helping as it pauses there for a bit while I type the password. This should allow me to do whatever steps necessary on the phone to make this work.
Any suggestions?
PS - I just downloaded the latest CM10.1 nightly to check to see if this helps at all.
Author?????
After suffering for many months from terrible performance and performance that gets progressively worse, I've finally decided to abandon the stock ROMs (been through every single one since February 2012) and go with Clean&Slim (hoping it lives up to its name).
I also have this annoying problem with the "Indexing Files" which never stops and eventually crashes the tablet event with the very latest ROM .....28. So started this morning...
I've done the SDE thing and was about to push Clean_Slim&FastV02 to the tablet but realised that the recovery partition presented to Windows is only 300Mb and the ROM is 375Mb.
How do I get around this for a G9 ?
Thanks
You are doing it wrong. Did you read the install guide?
connect USB cable ( PC <-> Tablet ) ;
unzip Clean_Slim&FastV02.zip.zip
put archos.ext4.update in your device, or > adb push archos.ext4.update mnt/storage/
go to recovery SDE and Remove Android kernel if you have already installed any official firmware !
go to Flash kernel & Initramfs and copy here zImage and initramfs.cpio.lzo -> in the new driver that appeared !
Ok ! ... & wait to boot !
Click to expand...
Click to collapse
Sent from my GT-I9100 using xda app-developers app
OK, I realised I was starting all wrong but I still don't understand which physical location to put the ROM file in if I choose not to use ADB?
OK, I now realise the ROM just goes in the ROOT. I've re-imaged. All is good. I wish everything was that easy! Thanks
It makes the tablet a little faster but don't expect miracles
Sent from my ARCHOS 80G9 using xda app-developers app
I did install Cyanogen Mod 10.1 from the link in the "Free Xperia" thread (stable pollux_windy) today. It actually was an update from a nightly version from some days ago. It works pretty well except the gps, which doesn't work at all. I've done some googeling, but I didn't find anyone with similar problems. GPS worked fine for me with the stock rom, so i guess the chip is working. If i use a GPS tester, it shows that 0 satellites are available. I've not switched back to stock to try if it still works, because I had hoped that i could save all the time.
The positioning system works from time to time, but I guess it is only Wifi positioning. If i deactivate the Wifi positioning, it can't get any gps fix.
What i tried so far:
Stop/Reboot/Restart GPS
Wipe Cache and Dalvik Cache
Reboot again and again and again
Comparing the GPS.conf to the one from the stock rom (they are identical)
This is the first time I tried installing a custom rom, so there is a high chance, I did something wrong, but i would really appreciate if someone told me what it was. And please remember, that i'm quite new to the whole custom rom scene.
Not getting any answers at least tells me the problem is not that simple and I am not too stupid.
I thought till now at least anyone would have asked for details or anything.
Please anyone help! I desperately need the GPS!
Woozar said:
Not getting any answers at least tells me the problem is not that simple and I am not too stupid.
I thought till now at least anyone would have asked for details or anything.
Please anyone help! I desperately need the GPS!
Click to expand...
Click to collapse
Woozar,
working now to understand the problem. You know adb connection (debug mode)??. You know how to create logcat.txt??.
Asap I will tell you if I find the solution....
Regards
I just googled it. I need to use usb debug mode and then attach it to a pc with the android ask installed and run the command
Code:
adb logcat -d > logcat.txt
Do I need adb root access for this?
Shall I upload the file to the thread or send it to you personally?
Woozar said:
I just googled it. I need to use usb debug mode and then attach it to a pc with the android ask installed and run the command
Code:
adb logcat -d > logcat.txt
Do I need adb root access for this?
Shall I upload the file to the thread or send it to you personally?
Click to expand...
Click to collapse
make cold reset on GPS status app Pro
download AGPS
Swicth off the tablet
start adb logcat just after power on the tablet.
open GPS status again, download again AGPS.....
wait for searching in open sky area
only stop it after few min gps status is running...lets say 10 minutes.
press Ctrl+C on terminal mac to stop logcat.txt
send logcat.txt link download to me private.
I will use my and yours to search what is failing...
which CM10.1 running now...me experimental 25/06/13.
Sorry no time now...
I am not allowed to post links, so I need to post it like this.
https ://dl.dropboxusercontent.com/u/11941413/1
I hope I did everything as you wanted me to.
Please let me know if you need anything else.
Woozar said:
I am not allowed to post links, so I need to post it like this.
https ://dl.dropboxusercontent.com/u/11941413/1
I hope I did everything as you wanted me to.
Please let me know if you need anything else.
Click to expand...
Click to collapse
logcat.txt was good, but not usefull info errors.
I sent you private message here.
Regards.
Does this affect all sgp311 or does it work for anyone?
Is sgp 312 or 321 affected, too?
I'm in the same boat and after researching the XDA forums for a while it seems to me that GPS is not working in any of the current custom ROM's for our device. If GPS is important for you you would have to stick to the Stock ROM and wait a little bit more until the developers fix it.
For reference:
---------------------------------
SGP311 - Wifi-only Version (16GB) => CyanogenMod 10.1 (pollux_windy) = No GPS
SGP312 - Wifi-only Version (32GB) => CyanogenMod 10.1 (pollux_windy) = No GPS
SGP321 - LTE Version => CyanogenMod 10.1 (pollux) = GPS is working
---------------------------------
Tip: Some very resourceful user suggested a neat workaround where you could use the GPS from a mobile phone in the tablet. I didn't try it yet but it seems to be a good idea:
http://forum.xda-developers.com/showpost.php?p=43159748&postcount=10
I hope this helps!
Introduction
A new, updated version of Android for the Nintendo Switch. Now based off of Android 10 (Q) (LineageOS 17.1 with Shield TV trees) it's faster, more responsive and has many new features over the previous release, including deep sleep and an Android TV build.
Features
Android 10 based on Lineage 17.1
Significantly improved UI smoothness compared to Oreo.
OTA updates (bugfixes and new features without a reinstall).
Deep sleep that can last for weeks compared to hours in the previous version.
RSMouse support for controlling a mouse cursor with your right stick
Full Joy-Con and Pro Controller support with analog sticks and rails.
Hori Joy-Con support.
Uses Joy-Con HOS Bluetooth paring data.
Both Android TV and Android Tablet builds.
Reworked fan profiles for quieter operation.
Optimized dock support with resolution scaling.
OTG support including DisplayPort or HDMI output (no power supply necessary).
3rd party dock/hub support including DisplayPort or HDMI output.
Rewritten charging driver to properly support USB-PD.
Optimized touch screen driver.
Easier install via hekate partition tool.
Reworked, simpler, power profiles.
Much improved WiFi driver with less dropouts.
Shield TV remote app support for easy docked control.
Reboot to payload support.
Improved Bluetooth accessory support.
Auto rotation support.
Installing
Follow the tutorial here
Stay in touch
Discord:https://discord.gg/6gWvaASF72
Twitter: https://twitter.com/switchroot_org
Website: https://switchroot.org/
Sources
https://gitlab.com/switchroot/android
https://gitlab.com/switchroot
See manifest repo for build instructions.
Credits
Ave - Handling hosting of OTAs and the switchroot website. Check out her patreon!
CTCaer - Fixing a lot of things in the kernel - charging, dock, touch etc - and adding Android install support for nyx. Donate to his patreon here!
Langerhans - Figuring out the majority of stuff for deep sleep and helping massively with initial bringup.
Steel01 - Maintaining the Shield TV Lineage trees which ours are heavily based on.
Nvidia + Nintendo - ❤
Everyone else who contributed!
Reserved
Amazing! Thanks to all the devs working on this <3
Wooohoo finally here, running since Jan without issues, definetly faster than Oreo, looking forward to reflash now that it is official
Super excited about this. Long time coming!
It's a Great day for the Switch modding scene.
Thank you Switchroot team you are the best.
You guys have made my Switch a ton more useful, thanks for all the work you guys put in! ★＼(^▽^ )♪
Android 10 and Deep Sleep are great to have! Haven't tested the build yet since I won't be free until tomorrow but I'm looking forward to it!
Edit: Forgot to edit it, just chiming in to say that I've been loving it! Thank you so much devs!
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Absolutely fantastic! Thanx a lot for the release
Very exciting day, big thanks to everyone who worked so hard on this! I loved playing with the original Android release, but decided to wait for a version with the kinks worked out, looking forward to diving back in!
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
rac08241988 said:
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Just follow the guide in post
Click to expand...
Click to collapse
sashka69 said:
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
Click to expand...
Click to collapse
Dirty flash wont work, you need to wipe and repartition in hekate
bylaws said:
Dirty flash wont work, you need to wipe and repartition in hekate
Click to expand...
Click to collapse
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Fukurou83 said:
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Click to expand...
Click to collapse
The Installation Guide's 20th step is "If setup gets stuck on voice detection go back to the wifi config page in the setup and select "Skip for now"".
This should solve your issue!
Wow there it is finally!
Well done!
rac08241988 said:
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Click to expand...
Click to collapse
try redownloading, we updated the zips
bylaws said:
try redownloading, we updated the zips
Click to expand...
Click to collapse
I got it. I don't know what happened but it worked the second time I did it. Sorry for wasting people's time lol I like the improvements alot. So glad lockscreen and battery charging indicator is working properly now.
I'm simply amazed. Thank u so much for all the months of hard work @ANyOne involved!
I've got two questions:
1. If I go for the non-Android TV image, can I control the Switch in the dock with the Joy-Cons wirelessly?
2. If going for the Android TV image, would it support the Google Cast protocoll receiver-sided (meaning I could cast to it)?
Edit: Please let me add a third question:
3. Can Android access the FAT32 partition I'm using in Horizon?
Aka can I continue my SNES savegames in Android's RetroArch by pointing it's directory settings to the same folder on the FAT32 partition I'm using in Horizon's RetroArch for the savegames?
Followed the guide and been testing for a bit, this version is incredibly smooth compared to the previous one, i barely get any lag with a 64GB class 10 card