Hello, everyone!
If you aren't an expert - that's okay. Everyone is welcome and you're free to ask questions.
Make sure to check the date this post was updated (I may forget to update the date in the title) which is located at the bottom of this post. If this post hasn't been updated in more than a month, contact me and I'll refresh everything.
Quick Introduction:
I'm new to the Yoga Book squad, and I've noticed one major downside.... the forums are a total mess. So what I'm hoping to do, is to keep this thread as up-to-date as possible, with links to guides, development progress and anything else.
I figure to make this more... tidy, I will enforce a colour-coding system for each sub-thread-guide-thingy, so you can instantly tell whether a guide or method to do something to your Yoga Book is risky, and most likely experimental, or is well tested. These will probably be done via experiments on my own Book (the wifi-only version), but of course I will hope via this community thread I will be able to provide more detailed statistics and such as everyone does their own thing to their device.
If you have anything to add to this thread, or would like to help out with anything; please feel free to contact me or just tell me what you're thinking - I'll do my best to read everyone's replies.
General Yoga Book Information
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
The SIM card is a Nano-SIM with 3G capability.
Other than that, all Yoga Book devices share the following specifications:
- 10.1 inch IPS display, of resolution 1920x1200
- Intel Atom x5-Z8550 processor, which:
----+ Has an architecture of x86_64
----+ Core base clock of 1.44 gigahertz
----+ Core boost clock of 2.4 gigahertz
----+ 4 cores and 4 threads
- Battery capacity of 8500 milliampere hours
- On-board storage of 64 gigabytes of solid-state storage (SSD)
- 4 gigabytes of random-access memory (RAM)
- A microSD card slot capable of up to 128 gigabytes of storage
- Two camera's, one above the display and one on the keyboard
- Wi-Fi (802.11 ac) and Bluetooth (v4)
- 3.5 millimetre headphone jack
- Micro-USB 2.0 OTG port
- Micro-HDMI port
Colour (or color) Codes and Tags:
For those who like using grey-scale display filters or whom are colour blind, I've added a "level" to each of them, where level 3 is like... crazy meltdown experimentation mode, and 1 is stable-ish (probably as stable as it'll get unless a REAL developer takes on the challenge).
[X] - Means that you will have to delete some or all of your data for it to work
[R] - Means that it requires a Rooted device
[Level 3] VERY EXPERIMENTAL - Use with caution, and with the knowledge that you may boot-loop, brick your device or lose your data!!! OR ALL OF THOSE THINGS!! Make sure to backup everything you hold dear, and just for good measure you'll have something to fallback on.
[Level 2] NOT WELL-TESTED - This will probably work for most people, but things may be unstable at the best of times. Again, make sure you have a backup before trying level 2 items.
[Level 1] 99% FINE - If there's an issue, it's probably your own fault... but again, I can't guarantee that everything I or anyone else does is perfect and will work for everyone! You should probably still have a backup, but if you're lazy like myself it's okay, I forgive you.
Android M/6.0
Rooting, backups, and more!
[1][X] Unlocking the Bootloader
earthCallingAngela wrote a really nice guide for unlocking the bootloader. The original thread is here, but for those who are too lazy to open the link in a new tab I've quoted the information.
IF YOU APPRECIATE THEIR EFFORTS GO AND THANK THEIR ORIGINAL POST!!!
Remember, unlocking your devices bootloader will format your storage (meaning you'll lose all of your data), so backup anything important before proceeding.
earthCallingAngela's OP: https://forum.xda-developers.com/yoga-book/how-to/how-to-unlock-bootloader-t3502216
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Click to expand...
Click to collapse
[3] TWRP Custom Recovery
danjac has written a post about his attempt at getting a modified version of TWRP running on his Yoga Book. From what I can tell it was a success, besides a few bugs (which are avoidable... I think).
WARNING! MAKE SURE YOU READ THESE!!
Before you go ahead and just flash his version, make sure you know the consequences that could arise if something goes wrong. If the recovery of your device screws up, you don't really have much to bring it back to life with. Even though there shouldn't be many things to worry about, it's still very risky.
In fact, it is recommended you ONLY temporarily boot into TWRP, instead of just flashing it like you would on another device. danjac's OP gives more information for you to use.
If you think you are willing to take the risk and know what you're doing, I highly suggest you make a complete backup of your device if possible. So far there isn't really a way to get your stock recovery back (since we don't have a custom ROM or a way to download Lenovo's modified version online).
danjac's OP: https://forum.xda-developers.com/yoga-book/development/recovery-twrp-t3533980
[2] Rooting (via Magisk)
danjac wrote the first guide to rooting the Yoga Book, and you should, again, go and thank his original post. However, his OP is now a bit outdated, Magisk (currently v12.0) now includes a root module (MagiskSU) based on phh's SuperUser.
Please note: If you are already rooted via a different method (and maybe you want to change because it didn't work... or something like that) you have to go into your super-user manager and uninstall it. If you have a previous version of Magisk installed, there is an uninstall ZIP that you can flash, which will remove any Magisk version, including MagiskSU. Again, more details on the main Magisk thread.
Do I NEED to unlock my bootloader to Root my device?
The short answer is yes, and the long answer is sort-of. You only need to unlock your bootloader if your ROM doesn't support Rooting out-of-the-box (which in Lenovo's case, it isn't supported). However, you can lock your bootloader afterwards if it's such a concern to you. Yeah, you probably will stop receiving over-the-air updates from Lenovo, but they're probably not going to push out another update for a long while, so in my opinion it's nothing to worry about.
Follow the instructions on the main Magisk page to install it if you're new to Magisk, but if you know a thing or two then I'll paraphrase:
- Flash the latest Magisk ZIP file via the TWRP Recovery (if you have it) or just flash it over ADB
- You should also download the Magisk Manager from the Play Store to make sure you're always up-to-date
danjac's OT: https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268
Magisk's main thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[2] Dual-booting Android and Windows 10
Since there isn't a place to get the Android side of things, I won't put too much info here.
Although if you're already running the Android version and want to know how to put Windows 10 on your device too, look at this thread.
Dual-booting OT: https://forum.xda-developers.com/yoga-book/help/android-to-windows-hack-dual-boot-option-t3475733
[3][X] Custom ROM
Currently there is no custom ROM which supports the Yoga Book, mainly for the simple fact not many people own the device. However, if we make enough noise in the community I'm sure someone will crack under the pressure ;P
Although, I'm doing my best efforts to merge the device drivers and such into the Android Source code, but you shouldn't get your hopes up. If I ever get it working, it will probably be unstable and not that great (I don't have much experience with the details of the Android OS), I'm running off my knowledge of the Linux OS.
If you're using the Windows 10 version of the Yoga Book (I'm sorry you paid the extra $50!!), hopefully Lenovo will at least release a version of their own ROM soon (or put it back from what I've heard). I've also heard that they're upgrading to Nougat in October (of 2017)... so we've got plenty of time to find another solution to our sorrows.
Information for Developers:
Someone has also posted a backup of their working Lenovo-customised Android OS, but I won't post a link here because:
- It's only a backup
- May draw un-wanted attention to the link
But if you're a developer and you think that will help you, you can easily find it somewhere in these forums.
EDIT: The link has now been removed (I can't find it)
If you're trying to
Code:
repo sync
the AOSP and you're getting stuck syncing the work tree, try doing this (from the folder you're trying to sync to):
Code:
rm -rf frameworks/compile/slang/
mkdir /home/<user>/slang_helper
sudo ln -s /home/<user>/slang_helper frameworks/compile/slang
Please be careful when typing commands into your terminal, especially from the internet, and especially when you don't understand what the commands are doing.
Lenovo's source code download: http://pcsupport.lenovo.com/au/en/products/tablets/yoga-series/yoga-book/za0v/downloads
[2] Linux without removing Android
Thanks to @Tiggi2017 for making the first guide. His OT here is a good one to read through if you're interested in this.
Via a few apps and some commands, you're able to have a "Linux" OS running on your Android device with the Halo Keyboard and such still working perfectly.
His original method doesn't need Root access apparently. However, there are other methods that may be easier for some people if they have a Rooted device. Look through the comments in that thread for more information.
OT: https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
Apps, tips and tricks!
[1] Apps That Support Multi-Window
Thanks to sashlon1138 for doing most of the hard work by putting this list together (may not be complete, if you know of more apps that work let me know so I can add them!).
Thanks to uuang for getting the ball rolling.
Thanks to Csilla4 for finding the first calculator app that works.
Thanks to docoli for also finding a huge list of compatible apps.
Csilla4:
- iDo Calculator
uuang:
- RAR
- Google Photos
sashlon1138:
- Chrome (but not beta)
- Facebook
- Messenger (Facebook)
- Gmail
- Outlook
- Youtube
- VLC
- Google Search
- Home
- Instagram
- Pinterest
- Dolphin Browser
- Ebay
- Paypal
- Flow Free
- Google Maps
- Google Earth
- OneNote
- Wikipedia
- ES File Manager
- Twitter
- Evernote
- Reddit
- Skype
- Candy Crush Saga
- Candy Crush Soda
- Candy Crush Jelly
- Spotify
- Soundcloud
- Opera
- Opera Mini
- Yahoo Mail
- Viber Messenger
- MX Player
- Google Translate
- Shazam
- AliExpress
- Tumblr
- Twitch
- Mega
docoli:
- Microsoft Word, Excel and Powerpoint
- Softmaker Textmaker HD, Planmaker HD and Presentations HD
- RealCalc
- Adobe Acrobat
- CamScanner
- MindjetMaps
- LinkedIn
- ezPDF Reader
- Detexify
- HERE WeGo
- Google Street View
- Öffi (German Public Transportation Schedule app)
- DB Navigator (German Railroad Schedule app)
- Kindle
- Amazon Prime Video
- Maxdome
- Barnes & Noble Nook
- Audible
- TuneIn Radio
- TED
- Babbel
- dict.cc. plus
- Amazon
- Nine (you can even have any number of items in parallel on the screen, e.g., inbox, calender, contacts, notes)
- OneDrive
Link to OT: https://forum.xda-developers.com/yoga-book/help/multi-window-apps-t3565253/post71494066#post71494066
[2] Changing the DPI
WARNING! Do not change your DPI to extreme values! You may render your device useless (unless you already have set up ADB and know how to revert the changes)!
Thanks to melando for bringing up the actual default DPI values.
Just so you are aware, if you're running Android 7 (Nougat) or later, you can adjust the "DPI" to some preset values from the settings app.
Using this site, I calculated that the Yoga Book has a technical DPI of 224 pixels per inch, with a resolution of 1920 by 1200 pixels, over a 10.1" screen (diagonal). However, the default Lenovo has set it to may be actually 280. They suggest that you may find it better if the DPI is set to 240.
This is a trivial modification if your device is Rooted. All you have to do is open the Play Store, and search for something along the lines of "DPI changer", and find an app that has good reviews.
An example app would be "Easy DPI Changer [Root]"
If your device does not have Root, then you will have to have a computer with ADB installed.
To install ADB, do a quick Google. There's bound to be a guide there somewhere (I'll put one here soon).
Once you have ADB installed, you can follow this easy guide to change your DPI to whatever you like.
DPI Calculator: http://dpi.lv/
Non-Root Method: http://www.androidbeat.com/2015/07/how-to-change-dpi-of-android-device-without-root/
[1] Recommended Apps...?
There isn't anything here as of yet, because I haven't gotten far enough to look for any good apps that work well with the Yoga Book. So right now I'm going to rely on everyone else for that. I'll get there eventually.
However, you should at least download Magisk Manager from the Play Store, to manage your Root and other neato Magisk features.
If you're a developer, and need guinea pigs to test your stuff on, I am happy to help anyway I can (and I'm sure much of the community is too).
If anyone needs help, I'll do my best to assist, but if it's anything too tedious (such as teaching you how TWRP works or something along those lines), you should probably have a look on the internet for tutorials and guides for that stuff. There are plenty of people out there who can explain concepts better than myself.
Windows 10
Simple customisations!
[1] Touch-pad Customiser
This program was first put into the spotlight by dinosauria123, so go to their original post and thank them for finding this.
This small program lets you modify some simple variables associated with your touch pad, only requiring a reboot after you change something.
Features:
- Setting extended right click area
- Setting unlock area
- Setting mouse pointer acceleration
- Setting scroll direction
- Disable Touchpad clicking (added in version 1.4)
Click to expand...
Click to collapse
OT: https://forum.xda-developers.com/yoga-book/themes/yoga-book-touch-pad-setting-application-t3569836
[1] Minor Halo KB Customisations
If you were wondering if there was a simple and easy way to lower the brightness of the Halo Keyboard, or just get rid of those pesky battery-draining touch vibrations for every key press, there is a way!!
Best of all, you don't have to download it! It's already installed!!
To find this not-so-well-hidden app, you have to either go to your Program Files, or open the good-old Control Panel (thanks to urayandro for pointing out that it's in the Control Panel!).
Control Panel method: Once you're in the Control Panel, just click on "Appearance and Personalisation", and you will find the "Halo Keyboard" program right at the bottom.
Program Files method: For 99.9% of people this is on your Local Drive (C: ). It may be located in your normal Program Files or it may be in your x86 Program Files, I'm assuming it depends on whether you're using the Windows 10 your device originally came with, or you have re-installed it (thanks to sawyerbenjamin for informing me that for them, it was in the normal Program Files folder). Assuming it's in your normal program files; go to Program Files/Lenovo/ and there it is. The application name is "ControlApp.exe". You can also make a shortcut to this application - I put a shortcut on my Desktop.
It allows you to:
- Toggle the touch tone/sound
- Toggle the vibration on keypress
- Adjust the time it takes for the keyboard lights to turn off
- Adjust the backlight (or whatever that is called) brightness for the whole keyboard
Risky or experimental customisations!
[2] Using AMIDuOS (Android Emu)
Update: I've spent a bit of time trying to use this, and in my opinion it's not worth the time. But if you need a development environment for something, it's pretty good at that. :/
In my attempt at replacing my Windows 10 installation with any version of Android I could find, I ran across this program called AMIDuOS. It's similar to emulating an Android system while you're in Windows, but instead of running it in a virtual environment, it runs directly on your x86 hardware (which is what the Yoga Book uses).
If you're cool with having a Windows 10 version of the Yoga Book, but still want to use some Android applications (possibly for drawing, or maybe just because the Android ecosystem is miles better compared to the Windows one) this may be a good solution for you.
Currently, they support Lollipop and Jellybean (not Marshmallow). However, this program is not free. You can trial it for free though. I'm fairly certain the full price is $10 USD.
It's not a difficult thing to set up (apparently), so if you wanna try something out and know how to deal with possible emulation problems (although unlikely) it may be worth it.
AMIDuOS Website: http://www.amiduos.com/
[2] Process Lasso
Huh? Process what-now? Yep, Process Lasso is a very complex program filled to the brim with algorithms tailored mainly towards getting the best performance and responsiveness, and to control those pesky rogue background processes that slow down your device when you don't need them to.
This program is completely free (but it does have a Pro version if you want a few extra customisation's and want to support the developers) and I've found it works pretty well, especially with a low-power device like the Yoga Book.
Since the Yoga Book is meant to be a very portable device, I'm not using Process Lasso to get maximum performance (as that would obviously drain the battery life quickly), I'm using it to make sure that if there's a program that needs to use power and deplete my battery life, then it's something I want - not some dodgy Windows background processes or other stuff like that.
It's pretty easy to set up. I've got a few of the main features enabled, and I recommend that you use similar settings.
I've enabled:
- ProBalance; this will keep the background processes in check, and allow the foreground processes to take the reigns of your CPU, insuring you experience minimal stutters.
- SmartTrim; this is an optional one, since I'm constantly micro-managing the applications I've got installed on my 64GB internal drive, this should help to prolong the performance of my drive, making sure it's well pruned (that's a pretty good analogy actually)
I've turned off the tray-icon showing me the CPU utilisation, so that doesn't need to waste any of my precious battery life (I'm usually a battery-life extremest), but you don't need to do that.
So if you're experiencing major delays when just doing simple things like moving around the Windows 10 user interface due to rogue background processes, I highly recommend you give this program a try.
Also, if you're a pro-ish-user like myself, feel free to dive deeper into the program. It's filled with toggles and adjustable's for you to play with and tailor the program to your needs, and almost everything you can change is accompanied with a tool-tip explaining what it does. Enjoy! But of course, as always, be careful of what you change - there are some things that could make your system really slow and or unstable.
P.S. The Yoga Book uses the 64-bit system, so choose that version of the program.
Website: https://bitsum.com/
Reserved
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Con_Sole said:
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Click to expand...
Click to collapse
I'm not entirely sure, however flashing something to your device (via TWRP at least) does require an unlocked bootloader. So without an unlocked bootloader, I don't think there's a way to install MagiskSU. Sorry about that... :/
I will have a look around and see what I can find, though.
Con_Sole said:
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Click to expand...
Click to collapse
So I've done more looking around and here is your answer: Yyyyeeeeaaaahhhhhh......?
Magisk itself does not require an unlocked bootloader, however, it does require root access. Usually to get root access you need to unlock your bootloader, unless it comes already rooted in a custom ROM (but in our case, it doesn't). Unlocking the bootloader is a relatively safe procedure to perform, so [in my opinion] you shouldn't have anything to worry about!
nan0s7 said:
[1] Minor Halo KB Customisations
If you were wondering if there was a simple and easy way to lower the brightness of the Halo Keyboard, or just get rid of those pesky battery-draining touch vibrations for every key press, there is a way!!
Best of all, you don't have to download it! It's already installed!!
To find this not-so-well-hidden app, you have to go to your Program Files. For 99.9% of people this is on your Local Drive (C. So to get to it, go to Program Files (x86)/Lenovo/ and there it is. Its very helpful and informative name is ControlApp.exe.
It allows you to:
- Toggle the touch tone/sound
- Toggle the vibration on keypress
- Adjust the time it takes for the keyboard lights to turn off
- Adjust the backlight (or whatever that is called) brightness for the whole keyboard
Click to expand...
Click to collapse
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
urayandro said:
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
Click to expand...
Click to collapse
Indeed it is! Consider that noted ;P
urayandro said:
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
Click to expand...
Click to collapse
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
sawyerbenjamin said:
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
Click to expand...
Click to collapse
Huh, well it must depend on whether you kept the original installation of Windows that came on the device, or whether you reinstalled it (or came from Android). I'll add that information. Thanks!
sawyerbenjamin said:
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
Click to expand...
Click to collapse
Same here. In my device is also only contain LenovoPaper under \Program Files (x86)\LenovoPaper
What i mean with retro control panel is old window's control panel. not the win10 setting. You can access it by:
1. Click start and type "control panel" then press enter.
2. You should see control panel window that similar to older version of windows.
3. Go to "Appearance and Personalization
4. Under there you should see "HaloKeyboard" shortcut.
You can also create another shortcut of this app by right-clicking it then choose create shortcut. Windows will make another shortcut on the desktop. I did this to get easier access when need to adjust keyboard brightness.
Hey there,
i think there is a way to flash the win 10 image on my yb1-x90f. just don't wont to brick it and so i have a few questions to all of you experts. in other words, i need your help
there is a quide i found in internet, which i think could work. But there are words i've never read before like "RUSB". is this an important word? i attached as low quality pdf...
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
maybe we can put together, 50/50 so its 25$ for me and you?
i think you know which page is meant. if not pm me
like descriped in the guide, (part 3) we have to select "Boot Menu" and after that "EFI USB Device"
But my bootloader looks different (android version).
is there a way to flash the image via original android bootloader/recovery or do we need to find a way to get into the other bootloader?
in this post: https://forum.xda-developers.com/yoga-book/help/bricked-yoga-book-yb1-x90l-t3537048
@mmusaad managed to get into this kind of "mode" but i think its a dangerous way and he had a big luck to "unbrick" his device. maybe onyone find an easy way to go into this "windows bootloader" or whatever?
so maybe we can work togehter
woodirk said:
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
Click to expand...
Click to collapse
Probably wrong translation from Chinese... Should read USB-R. There are USB Ports which don't support remote drives
woodirk said:
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
Click to expand...
Click to collapse
Windows was never free, that's why the Windows Yoga Book is $50 more expensive. A Win-Image will not help you either, as Lenovo brands the Product Key into the Bios.
jamespmi said:
Windows was never free, that's why the Windows Yoga Book is $50 more expensive. A Win-Image will not help you either, as Lenovo brands the Product Key into the Bios.
Click to expand...
Click to collapse
OMG sometimes i think "together" :highfive: is a heavy word... :crying:
what about this ? (see attachement)
and stop letting me look like an idiot...
I'm on the YB1-X91F, which is the Windows version. Unfortunately for us, the Android and Windows versions of the Yoga Book have totally different BIOS's. This is the main thing stopping us from being able to dual-boot.
Easy-firmware has both the Android and Windows' ROM's, but they only provide instructions on how to overwrite the current operating system, not the opposite ones. I have downloaded everything they have on the Android side of things, and everything except the Windows ROM on the Windows side.
While I was messing around with my device, I did brick it. But I was able to get an SD-card with a Windows bootable "USB" install on it, and went through the installation process on my external keyboard. Then from there was able to install the drivers and restore the Windows version with everything working after a bit of time. I don't know how different this would be if you don't mind getting rid of the Android bootloader totally, but that's not really recommended.
What we'd need for getting Android alongside the Windows version is a way to get a working Fastboot/ADB connection.
For the Android version getting Windows alongside it, you need a way to get the Android bootloader to point to and recognise the Windows installation. However, this is almost impossible unless you have a custom ROM, which we do not have that supports the Yoga Book. You could probably delete Android totally, and then install Windows from there, but I'm not 100% sure because I haven't messed around with the Android version of the tablet.
We'd need a way to get the Android BIOS and Fastboot off of it so we can then use it to our advantage.
nan0s7 said:
I have downloaded everything they have on the Android side of things, and everything except the Windows ROM on the Windows side.
Click to expand...
Click to collapse
that's good to know...
nan0s7 said:
You could probably delete Android totally, and then install Windows from there, but I'm not 100% sure because I haven't messed around with the Android version of the tablet.
Click to expand...
Click to collapse
this is exactly what i want to do and where i need your help
imo this will help us https://forum.xda-developers.com/showpost.php?p=70540959&postcount=7
woodirk said:
what about this ? (see attachement)
Click to expand...
Click to collapse
That probably flashes a valid Serial Number into the Bios...
DPI settings
I believe default DPI may actually be 280 - there's a Lenovo forum thread recommending setting it to 240 which I have found reduces the size of icons etc. so 224 does not seem right
melando said:
I believe default DPI may actually be 280 - there's a Lenovo forum thread recommending setting it to 240 which I have found reduces the size of icons etc. so 224 does not seem right
Click to expand...
Click to collapse
Thanks for the information! I've added a bit to the DPI section about the other values.
nan0s7 said:
Thanks for the information! I've added a bit to the DPI section about the other values.
Click to expand...
Click to collapse
However now that the Nougat update is out some adjustments can be made in Display Settings...
melando said:
However now that the Nougat update is out some adjustments can be made in Display Settings...
Click to expand...
Click to collapse
Oh yeah forgot that happened (I'm on the Windows version). Fixed it now!
Related
Hi all,
I've learned that the StarTrek is able to boot the current kernel from the Linwizard project without any modifications. I've posted a video of this at http://vimeo.com/2114567. Before you get too excited, however, there's a few things to keep in mind:
The buttons aren't mapped correctly by default.
You need a networked computer to log in and do anything fun, for now.
If you're wondering about Android, the answer is "not yet".
I will do my best to address the important things here; what works, what needs tweaks to work, and (most of all) what needs attention. I will also, over the next day or two, try to post my findings regarding the button GPIOs collected from HaRET, kernel modifications necessary to fix a few things. etc.
Consider this post a call for help. I'm hoping this will encourage others to contribute toward more complete linux support on the phone. I personally am driven by the opportunity to dual-boot Android on the device, but I have much to learn and can't do this alone. So, if you have kernel experience and a StarTrek, here's your motivation to get hacking! (If you'd like to help, but don't have a device to test kernels on, I'm often in #xda-devs.)
Status (Let me know if there's anything missing here.)
Internal LCD - YES - Seems to work great.
External LCD - ? - Shows the device's default image. Not sure how to control this in linux.
Backlight - ? - Unsure. As far as I can tell, Linux will retain the brightness level being used when HaRET finished loading the kernel.
USB Networking - YES - Works like a charm.
Audio - ? - No idea. I don't know how to test this.
Cellular - ? - No idea, but I don't think it will necessarily come easily.
Buttons/Keypad - SOME - By default, the keys and buttons are mapped either incorrectly or not at all. The phone keypad and some of the special buttons type random keystrokes, since we are using the mappings for the Wizard. I have a modified board-htcwizard.c with correct mappings for the StarTrek I'll post really soon, as well as a list of the GPIO readings for many of the buttons. Unfortunately, the Up/Down/Left/Right/Select/End buttons function differently than the other, matrix-based keys. I have yet to discover how to configure them.
Camera - ? - No idea, but they don't even have this working on the Wizard (Linwizard's primary target device).
Light Sensor - ? - I wouldn't know where to begin. It barely works in WM, anyway.
MicroSD - YES - I can mount the MicroSD with no issues, full read/write. Even managed to open my photos in the GPE photo gallery on the device (launched over telnet).
X[\B] - YES - I am able to start X, by calling startx over the telnet connection. However, X will try to run a touch screen calibration before doing anything else, and this is a bit of a problem for us! Fortunately, on newer Linwizard versions, you can disable this by passing tslib=0 to the kernel (in the defaults.txt file you give to HaRET). GPE also seems to be running perfectly after X starts.
Problems - After a few idle minutes in linux, the screen likes to black itself out automatically, as per the design of Linwizard. Unfortunately, on the Star Trek, there seems to be no way to make the screen wake up. Telnet still works in this situation.
I promise to keep this post updated, and get my data together and uploaded soon. Please share your own results and tricks as they come along, and join me (and some talented people) in #xda-xevs and #htc-linux on irc.freenode.net. Happy hacking!
Attached:
arch/arm/mach-omap1/board-htcwizard.c - Contains key matrix mappings modified for StarTrek. Be sure to remove the ".txt" from the file extension before using.
default.txt - Used with HaRET to make Linux boot. The only thing unusual in here is the TSLIB=0 option that's passed to the kernel, telling linux to skip touchscreen-related tasks.
great work! but you need some advanced startrek owners to test linux - that's a big problem
Fantastic news! I' would really try it out. Unfortunatly my startrek's connector is damaged. I can charge the device, but I cannot connect with the pc. If I can use the micro sd card to install it(I think is possible) I will try it.
Thanks for the great job.
dancer_69 said:
Fantastic news! I' would really try it out. Unfortunatly my startrek's connector is damaged. I can charge the device, but I cannot connect with the pc. If I can use the micro sd card to install it(I think is possible) I will try it.
Thanks for the great job.
Click to expand...
Click to collapse
You can, by dropping Haret+default.txt+zImage+initrd onto the SD card. Unfortunately, without a USB connection, you won't be able to telnet into the device and run commands.
very interesting! Ive been waiting to hear this kind of news Unfortunately, I still use my StarTrek as my primary phone, so I can't test it out until it moves along a little further. I'll be sure to keep an eye on this thread, as this is good news!
gigawatts said:
very interesting! Ive been waiting to hear this kind of news Unfortunately, I still use my StarTrek as my primary phone, so I can't test it out until it moves along a little further. I'll be sure to keep an eye on this thread, as this is good news!
Click to expand...
Click to collapse
Linux actually boots directly from a Windows Mobile program called HaRET; When you're done playing with Linux, you can just reset the phone and you're back to normal. No permanent changes.
awesome! I'll give it a go right now, thanks!
BHSPitMonkey said:
You can, by dropping Haret+default.txt+zImage+initrd onto the SD card. Unfortunately, without a USB connection, you won't be able to telnet into the device and run commands.
Click to expand...
Click to collapse
I already did it, and works. Thanks anyway.
Why not combine the effort to get Android on it?
Kwen said:
Why not combine the effort to get Android on it?
Click to expand...
Click to collapse
Are you volunteering your expertise on the subject?
The point of this post was to accomplish just that: to attract the interest of more people who can contribute. I'm in the process of setting up a repository of changes right now, so the patches I've made so far are kind of scattered about my hard drive for the moment. If you're interested, you can try catch me in #htc-linux or #xda-devs on irc.freenode.com. Otherwise, I'm trying to keep the post at the top of this thread up-to-date.
Unfortunatly Android cant work, it needs 128 ram.
http://source.android.com/release-features
BHSPitMonkey said:
Cellular - ? - No idea, but I don't think it will necessarily come easily.
Click to expand...
Click to collapse
from linwizard wiki page :
What we need
Right now we need people with experience with GSM and WiFI to help get linwizard connectivity up!
Click to expand...
Click to collapse
about two years ago , another linux project ran that called Xanadux. why you don't use from Xanadux ?
sorry for my english !
I have linux booting
it up booting to the point correctly then sit conclusion cannot one yet start?
sorry for my bad english my german are better
Oh.......I think HTC Phone can do that ADIDAS ' AD "impossible is nothing"
Been a few months since ive been on the scene, any news here? My Cingular 3125 is nearing the end of its life, and I figured I can play a bit more with it
P.S. Whats new BHSP?
autologin on linwizard
hi
http://wlcrck.wl.funpic.org/wlcrck-elf-linux/autologin
to solve the problem i develop a simple aplication to automatic login but dont have any security autologin in root mode
to use this have to make a couple of things
you need decompress the inirtd and add this app to /bin and set suid and modify
/etc/inittab file and compress the initrd again.
change this line
tty1::respawn:/sbin/getty 38400 tty1
for
tty1::respawn:/sbin/getty -l /bin/autlogin 38400 tty1
sorry for my english
thanks for the code of htc board
After weeks of hard work we (Setmov and uncle Fab) proudly present you the first Una ROM for the galaxy Grand 2 I7102, based on 4.3 XXUANG4.
DISCLAIMER
As usual, your phone your responsability, we won't take any responsability if it flies out of the window or if your girlfriend/boyfriend runs away with it.
PLEASE, DO READ OP COMPLETELY AND CAREFULLY BEFORE ASKING ANY QUESTIONS, ANSWERS TO MOST PROBLEMS ARE THERE
WHAT IS UNA?
Una is a new concept that takes security to a new level.
Are you tired of seeing so much blatant, outrageous and shameless invasion of your privacy and data mining hidden behind nice sentences like "enhanced use experience" or "complete integration with the system"? We decided to develop secure ROMs where privacy means just that – Private!.
It’s free of charge, we are a non profit structure and we are not here to make big bucks
WHAT UNA ISN'T
UNA isn't a way to help you to stealthily buy massive destruction weapons to foment a coup d'etat in your favorite banana republic or to prepare the third world war.
UNA secures what leaves from your phone (ie your personnal data doesn't leak and no app can look over your shoulder to spy your activities), but it can't completely secure what comes into your phone.
Why is that?
Because it's just not possible to fully secure a phone from what comes into it, and anyone claiming to be able to do it is either a liar, or an ignorant, or both.
There are too many attacks, some not well documented, if documented at all, and some unknown to the public, and there are too many ways to hack a phone, especially if the user doesn't use his/her common sense.
If you are the type of person that installs apps from shaddy source and/or warez web sites (sites offering cracked paid apps) chances are that at some point you will unknowingly install a malware or a spyware. The same applies if you click on any link, specially on SMS' and emails, if you let any pop out window appear or if you don't protect your lockscreen with a password/pin/pattern and let anyone get physical access to your phone.
A bit of judgment and common sense can save you a lot of trouble, but there's unfortunately nothing UNA can do about it.
Then, if you use your phone to call through GSM your provider will know where you are. If he didn't you wouldn't be able to make any call, the signal has to find you and there's nothing UNA or anyone can do about it.
The only way to prevent that is to disable the phone functions (but then your phone will turn into a wifi only device) and reenable them when needed, head to the scripts section to learn how to do it.
Last but not least, bear in mind that the agencies have armies of tech savvy henchmen and 10 storeys computers, and tricks we can't even imagine, so think twice and use your brain before you attempt to outsmart them...
UNA IS FOR YOU IF:
. You are willing to learn how to use an unconventional ROM and generally speaking to understand how things work, even if it sometimes requires a little effort to fix this or that little problem (bear in mind that it took us a lot of work to develop Una to where it is now),
. You don't mind a few little occasional bugs here and there that come from all the restrictions the ROM contains,
. You want to take back ownership of your phone from google’s claws.
UNA IS NOT FOR YOU IF:
. All that you care about is the latest gimmick in the latest OS,
. You can't live without the google’s apps,
. You are the kind of person that never reads through the OP and only scroll down to the download section, and then complain that things don't work and/or ask stupid questions that have already been answered in OP.
An example? One guy makes a mod and writes clearly in OP that it's specifically for 4.2.2. Then some people complain: "it doesn't work on 4.4.2"...
ARE WE PARANOID TIN FOIL HATS? OR TERRORISTS? OR CARTEL BOSSES?
Nope, we only are people that don't see why we shouldn't be in control of our phones. Or why our phones can be wiped remotely, why apps or updates or who knows what can be downloaded and installed without asking for our consent, why SMS' can be sent without us to know, why we should pay for the bandwidth used for data mining and unwanted downloads, and why all those activities should deplete our battery and kill our RAM.
You think we are overreacting here?
You don't have to take our word for it, just download and install Network Log from here:
https://f-droid.org/repository/browse/?fdfilter=network+log&fdid=com.googlecode.networklog
Give it root permission, start logging and open some web pages. Come back to Network Log after a few minutes and see for yourself, you'll be surprised (or maybe horrified?) to find out that your android system, your settings, your kernel etc. connect to all sorts of funny IPs, including and foremost google’s.
Now you see what we mean?
It's time to go for Una
UNA'S FEATURES
. Rooted.
. Deodexed.
. Zipaligned.
. Busybox and sqlite installed.
. Init.d support and scripts.
. Auto start disabled for most apps.
. About 120 system apps, 40 framework jars, 30 permissions xmls and 25 libs removed, plus files here and there.
. Very low RAM and CPU consumption, more than 8 hours screen time with the WIFI on, 1% battery decrease every 10-12 hours while in stand by.
. Heavily and extensively modified system, in order to make it secure and prevent it from leaking your data.
. App Settings, Firewall and Xprivacy built-in, and already applied out of the box to make sure you are well protected.
. Xprivacy is a fantastic tool but it has one big limitation, it can't restrict the Android System from accessing your serial numbers and leaking it. For that reason these IDs have been edited as follows:
build.serial (androidboot.serialno), ro.boot.serialno and ro.serialno are both set to "1",
android id is set to "id",
net.hostname is set to "1".
. Wlan serial number set to "00000001" (this number identifies you everytime you connect to the internet, and Xprivacy can't do anything about it).
. USB ID (iSerial) set to 1.
. Unreadable cp access.
. Vulnerabilities patched thanks to Master Key Multi Fix.
. ADB disabled (can be re-enabled, see below).
. By default ADB, all google access (including youtube, blogspot and google search), the Live Wallpaper Picker and the Media Storage are disabled. You can re-enable some or all of them, instructions are in the "HOW TO USE THE ROM" section.
. Plenty of under the hood modifications to make the ROM fast and fluid.
. Multi-purpose navigation keys.
. Call button in contacts.
. Because secure doesn't mean ugly, the whole ROM has been themed with a beautiful green color (if there are enough requests other themes will follow), transparency, and Lollipop HD wallpapers.
. Multiwindows have been revamped, they are no longer only static in Samsung style but now they can float and be resized/minimized too, like on a computer.
. All apps can be opened in floating mode.
. KK style quad view multiwindows.
. Heaps of hand picked and carefully scrutinized open source apps.
There are 2 non open source apps (Greenify and Quick Pic) but they are safe, believe me, I have thoroughly examined them. Still, you can always uninstall them if you feel like it.
In time we will develop our own apps, but first we want to see how people respond to the Una concept...
Installed apps/tools
. 920 Editor, to create and edit scripts or text files.
. AF+ Firewall.
. Alarm clock.
. APG, to encrypt messages.
. App Settings, to restrict apps' permissions, change DPI on a per app basis and more.
. Arity, a calcultor.
. Conversations, a secure and encrypted chat, modded by uncle Fab for increased security.
. Fdroid, an alternative to the Play Store, and all the apps are open source!
. Floating stickies, to make small notes on the fly.
. FTP Server, to copy files to/from your phone wirelessly.
. Ghost Commander, a very powerful dual panel root file manager.
. Gravity Box, a theming engine.
. Greenify, to make apps behave by hibernating them when not in use.
. K9 Mail, an email client.
. Kernel Adiutor, if you feel like playing with kernel tweaks (but you have to know what you are doing).
. Lightning, a fast and light weight browser.
. Master Key Multi Fix, a patch to some vulnerabilities.
. Network Log, to check where your apps connect and chase unwanted connections.
. Open Camera.
. Tor (Orbot) for Android, modded by uncle Fab for increased security.
. OS Monitor, to monitor and kill your phone's processes, and more.
. Pale Moon, based on Firefox for Android, for a full desktop experience with Mozilla add-ons preinstalled for enhanced security.
. PDF Reader.
. Preferences Manager, to edit the otherwise difficult to read shared_prefs files in data/data.
. Quick Dic, a good selection of free dictionaries.
. Quick Pic, a Gallery app.
. Rmaps, a maps app where you can download maps from various sources for offline use.
. Search Light, a torch.
. Terminal Emulator, fire up your commands and show your phone who is the boss!
. Text Secure, a secure and encrypted SMS app, modded by uncle Fab for increased security.
. Tint Browser, another fast web browser.
. Urecord, to record sounds with different sample rates.
. USB Mass Storage Enabler, to connect your phone to any computer (note that it only mounts the external SD).
. Viper4Android FX, a powerful sound enhancer.
. Viper4Android XHiFi, some more sound enhancements.
. VLC, a video and music player favourite.
. WI-Fi Privacy Police, to secure your connections even better than they already are.
. Xposed Installer, a great framework that enables apps like App Settings or Xprivacy to work.
. Xprivacy, last but not least, the best privacy app.
WHY DO WE USE A 4.3 ROM AS BASE INSTEAD OF THE LATEST 4.4.2?
Because when it comes to privacy Kit Kat 4.4.x is a complete
disaster, the newer the android version the more buit-in spying there is (and the more difficult it is to remove it), despite google's sweet talk about "enhanced user's experience.
Lollipop seems to be even worse, but that's another story.
INSTALLATION
As usual, make a backup first!
Do backup your contacts and whatever is important because all your apps and data will be erased (your sd card contents won't be deleted though).
Do backup your /system/csc folder, in case you need it for later.
Do backup your efs folder (VERY IMPORTANT).
Open an android terminal from your phone and type:
su
enter, then type:
busybox dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.img
enter, this will create an efs backup caled efs.img in your sd card.
To restore it, first make sure the efs.img is in your internal sd card, then type:
su
enter, then type:
busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p11
enter, your efs will be restored in no time.
If that sounds like too much work you can use the scripts provided to backup/restore your efs, instructions are in the scripts section.
To install the ROM you need a Custom Recovery and Philz' comes highly recommended.
We chose Philz since AFAIK it's the only one that allows you to lock you recovery with a password (if your recovery is not password protected it wouldn't take more than 2 minutes for someone to disable your pattern or pin protected lockscreen and access all your personal data on the phone).
I'm not sure whether there's a Philz recovery or not for the Grand 2, if there isn't then CWM or TWRP will do.
Custom recovery installation instructions
You need to have Samsung drivers installed.
Boot your phone into download mode (press volume down and power at the same time).
Open Odin 3.07 and connect your phone.
Click on the PDA slot, navigate to where the Custom Recovery is located and select it.
DOUBLE CHECK AND MAKE SURE THAT "RE-PARTITION" IS UNTICKED (only "Auto Reboot" and "F.Reset Time" should be selected).
Click start and wait while Odin flashes the Recovery.
If everything went well your phone will now auto-reboot into the system. Go into recovery, you should see your brand new Custom Recovery.
If you are still on stock recovery then repeat the above steps, but this time untick “Auto Reboot” in Odin.
When in recovery, if before you reboot you see a text on the screen displaying “yes – disable flash recovery”, select it to avoid stock recovery overwriting the Custom Recovery.
Download Una for Grand 2 from here (click on the menu at the top right and go to the download section):
http://unaos.com
Unzip the ROM and copy it to the backup folder that is inside the clockworkmod folder in your sd card (if there's no backup folder create it by choosing "mkdir" in Ghost Commander).
Boot into recovery.
Go to restore from sdcard, choose 1970-01-01.10.06.02, and go for it!
IMPORTANT!!!
If you are on Kit Kat (4.4.2) you must downgrade first to stock 4.3 before you attempt to install Una ROM, otherwise you may end up with a bricked phone.
Here are 2 threads to assist you in the downgrading process:
http://forum.xda-developers.com/galaxy-grand-2/general/how-to-downgrade-galaxy-grand-2-sm-t2857767
http://forum.xda-developers.com/galaxy-grand-2/help/downgrade-to-4-3-t2857183
If it works please report here so that other people will know, thanks in advance!
Once it's done reboot, congratulations, you have installed Una ROM on your phone!
HOW TO USE THE ROM
. Swipe down to access the applications drawer.
. Swipe up to turn off the screen.
. Go to settings and set a stong password/pin/pattern protected lockscreen (recommended).
. Go in recovery and set a recovery password (recommended).
. Long pressing on the menu key toggles expanded desktop (full screen, no more navigation bar and no more status bar).
. Double pressing the menu key kills and hibernates the current application.
. Long pressing the recent key brings you back to the last application (convenient to switch from one app to another).
. Between the home and the back key there's a supplementary key that can display up to 12 apps (editable in gravity box).
Double pressing that key shows the sound panel, long pressing it shows the reboot menu (note that there's an option to take screenshots in the reboot menu).
. You can open an app in full screen mode by dragging it from the Flash Bar (the side bar), then you can drag and add more windows to the view (up to 4 on the same screen).
Or, you can open apps in resizable and movable floating mode by clicking on them (double tapping the top bar minimizes them into a bubble, double tapping the bubble restores them).
. Go to /system/etc/security/cacerts, check the certificates that are there (you'll find the certificate's name approximately by the middle of the file), and erase the ones you don't need/like.
When you want to transfer files to/from your phone open the USB Mass Storage Enabler app and enable mass storage, that's it. When you are done, don't forget to eject your phone from the computer and to reenable MTP from the app.
. When you install a new application, by default it will be fully restricted in both Xprivacy and the Firewall.
Before you open the newly installed app wait until the Xprivacy icon appears in the status bar, then and only then can you open it.
Most likely the app will crash.
Go to Xprivacy, open its settings and then usage data, you will see what restrictions caused the crash. Re enable some, provided that they are not too invasive.
Many apps require "load.Library" to be allowed in the shell section, that's ok.
Others may need to access the sd card, that's in the storage section and it's ok to allow it for apps that really need to access the storage, like players, cameras or file managers (for other apps try to keep it restricted).
Root apps obviously need "su" and/or 'sh", and sometimes "exec", in the shell section.
Always try to enable as few fields as possible, and bear in mind that data requested by an app is not necessarily needed for that app to work (especially true for identification, internet and mcc/mmc access).
Lastly, give the app internet access in the Firewall if, and only if, it needs it, and restrict some more permissions in App Settings.
If you can't tame the app consider uninstalling it and look for a similar one that has less built-in spyware.
SCRIPTS
. As said above, by default ADB, all google access (including youtube, blogspot and google search), the Live Wallpaper Picker and the Media Storage are disabled.
If you want to re-enable some or all of them, open the script folder located in system/etc.
Click on the desired script and choose edit.
Copy the whole text and paste it into the Android Terminal, voila, the script is automagically executed.
. You will see more scripts to disable/enable the Bluetooth, the FM Radio and the Phone.
If you disable the Phone and later want to re-enable it do as follows:
untick App Settings in Xposed's modules section, re-enable Phone, reboot, then enable App Settings again.
. Some scripts will enable you to backup/restore your efs partition and flash a recovery.img (to restore or flash an .img, make sure it's in your internal sd and execute the script).
. Other scripts can enable/disable am and pm, but don't play with it unless you know what you're doing.
. You can uninstall the Live Wallpaper Picker, the Wallpaper Chooser and the Media Storage if you want, or keep them disabled and resurrect them when needed.
. If you are very privacy concerned you should consider using the "uncle's phone lite" mod because it enables you to call with only the Phone and the Telephony Provider apps (CSC, Contacts, Contacts Storage, Logs Provider and STK are completely de-activated). That's the method I use to make calls, but you have to know that the dialler forces close after you complete the call (not a big deal in my opinion but still, I may look into it one of these days). You'll find the mod in the add-ons section.
ENCRYPTION
If encryption is your thing we have you covered with the following installed apps:
APG, Conversations, K9 Mail and Text Secure.
BUGS
. Quick Dic won't download any dictionary, actually it's not a bug but a Una restriction since Quick Dic downloads from a google owned web site.
If you need to download dictionaries, temporarly enable google by running the "enable_google" script (don't forget to disable it again when you're done). After you've run the script go to the firewall, open its settings, go to "Set custom script" and click "OK" (do the same if you decide to disable again google's stuff).
. For some reason the ADW Launcher doesn't allow transparency in the navigation bars while in portrait, I'm working on that.
. You can't download anything from Lightning and Tint Browser, that's because the Download Manager and the Download UI have been uninstalled. If you need to download something, copy the link and paste it in Pale Moon, it has its own download engine.
. I didn't have time to properly and restrictively set Text Secure (the SMS app), because I don't own this phone and the person I borrowed it from wanted it back ASAP. Sorry about that, you'll have to do it on your own (if you want to make it simple just restrict its internet access).
. All the installed apps work, but other apps you install may crash. I call that kind of apps "google’s henchmen", they only work if the play store services or the bla bla app are installed and of course they won't on Una since all that garbage has been removed.
If I install your app, why do you want to force me to install your boss' app too? Forget about those apps and search Fdroid, you'll find what you need...
. Depending the way you use your phone you may have to fine tune Xprivacy and reenable some permissions, I'm sorry for the inconvenience but it's impossible to set Xprivacy for all users since we all have different ways to use our phone.
ADD-ONS
. Sony Xperia Keyboard, flash it in recovery.
Credits KristianCarl for porting it, and unclefab for theming it in green.
It's not open source and that's why it's not included in the rom by default, but it's my every day keyboard because it works fine and because I themed it to make it look nice.
Don't give it internet access in the Firewall.
In Xprivacy, only allow "loadLibrary" in the shell section. You may have to enable a few fields in the contacts section depending your phone's configuration.
In App Settings, restrict "Read_Phone_State" and "Record_Audio".
I removed the Chinese Keyboard, tell me if you want it and I'll readd it.
. Universe Wallpapers
If there are enough users' requests then I'll upload the following:
. Uncle's phone lite (with clipboard and dialer) for hardcore users. It's safer than using the regular phone configuration, but the dialer forces close when you hang up the call. Flash it in recovery, wipe dalvik-cache, reboot.
. Completely disable internet access for the Android System. Lightning and Tint Browser won't connect anymore since they use the same web engine as the Android System, but Pale Moon still works thanks to its build-in web engine. Flash it in recovery, wipe dalvik-cache, reboot.
RECOMMENDED NON OPEN SOURCE APPS
. Pri-fy, from chainfire the root master:
http://forum.xda-developers.com/showthread.php?t=2631512
. Logging Test:
http://androidsecuritytest.com/
UPDATES?
I'm working on some improvements on kernel and system level to make Una even more secure, but I will release them for the Grand 2 if, and only if, there are enough users' feedback for the current version, because it's a lot of work to implement such stuff in a ROM.
No ETA though, you'll have to be patient because now we have to design and release Una for many other phones.
Still, any suggestions/comments/bug reports are welcome, help us to improve Una!
FEATURE REQUESTS
Yeah, sure, we'll see what we can do but we don't promise anything
SCREENSHOTS
I didn't have time to make screenshots since I ran short of time, so the ones you'll see here come from another phone.
They are very similar in shape, layout and color though, and you'll get the idea.
That's all for now, enjoy the ROM!!!
The Una team
CREDITS
Big thanks to:
F-Droid
M66B (Xprivacy)
Rovo89 (Xposed)
Tungstwenty (App Settings, Master Key Multi Fix)
Ukanth (AF+Firewall)
Jecelyin (920 Editor)
Kraigsandroid (Alarm Klock)
Thialfihar (APG)
Arity (Arity calculator)
Siacs (Conversations)
Ppareit (FTP)
Ghost Squared (Ghost Commander File manager)
Mohammad Adib (Floating Stickies)
C3C076(Gravity Box)
Oasisfeng (Greenify)
K-9 Dog Walkers (K9 Mail)
Grarak (Kernel Adiutor)
Anthonycr (Lightning)
Xperiacle (Multiwindows Manager)
Pragmatic Software (Network Log)
Mdwh2(Open Camera)
The Guardian Project (Orbot)
Eolwral (OS Monitor)
Moon Child and Cyansmoker (Pale Moon)
Droidapps (PDF Reader)
Simon Marquis (Preferences Manager)
Thad Hughes (Quick Dic)
Q-Supreme team (Quick Pic)
Robert.Developer (Rmaps)
Search Light (Search Light)
Jackpal (Terminal Emulator)
Anasthase (Tint Browser And Tint Browser Adblock Addon)
Thomasebell (Urecord)
Mohammad Abu-Garbeyyeh (USB Mass Storage Enabler)
Zhuhang (Viper4Android FX and Viper4Android XHiFi)
Videolan.org (VLC)
Brambonne (Wi-Fi Privacy Police)
i dont own a galaxy grand 2 , although i may have to get one , but thank you for sharing your work. i'm not a developer so i can only imagine ( which probably falls way short ) of what this took to build.:thumbsup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Please do a 4.4.4/4.4.2 version. What about the security? Like anyone can hack into your phone....
salimtn said:
4.3 ?! Not interrested
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Laurisss said:
Please do a 4.4.4/4.4.2 version. What about the security? Like anyone can hack into your phone....
Click to expand...
Click to collapse
Thank you for your useful feedbacks.
PLEASE, DO READ OP COMPLETELY AND CAREFULLY BEFORE ASKING ANY QUESTIONS, ANSWERS TO MOST PROBLEMS ARE THERE
WHY DO WE USE A 4.3 ROM AS BASE INSTEAD OF THE LATEST 4.4.2?
Because when it comes to privacy Kit Kat 4.4.x is a complete disaster, the newer the android version the more buit-in spying there is (and the more difficult it is to remove it), despite google's sweet talk about "enhanced user's experience.
Lollipop seems to be even worse, but that's another story.
And NO, not anyone can hack into your phone, but many can and google already did it!
salimtn said:
4.3 ?! Not interrested
Click to expand...
Click to collapse
Thank you soooooo much to take time to reply and show how much consideration and respect you have for someone that worked about 100 hours to build a rom and share it for free with the community.
It feels sad to know that you won t run Una rom on your phone, and thanks again for informing us that we won t count such a great person like you amongst our users, but maybe next time you should read OP:
UNA IS NOT FOR YOU IF:
. All that you care about is the latest gimmick in the latest OS,
. You can't live without the google’s apps,
. You are the kind of person that never reads through the OP and only scroll down to the download section, and then complain that things don't work and/or ask stupid questions that have already been answered in OP.
Click to expand...
Click to collapse
You see guys?
It s thanks to that kind of person that so many devs have left, leave, or will leave the forum...
Please do a 4.4.4/4.4.2 version
Click to expand...
Click to collapse
As written in OP there might be updates:
I'm working on some improvements on kernel and system level to make Una even more secure, but I will release them for the Grand 2 if, and only if, there are enough users' feedback for the current version, because it's a lot of work to implement such stuff in a ROM.
Click to expand...
Click to collapse
Well, time will tell, but so far if you were me what would you think/do?
Thanks for your valient efforts.
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
salimtn said:
4.3 and a cute dev. ?! Still not interested ...
Click to expand...
Click to collapse
Still not interested?
Such a pity, people like you are every devs' dream and it would have been a real honour to count such a VIP like you amongst our users.
Thanks for letting us know, next time we ll try to do our best to satisfy demanding users like you...
wrishaba said:
Thanks for your valient efforts.
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
Click to expand...
Click to collapse
Thank you for your support. With this attitude you are definitely repaying every effort made.
wrishaba said:
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
Click to expand...
Click to collapse
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
unclefab said:
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
Click to expand...
Click to collapse
spying? Meh. 80% of people are on kitkat and a few are on lollipop. No reports of something hack-ish.
Laurisss said:
spying? Meh. 80% of people are on kitkat and a few are on lollipop. No reports of something hack-ish.
Click to expand...
Click to collapse
Most people don t realise they are being spyied.
Do one test.
Download network log from here:
https://f-droid.org/repository/browse/?fdfilter=network+log&fdid=com.googlecode.networklog
Install it, open it, give it root access and start logging by clicking "logging on" on the top.
Then do some browsing, going to this or that site, but don t go to any google related web site (no search, no youtube etc.).
Come back to network log, you will see that your phone connected to many funny addresses, including of course google, and that quite a lot of data has been transfered both inbound and outbound.
That s just a small test, there s actually much more than that but you ll get the idea.
You could make another test with xprivacy, and if you do so you ll see that all apps request various private data like ids and cell towers location.
The thing is that the higher the android version the more difficult it is to prevent that data mining, data mining that is little more than spying by looking over your shoulder.
Una roms have been designed to prevent that, and more (see OP), but it s up to everybody to install it or not.
I really appreciate your Hard work , I can imagine how much hard work you would have done by working on a phone which you do not own , borrowing it again and again , testing the ROM on someone else's phone and the fear of bricking it . But as someone mentioned in the thread many users are on 4.4 . Many here fear bricking there devices while downgrading it. The mere fact that you have to downgrade your device to use the ROM is what cause of lack of users . personally I really liked what your ROM offers. Just to help you for further development H6 is the most stable and without Knox count firmware. Some 60-70 % users who flash custom ROM are on this firmware and even many custom Roms use it as a base . Hope to see this ROM on kk .
Best of luck.
unclefab said:
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
Click to expand...
Click to collapse
Definitely I wanna going to try this rom. I never said 4.4. Or 5 is best versions of android.
But the fact is downgrading is some what risky. Eben then I am going to try.
No need to pay me for taking sweet.
wrishaba said:
Definitely I wanna going to try this rom. I never said 4.4. Or 5 is best versions of android.
But the fact is downgrading is some what risky. Eben then I am going to try.
No need to pay me for taking sweet.
Click to expand...
Click to collapse
I didn t read everything about the downgrade procedure, but of what I have read you have to odin flash a specific KK version first, and then a specific 4.3.
Anyway, if it s really that risky maybe you shouldn t try and wait until we manage to release a 4.4 Una rom.
The problem is that the person that owns that phone uses it for business purposes, so I have to be very careful not to loose all the whatsapp, bbm etc. contacts and settings, and if it was ok to backup her rom, work on making una during nights and then restoring her original rom in the early morning, it would be a different story to switch from 4.3 to 4.4 to again 4.3 every night...
Let s see if I can convince her to use 4.4 as her daily rom, but I can t lie and tell her that 4.4 is better than 4.3, and I don t think she will accept to sacrifice her phone.
I meet her again next month and I ll keep you informed in case she accepts.
For now what you can do if you want to make your phone more private and secure is to follow what I explain in my security thread (check my signature "how to secure your phone").
unclefab said:
I didn t read everything about the downgrade procedure, but of what I have read you have to odin flash a specific KK version first, and then a specific 4.3.
Anyway, if it s really that risky maybe you shouldn t try and wait until we manage to release a 4.4 Una rom.
The problem is that the person that owns that phone uses it for business purposes, so I have to be very careful not to loose all the whatsapp, bbm etc. contacts and settings, and if it was ok to backup her rom, work on making una during nights and then restoring her original rom in the early morning, it would be a different story to switch from 4.3 to 4.4 to again 4.3 every night...
Let s see if I can convince her to use 4.4 as her daily rom, but I can t lie and tell her that 4.4 is better than 4.3, and I don t think she will accept to sacrifice her phone.
I meet her again next month and I ll keep you informed in case she accepts.
For now what you can do if you want to make your phone more private and secure is to follow what I explain in my security thread (check my signature "how to secure your phone").
Click to expand...
Click to collapse
All builds prior to NK1 are without KNOX.
NH6 is good and speedy.
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Also, the screenshots are from a Grand 1, and our device is SM-G7102, not I7102. You mixed up with the Grand 1 i9082.
Oah you know, customers is maybe not the right word, unless they pay which is not the case!
Then I don t know if that can be called a vip experience, but I understand your point, maybe sometimes I m too nice, what to do...
For the screenshots, I didn t mix 'em, I explained in OP that I didn't have time to make any since I ran short of time, and that the ones I put here come from another phone.
A galaxy grand i9082, yep, well done, you have a sharp eye!
They are very similar in shape, layout and color (apart from the cascade icon to minimize windows that Samsung has removed after 4.2.2, a big mistake to my opinion), so people can get the idea.
WaseemAlkurdi said:
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Click to expand...
Click to collapse
In some ways you are right, but we think that being professional is not a bad thing, despite the fact that the forum is full of picky users, ready to make bad comments even without trying the product. Of course, we can and we will also give a VIP experience, but it is reserved for the ones that will earn it.
In any case we appreciate your support. Thank you
WaseemAlkurdi said:
All builds prior to NK1 are without KNOX.
NH6 is good and speedy.
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Also, the screenshots are from a Grand 1, and our device is SM-G7102, not I7102. You mixed up with the Grand 1 i9082.
Click to expand...
Click to collapse
When downgrade strucked at boot logo "samsung".
Thai version. 4.3. What to do wasim? Any idea.
Odin flash failed. Again flashed NH6. Again boot loop.
Pllllzzzzz download link
Sent from my SM-G7102 using XDA Free mobile app
wrishaba said:
When downgrade strucked at boot logo "samsung".
Thai version. 4.3. What to do wasim? Any idea.
Odin flash failed. Again flashed NH6. Again boot loop.
Click to expand...
Click to collapse
As I recall, wiping (data/cache/Dalvik cache) from recovery worked.
You're lucky you ain't in a hard brick
Note that you need ClockWorkMod Recovery to wipe Dalvik.
EDIT: Please direct any development questions, queries, etc. to the new thread in the Development Forum, concerning all development-y things.
http://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-12-1-g530w-t3424761
============================================================
I've recently started working on a custom ROM for the Samsung Grand Prime G530W [gprimeltevl/gprimeltecan], and so far I have built a somewhat working ROM (without any radio/wireless capability or audio for now).
If there is interest in this project (which I think there is; the lack of any kind of love shown for the G530W is annoying), I'll continue hacking away at it until I (hopefully) have a working ROM.
I'm new to Android ROM building in general, and there have been several bumps along the way, so any help would be appreciated.
Thanks.
I will be uploading images daily to my Drive storage, in folders named by date (if the date today is not there, then the image had not been built or uploaded yet), and will be compressing the system.tar images with either gzip or xz to reduce the image size.
I will also be updating this area with issues and fixes as necessary.
What I have managed to get working so far (23/07/2016)
Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Wifi is working
Screen brightness controls working
Sensors are working (magnetic, rotation/gyro,proximity)
App installation is now working
Camera is kinda working - only back camera works, and the image is distorted.
Issues
Radio [ modem ] is not working properly
NFC is not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/open?id=0B-bYwctD_MoDaWJGcUQ4eWtzRTQ
Project GitHub Repositories:
https://github.com/vince2678/android_device_samsung_gprimeltecan
https://github.com/vince2678/android_vendor_samsung_gprimeltecan
If there are any other issues I missed, let me know.
Great effort
vince2678 said:
I managed to compile and get an image working for the G530W.
What I have managed to get working so far
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Sensors are working (magnetic, rotation/gyro,proximity)
Issues
Device fails to unlock and heats up [only once, so far]
Wifi is not working
Radio [ modem ] is not working
User interface crashes periodically
Screen brightness controls not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/folderview?id=0B-bYwctD_MoDVzd0eS1aaDV6RW8&usp=sharing
I'll be working at it to get at least the Wifi working, if there are any other issues I missed, let me know.
Click to expand...
Click to collapse
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Zippy Dufus said:
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Click to expand...
Click to collapse
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
vince2678 said:
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
Click to expand...
Click to collapse
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Zippy Dufus said:
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Click to expand...
Click to collapse
Hey Zippy,
That sounds like a good idea.
That website does seem kinda sketchy, and their downloads take millenia, but it's the only option available and their images actually work (just make sure to get the correct one).
Setting up a virtual machine is a good idea, because heimdall doesn't work with this device and I'm not keen on bricking my device trying to force it.
Rebooting between builds to test firmwares because of a lack of a good recovery was becoming a pain. (CyanogenMod Recovery is still missing critical features but it's better than stock).
You can use CF-Auto-Root to root the device (so simple) at:
https://download.chainfire.eu/774/C...uto-Root-gprimeltecan-gprimeltevl-smg530w.zip
Yup, debloating is good, i wanted to do so at first but I wanted to be done away with KNOX and have an su binary which worked flawlessly for good so I decided to start from scratch.
I've considered starting from M, but that will be a task for later. It is troublesome to start from a fimware above what your device is at when you're porting, because the vendor libraries and binaries you copy might not work in the newer version of Android because of linking errors.
You can copy the binaries fine but obscure errors due to missing references will pop up in the logs which will stop the modules from loading or binaries from running.
I'm having these issues with a build ID that is just a few apart from the one used on the stock ROM - LMY49J on the cm build versus LMY47X on the stock).
My Git repos are above - you can get yourself a cm12.1 source tree, pull my device_ and vendor_ trees, pull proprietary files using the scripts in the vendor tree, build from source and then flash the resultant images to your device.
The G530H ROM might, in theory flash without issue and actually boot, but whether it will be usable is another thing.
The thing that differs between the devices, as far as I'm aware, is mostly the baseband, some other device hardware (e.g the G530W has 1.5GB RAM instead of 1GB as most G530 devices), and the device bootloader. As such, the kernels and modules used might differ slightly in terms of modules compiled in, even though they're built from the same kernel source.
And yes, indeed, I started from a G530 device and vendor tree, though whether it was that one, or perhaps one for the G530FZ, I don't remember (though I think it's the G530FZ, it's the device closest to the G530W).
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Some more questions ...
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Pbotelho said:
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Click to expand...
Click to collapse
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Zippy Dufus said:
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Click to expand...
Click to collapse
Hi Zippy,
I do not have a local_manifest, if you want you can just manually pull the device and vendor trees into your build area, or you can make one yourself if you wish.
I will probably make one though, because the build has dependencies on some qcom sources.
I just use 'make -j8' to build everything, though you can use 'make otapackage' to build a flashable zip [You'll need the CMR recovery from here though, the images can't be flashed by stock recovery]
For creating flashable tar files, you can just use `tar`. You don't need to make .md5 verifiable archives, those are just to ensure a download wasn't corrupted [I provide md5sums for checking].
The system.img in the output directory will have to be renamed to 'system.img.ext4' and then archived, as so:
Code:
cd out/target/product/gprimeltecan
ln system.img system.img.ext4
tar cf system.tar system.img.ext4
tar cf boot.tar boot.img
tar cf recovery.tar recovery.img
Then you can move the files wherever and flash them with Odin.
Yes the gprimeltevl/gprimeltecan baseband is indeed G530WVLU1AOFB, though this should work with all G530WXXXXXXXs (not sure how many different ones are out there].
I'm not sure about the SIM locking thing, I cannot confirm this, someone might have to try to check.
I did consider sourcing from that repository, though ultimately i ended up using another one [I don't remember the name]. I might take a look at their source to see what I can do about mine though.
I did trip KNOX, though that was back when I was still trying to root my phone with CF-Root, so I'm not sure if flashing this will trip KNOX. And yes, KNOX is completely gone from this device, with no problems from the phone.
vince2678 said:
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Click to expand...
Click to collapse
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Edit: Upon further analysis, it seems that the notification content is linked to the bottom of the header instead of the bottom of the quicksettings tiles, and that's why it works this way. When expanding or shrinking the header, the notification also moves directly with it.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
4) Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
That's all I got for the moment, I tried to be as descriptive as possible as I won't be able to get the logcats up for awhile. Let me know if you have any questions about what I've said here.
And also, are you taking feature requests?
Pbotelho said:
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Click to expand...
Click to collapse
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
Click to expand...
Click to collapse
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Click to expand...
Click to collapse
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
Edit: when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
Click to expand...
Click to collapse
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
And also, are you taking feature requests?
Click to expand...
Click to collapse
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
vince2678 said:
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
Click to expand...
Click to collapse
1) Aww man I love using Trebuchet, I like to keep my install as small as possible so I'm not one for installing additional apps. I'm a resource junkie though, so its just a matter of personal preference.
2) Again, I'm not an expert, but I suspect it might be the device port. Previously, I've had an unofficial version of CM12.1 installed on a Galaxy Tab 3 as well as a CM12.1 based Pac-rom installed on a Galaxy S4. I'm not sure if this is something those developers corrected on their own or not when building their ROMs, so it could be the source. That's the best of my knowledge on the topic.
3) Will do for the brightness slider, but again, it isn't something I experienced on the other devices with CM12.1 and the sister project.
4) Yeah I played around with the governors and tried all of them. They all list 0MHz as the only option. Maybe its a CPU hotplug issue? I didn't try playing around with those so I'll have to get back to you on that one.
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
4) USB fast charging, aka setting USB to "charge only".
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Pbotelho said:
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
Click to expand...
Click to collapse
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
Pbotelho said:
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
Click to expand...
Click to collapse
I fixed this in the device tree, once I've built a new image this should be corrected.
Pbotelho said:
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
Click to expand...
Click to collapse
I'll be looking into this one.
Pbotelho said:
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
Click to expand...
Click to collapse
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
Pbotelho said:
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
Click to expand...
Click to collapse
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
Pbotelho said:
4) USB fast charging, aka setting USB to "charge only".
Click to expand...
Click to collapse
This is already available under the Settings->Storage->USB Computer Connection menu
Pbotelho said:
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
Click to expand...
Click to collapse
Not sure I could do this, I'll check.
Pbotelho said:
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Click to expand...
Click to collapse
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
Pbotelho said:
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Click to expand...
Click to collapse
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
vince2678 said:
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
I fixed this in the device tree, once I've built a new image this should be corrected.
I'll be looking into this one.
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
This is already available under the Settings->Storage->USB Computer Connection menu
Not sure I could do this, I'll check.
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
Click to expand...
Click to collapse
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Pbotelho said:
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Click to expand...
Click to collapse
The USB tethering thing sounds interesting, though I would need to have one of the adapters to test that, and time at hand as well.
As for the build environment, the best source of information is the CM wiki. You can look at these links below on how to get started:
https://wiki.cyanogenmod.org/w/Development#Learning_To_Build_CM
https://wiki.cyanogenmod.org/w/Doc:_Building_Basics
https://docs.omnirom.org/Setting_Up_A_Compile_Environment
https://wiki.cyanogenmod.org/w/Build_for_captivatemtd
http://jira.omnirom.org/browse/OMNI-1263
http://forum.xda-developers.com/showthread.php?t=2329228
The guides above are just outlines to detail the general build process - you will need to do things slightly differently from the steps above to get the proper source and device trees.
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
vince2678 said:
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
Click to expand...
Click to collapse
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Pbotelho said:
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I've test Kernel Adiutor and I too got the O MHz only window for both as the only option. Though Now I wonder if it is because I used the latest beta Kernel Adiutor, I'll further check with the normal stable version. Pretty sure it'll fix it if it worked normally for Vinc. --- Update; As strange as it might look while re opening kernel adi to take a screenshot, the list of normal MHz values is there and working properly.. Strange.. Magic? Huh technology, you're so unpredictable.
Zippy Dufus said:
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Click to expand...
Click to collapse
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
vince2678 said:
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
Click to expand...
Click to collapse
As an experiment, why don't you try downloading the G530H ROM, unzip, take the boot.img, and flash it over top of your stock kernel? See if it boots and how it performs.
Meanwhile, I plan to hack at putting together complete manifest, possibly with the G530H kernel and my Linaro 4.9 toolchain and see if I can build a complete ROM.
Have you extracted the firmware?
However, I don't want to flash anything until I see your ROM's modem working because it is my daily driver. But I'm keen though!!
I've managed to download the stock ROM from SamMobile but I'm now thinking of going straight to your ROM once it is a bit more complete and stable.
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
Most Promising Leads for Installing Android (1/12/17)
I have tried to install Bliss OS, but with not much luck. Once you get passed the GRUB screen it says there was an emergency error of some kind and reboots the device.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
I found that his updated installer (v25.0004) doesn't work at all, but the latest version from the original developer worked fine, linked below:
https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
I followed the following methods, all which resulted in a failed attempt, but the one with the most success was the first one:
- Easy install for Bliss-x86 UEFI/ESP
- For Bliss-x86 USB based installs
- Custom install for Bliss-x86 UEFI/ESP
My next attempt will be with Phoenix OS.
OLD INFO (as of 1/12/17)
Edit: I managed to replicate my situation twice. So I now have a method. Will post more info soon.
Okay... so if you want to get into Remix OS (knowing it's only temporary), here's how to replicate what I did. But make sure you have the following tools:
- USB keyboard & microUSB to USB adaptor (for the keyboard)
- Remix OS (I'm using the 64-bit version)
- A bit of time
What I did:
- Install Remix OS (doesn't matter what size you choose; 8, 16 or 32) on your C: Drive (main Local Disk) with the bundled installer
- Reboot when it finishes (via the dialog box, don't reboot any other way... it won't work properly)
- Give it about 10-15 minutes on the first boot. It'll be "stuck" at this Android-looking thing (mine's all glitched up and stuff)
- When it's done it'll show a black screen, and the Pencil icon to switch the Halo Keyboard on/off will stop turning on&off, it'll instead just stay on 100% of the time
- Reboot again, again choosing to boot into Remix OS
- As soon as you choose Remix OS, you NEED to hold the escape (ESC) key!!! If you don't do this, you'll have to start from scratch
- If you did it right, it'll come up with a couple lines of code, and then after a couple second it'll say "ANDROID" underneath the code, and everything will load up
- Everything should be in portrait-mode, but you should have no graphical glitches now, and should see the setup screen
- The touch-screen still shouldn't work here, you need to use the keyboard to navigate through the setup. If the Wi-Fi bit isn't connecting properly, do that later (just skip that step, up the top right). I left Google Play Services enabled, it doesn't matter, it won't ask for your information unless you open a Google App.
- When you finish the installation, everything should work (except the Halo Keyboard of course)
- To make Remix OS take up the whole screen instead of just the middle... go to the Settings App -> Remix OS Settings (whatever the top one is) -> Always show landscape thingo, toggling this off will make it use the whole screen instead of that little square in the middle.
This is far as I've gotten. I've tried getting USB Debugging to work, but it doesn't want to work. Bluetooth doesn't work for me, nor does changing the brightness. I wouldn't lock the tablet either, sometimes that doesn't work. Also don't try use the Google Play Store, because when you finish entering your information, it'll likely crash and you'll have to start over again. Rebooting will reset everything.
OLD INFO (as of 30/03/17)
I've had some random luck (as told in my recent post, I'll quote it here) with Remix OS.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
Click to expand...
Click to collapse
Somehow I managed to get it working, but only temporarily.
If I'm able to replicate this situation again, I may be able to install the Stock ROM alongside Windows 10. However, I don't have all the time in the world, so this may take a long while.
General Yoga Book Information:
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
The SIM card is a Nano-SIM with 3G capability.
Other than that, all Yoga Book devices share the following specifications:
- 10.1 inch IPS display, of resolution 1920x1200
- Intel Atom x5-Z8550 processor, which:
----+ Has an architecture of x86_64 (ie. 64-bit)
----+ Core base clock of 1.44 gigahertz
----+ Core boost clock of 2.4 gigahertz
----+ 4 cores and 4 threads
- Battery capacity of 8500 milliampere hours
- On-board storage of 64 gigabytes of solid-state storage (SSD)
- 4 gigabytes of random-access memory (RAM)
- A microSD card slot capable of up to 128 gigabytes of storage
- Two camera's, one above the display and one on the keyboard
- Wi-Fi (802.11 ac) and Bluetooth (v4)
- 3.5 millimetre headphone jack
- Micro-USB 2.0 OTG port
- Micro-HDMI port
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
- Windows 10 with AMIDuOS on-top (honestly wasn't that great)
Currently testing:
- Windows 10 with BlueStacks on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting BlueStacks on-top of Windows 10, which is a player that allows you to run Android apps. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
Ehh... BlueStacks isn't that great after all. Personally I'd stick with Windows apps if you need something like that.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
AmiDuOS works for me but the keyboard language cannot be changed somehow.
nan0s7 said:
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
General Yoga Book Information:
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
Currently testing:
- Windows 10 with AMIDuOS on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting AMIDuOS on-top of Windows 10, which will be like having an app that just runs Android. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
Click to expand...
Click to collapse
deepsync said:
AmiDuOS works for me but the keyboard language cannot be changed somehow.
Click to expand...
Click to collapse
Have you tried different keyboard apps?
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
deepsync said:
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
Click to expand...
Click to collapse
Hmm you're right. I've tried switching to a Polish keyboard in AMIDuOS, and it doesn't work at all. Although I didn't try switching the keyboard language in Windows, and then using AMIDuOS. I'm kind of optimistic that that method may work, so possibly give that a try if you haven't yet?
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
sawyerbenjamin said:
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
Click to expand...
Click to collapse
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
nan0s7 said:
However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
Click to expand...
Click to collapse
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
jamespmi said:
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
Click to expand...
Click to collapse
I've got Windows machines all around me. Which is... tolerable. But it's more that I just enjoy having Android on my device, and I do really enjoy messing with tech. I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
nan0s7 said:
I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
Click to expand...
Click to collapse
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
jamespmi said:
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
Click to expand...
Click to collapse
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
nan0s7 said:
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
Click to expand...
Click to collapse
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Melliejoy said:
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Click to expand...
Click to collapse
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
nan0s7 said:
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
Click to expand...
Click to collapse
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Melliejoy said:
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Click to expand...
Click to collapse
Yeah I wish I had gotten the Android version, but I got mine for a reduced price... so I can't complain too much ;P
Yeah... none of the emus are perfect anyway. I'm hoping that a new version of x86 Android or Remix OS will allow me to get ADB to work, so I can then flash Android. But I'm not holding my breath for that.
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
sawyerbenjamin said:
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
Click to expand...
Click to collapse
Nah I haven't done anything recently. But if you're having trouble getting things booted use my method (assuming it still works now) and I guess see what you can do
nan0s7 said:
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
Click to expand...
Click to collapse
Is your stock ROM for YB1-X90F or YB1-X90L?
ljbha007 said:
Is your stock ROM for YB1-X90F or YB1-X90L?
Click to expand...
Click to collapse
I have both. Got them from easy-firmware (had to pay for the X90F version).
They're not "ROMS" so much as they are just a way to replace Android with this particular version. So it comes with all the .img files for each partition you'd normally see (system, boot, etc.) and some scripts to use with the Intel flasher program thingo.
Hi guys,
I recently dug up this ancient piece of hardware wondering if i could get it back into a usable state again, as expected the normal windows 11 edition was almost unusable. So i created an ISO based on https://tech-latest.com/ghost-spectre-windows-11/. Its completely stripped down version of Windows 11 and has an intuitive command line tool to install your needs.
NOTE: As with all custom windows builds be careful about putting in personal data, i don't know the sources, I just added the drivers.
Bugs:
All drivers are already installed, only thing not working is Camera... but let's be honest... that thing never worked please SHARE if you found a solution
Instalation instructions:
Download iso here: https://mega.nz/file/5YwHyRaR#kgjrw2iQI23EvW2V6ReqlUu1-Rs9GT60zzhPXSNU-CA
Download Rufus here: https://rufus.ie/
1. Use Rufus to create a bootable USB
2. Dont use any of the Rufus options to customize your install
3. After creating the USB connect it to the tablet through a USB OTG adapter
4. Press F2 while booting up, select to boot from USB
5. Wait till in the windows install screen (this can take up to 15 mins).
6. Go through windows installation (can take up to 1 hour)
7. your pc will automatically reboot
8. set up admin password
9. connect to wifi
10. open GHOST TOOLBOX on the homescreen.
11. you'll see a menu with numbers, type in the number of the feature you'd like installed and it will guide you through the installation.
Tip: start downloading a browser first
yeah I know, the install time is insane. But at least you will have a semi-usable tablet.
MAKE A BACKUP OF THE ISO( IT'LL BE ACCIDENTALLY DELETED IN THE FAR FUTURE).
THIS ISO WILL ONLY WORK FOR THE FIRST EDITION YOGA BOOK WITH WINDOWS 8. DONT SEND ME A DM QUESTIONING ME IF IT'LL WORK ON [INSERT GENERIC CHINESE BRAND]
Good luck and may the odds be ever in your favor
“I installed Ghost Spectre Compact without DEF and I would like to add it. Can I upgrade without reinstalling?” Thanx
You saved my life! Your ISO was very helpful, and the solution you provided was both light and stable. My yoga book was broken and wouldn't boot, but now it's working very well. Thank you!
kakalotfreedom said:
You saved my life! Your ISO was very helpful, and the solution you provided was both light and stable. My yoga book was broken and wouldn't boot, but now it's working very well. Thank you!
Click to expand...
Click to collapse
Thanks, it's good knowing I didn't do it for nothing. I mostly created it for myself but was so surprised with the usability that I decided to share.
Tbh I'm not really sure if this ISO is compliant with the MS Terms of Service. So I would recommend to download a backup
At least this ISO makes the tab usable and I'm happy I could share this goodness
Btw, I discovered that the camera's are not working with this iso. Please let me know if you found a solution
just working with superlite and its not good for audio production like Pro Tools my CPU not working with all cores even if i want to change to make my CPU work with full core from
System Configuration in windows >boot>Advanced option
is grayed how can i fix this?
and if i want to go with compact is any way to ypgrtade without losing setup plugins and configuartion installed before to make the system
the flying dutchman said:
Thanks, it's good knowing I didn't do it for nothing. I mostly created it for myself but was so surprised with the usability that I decided to share.
Tbh I'm not really sure if this ISO is compliant with the MS Terms of Service. So I would recommend to download a backup
At least this ISO makes the tab usable and I'm happy I could share this goodness
Click to expand...
Click to collapse
I attempted to install Android and Windows Lite on my slow Yogabook, but it resulted in it not starting up properly and being unresponsive to touch. However, with the help of your software, my old sluggish Yogabook now looks great and runs smoothly - almost like a brand-new device. Thank you very much for your assistance.
about the camera, check on setting, camera VO2740 is working well for me. You can try to update the drivers (instead of the battery driver)
Minanapil13 said:
just working with superlite and its not good for audio production like Pro Tools my CPU not working with all cores even if i want to change to make my CPU work with full core from
System Configuration in windows >boot>Advanced option
is grayed how can i fix this?
and if i want to go with compact is any way to ypgrtade without losing setup plugins and configuartion installed before to make the system
Click to expand...
Click to collapse
This is weird. Tbh I never looked into that and the perceived speed of the device is faster. Maybe there are some changes in this build that affect the multi core performance? Maybe the lack of TPM and windows 11? Is hyperthreading and or virtualization enabled? And have you tried it on the normal version of windows 11 and was it different? It could also have something to do with the limited CPU. I'm busy with my graduation internship, so don't really have time to delve into it myself