Related
[GUIDE] How to use the Note 2 at 260dpi w/ MultiDPI & Tablet Apps (Xposed, Universal)
Warning: Some people have reported boot loops after installing Xposed Framework. I've used it successfully with miscom's stock International DLL1 ROM port and scrosler's deodexed I317UCALK7 without an issue. I'm wondering if the issue could be with odexed ROMs and will take any reports on failures odexed vs deodexed.
The Note 2 ships with 320dpi configured in the build.prop file, making visual elements huge and easier to use farther away from your face or to accommodate bad vision. To maintain a screen real estate per inch ratio similar to that of a regular Android phone, you'll need to do a few easy tweaks which are easily reversible. This guide also includes tweaks to make Chrome, Gmail, gReader Pro use their tablet UI.
None of this is new, but I haven't found it documented anywhere that well. I've experimented with a dozen different DPIs, tried the multi-DPI mods, and found this to overall by the easiest and most stable route.
Requirements:
Root
ROM Toolkit Lite https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Xposed Framework APK http://forum.xda-developers.com/showpost.php?p=34609290&postcount=2
Xposed Tweakbox APK http://forum.xda-developers.com/showthread.php?t=1629653
Package Name Viewer https://play.google.com/store/apps/details?id=com.gijoon.pkgnameviewer
OPTIONAL Modded Samsung Keyboard http://forum.xda-developers.com/showthread.php?t=2001577 (if you want use Samsung KB)
OPTIONAL Xposed App Settings http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile (if you want to set app DPI with a GUI rather than editing XML)
Step by step:
Recommend a nandroid backup before starting
Install the requirements listed above
Open Xposed Installer and tap "Install/Update" and reboot
Open Xposed Installer, to go Modules and ensure that "Xposed Tweakbox" is checked
Open Xposed Tweakbox once, then close it. Don't enable anything here, it wasn't designed for the Note 2 and may break your phone.
Open ROM Toolkit Lite, open the Root Browser, and browse to /data/data/de.robv.android.xposed.mods.tweakbox/shared_prefs/
Open the de.robv.android.xposed.mods.tweakbox_preferences.xml and modify it to include your DPI/UI mods. You can start with everything in my example file below after "START DPI MODS". Either copy & paste the text or replace the file with my example through Dropbox or USB.
Open ROM Toolkit Lite again, swipe over to Performance, go into build.prop editor, scroll all the way down, tap one of the "ro.sf.lcd_density" items, change 320 to 260.
If you want the stock Samsung keyboard to work, you'll have to get the modded version linked above for your ROM version. My personal goal is to keep the stock APKs untouched on my phone, so I just use the AOSP 4.2 keyboard, which scales fine to any DPI. Setting the Samsung keyboard DPI in the XML file doesn't work like it does with apps.
Reboot, you should be good.
The de.robv.android.xposed.mods.tweakbox_preferences.xml file needs to be configured to sets all of the apps that would break to a fixed 320dpi and enables Tablet mode for some Google apps. I use Nova launcher instead of TW and have it's DPI set to 300. To tweak your other apps, add them to this file using the package names found using Package Name Viewer.
You can see in the example how tablet mode is force by adding a line. There's a few other apps you could add here, such as Settings, but I found Settings to be a little too tight. This line sets tablet mode for Chrome:
Code:
<int name="dpioverride/com.android.chrome/swdp" value="600" />
To go further, the DPI of Chrome can be changed (in this case to match the Nexus 7, with this:
Code:
<int name="dpioverride/com.android.chrome/density" value="213" />
Our issue of Samsung compatibility is solved by adding lines such as this:
Code:
<int name="dpioverride/com.sec.android.app.camera/density" value="320" />
My de.robv.android.xposed.mods.tweakbox_preferences.xml file:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<int name="low_battery_low" value="15" />
<int name="num_signal_bars" value="4" />
<boolean name="unplug_turns_screen_on" value="true" />
<int name="long_home_press_behaviour" value="2" />
<int name="statusbar_clock_color" value="-4276546" />
<boolean name="battery_full_notification" value="true" />
<boolean name="statusbar_color_enabled" value="false" />
<boolean name="statusbar_clock_color_enabled" value="false" />
<boolean name="show_ongoing_ime_switcher" value="true" />
<int name="low_battery_close" value="20" />
<boolean name="phone_increasing_ringer" value="true" />
<int name="low_battery_critical" value="5" />
<int name="statusbar_color" value="-16777216" />
<!-- START DPI MODS -->
<!-- Play Store Keeper required to prevent DPI Errors in Play Store -->
<int name="dpioverride/com.android.vending/density" value="320" />
<!-- Tablet Mode Mods -->
<int name="dpioverride/com.android.chrome/swdp" value="600" />
<int name="dpioverride/com.noinnion.android.greader.readerpro/swdp" value="600" />
<int name="dpioverride/com.google.android.gm/swdp" value="600" />
<!-- Samsung Compatibility DPI Retainers -->
<int name="dpioverride/com.sec.android.app.voicerecorder/density" value="320" />
<int name="dpioverride/com.sec.android.app.camera/density" value="320" />
<int name="dpioverride/com.sec.android.app.videoplayer/density" value="320" />
<int name="dpioverride/com.sec.android.app.popupcalculator/density" value="320" />
<int name="dpioverride/com.sec.android.app.launcher/density" value="320" />
<int name="dpioverride/com.android.contacts/density" value="320" />
<int name="dpioverride/com.android.phone/density" value="320" />
<int name="dpioverride/com.android.smspush/density" value="320" />
<int name="dpioverride/com.sec.android.app.clockpackage/density" value="320" />
<int name="dpioverride/com.sec.android.app.FlashBarService/density" value="320" />
<int name="dpioverride/com.sec.android.mimage.photoretouching/density" value="320" />
<int name="dpioverride/com.android.calendar/density" value="320" />
<!-- Custom DPI Settings -->
<int name="dpioverride/com.teslacoilsw.launcher/density" value="300" />
<int name="dpioverride/com.android.chrome/density" value="213" />
<!-- END DPI MODS -->
</map>
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've also found that you can set the notification bar to the Nexus 7 style tablet size by adjusting the System UI swdp, although it's a little ugly with my toggles.
Add this line:
Code:
<int name="dpioverride/com.android.systemui/swdp" value="600" />
This should be sticked. Great post
Sent from my SAMSUNG-SGH-I317 using xda premium
Phone locks up after the first reboot when installing the xposed framework. Running Jedi rom.
barry99705 said:
Phone locks up after the first reboot when installing the xposed framework. Running Jedi rom.
Click to expand...
Click to collapse
1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).
Att.Fan1982 said:
1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).
Click to expand...
Click to collapse
Interesting, I'm using type 2 of the same ROM. Must be one of those extra mods that Jedi uses as well.
Also getting bootloop running stock international N7105XXDLL1 after installing/update the framework and reboot
VinceThePrince said:
Also getting bootloop running stock international N7105XXDLL1 after installing/update the framework and reboot
Click to expand...
Click to collapse
Which type number are you on?
Does anyone have this working? I have tried three different ROMs( asylum, Jedi, and miscoms ROM #2) and two kernels with no luck. I boot loop after installing the first mod
Sent from my SGH-I317 using xda app-developers app
It's always worked on miscom type 2 for me. I wonder if the framework installer has changed since I got it installed. I've pulled the framework installer off of my phone, can someone try it with this?
http://db.tt/1YKhPYcX
Zathu said:
It's always worked on miscom type 2 for me. I wonder if the framework installer has changed since I got it installed. I've pulled the framework installer off of my phone, can someone try it with this?
http://db.tt/1YKhPYcX
Click to expand...
Click to collapse
I don't know if it was installing busybox from the market this time or the copy of your framework installer but I got it working! Thank you!
Sent from my SGH-I317 using xda app-developers app
moustro said:
I don't know if it was installing busybox from the market this time or the copy of your framework installer but I got it working! Thank you!
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Hmm, don't most of these suped up ROMs like Jedi have Busybox included already? Perhaps it is the Framework version. I've updated the main post with a new link.
Zathu said:
Hmm, don't most of these suped up ROMs like Jedi have Busybox included already? Perhaps it is the Framework version. I've updated the main post with a new link.
Click to expand...
Click to collapse
Jedi doesn't have it, but it still locks up with busybox installed.
Thanks for the guide. After trying different DPIs I've found 260 feels perfect for this phone.
barry99705 said:
Jedi doesn't have it, but it still locks up with busybox installed.
Click to expand...
Click to collapse
The updated framework link should take care of that.
Zathu said:
The updated framework link should take care of that.
Click to expand...
Click to collapse
Nope. Still locks up at boot. Though with the newest installer I can no longer adb into the phone, so I get to do the battery pull and restore instead of just doing an adb shell are moving the file back from it's backup...
Just tried this today. I found it was easiest to use the gui based app settings mod. Much simpler than coding up the xml. Works great with Gmail at a low mid forced resolution and moderate dpi. I recommend a nandroid backup because I got stuck in boot the first time around.
Edit: the best apps for this I've tested were Gmail and reddit sync. Chrome was a waste of space and the play store was overly laggy.
This is awesome, thanks OP!
I found that I had to add com.android.mail to the list of 320dpi apps, or there were a few UI issues in the mail app. Loving having Chrome with the tablet UI!
Zathu said:
I've also found that you can set the notification bar to the Nexus 7 style tablet size by adjusting the System UI swdp, although it's a little ugly with my toggles.
Add this line:
Code:
<int name="dpioverride/com.android.systemui/swdp" value="600" />
Click to expand...
Click to collapse
What do I do just to get this? Nexus 7 notification? Where do I add that line?
Will this mod work with stock rooted rom (jl5)? Does it need to be deodexed?
Sent from my SGH-I317M using xda premium
Code:
*** Disclaimer by cdesai
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
I'm starting this thread to see if DEVs and collaborators get motivated and help. I'm not really a DEV but...
Ubuntu Touch is still a WiP itself, and this is a Work-in-Progress of getting it to our SGT7 Tabs - P1000, P1000N/L/R/T/CDMA/etc
Click to expand...
Click to collapse
Features
Works: touch, wireless, camera...
Doesn't: audio, brightness, sensors, 3G/Mobile...
Click to expand...
Click to collapse
Installation instructions
Regular flash through CwM Recovery:
Wipe/Factory Reset
Flash cm-10.1-YYYYMMDD-UNOFFICIAL-p1.zip or cm-10.1-YYYYMMDD-UNOFFICIAL-p1c.zip
Flash quantal*.zip
Flash hdpi_overlay.zip
Click to expand...
Click to collapse
Changelog
UT ROM based on CM10.1 with humberos' kernel, p1 and p1-common. OS image directly from Ubuntu downloads.
Click to expand...
Click to collapse
Code:
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation, manual brightness.
2013-05-10
[note] My first UT boot.
[new] Thread created.
[changed] built and booted
[fixed] Now it boots!
Downloads
Base ROM
cm-10.1-20130515-UNOFFICIAL-p1.zip - fourth update!
cm-10.1-20130515-UNOFFICIAL-p1c.zip - fourth update! - NOT working - bad kernel without recovery. Reported by @sxfx
Ubuntu Touch Quantal from the MWC Demo:
quantal-preinstalled-phablet-armhf.zip
Ubuntu Touch Saucy:
saucy-preinstalled-touch-armhf.zip
Screen configs - changes screen resolution and proportions
hdpi_overlay.zip 20130515
Sources
https://github.com/sgt7-ut - maybe someday. :cyclops:
Mods/Addons/Themes/User Art
Ubuntu Touch Auto-debloater & Ubuntu Logo Welcome Screen
Click to expand...
Click to collapse
FAQ
The FAQ section in a thread is bound to grow over time... check for updates.
Q: How do I flash?
A: Learn that before coming here.
Q: How do I restore my {fill in here} ROM?
A: Learn that before coming here.
Q: How do I use ODIN?
A: Learn that before coming here.
Q: How do I use Heimdall?
A: Learn that before coming here.
Click to expand...
Click to collapse
Links and References
Ubuntu for Tablets
Touch install
UT Porting Guide
UT Building
Quantal MWC Demo CD Images
XDA Ubuntu Touch General Porting Discussion Thread
XDA Ubuntu Touch Forum - For non-device specific stuff
How to use apt-get through ADB + Apache Proxy without Networking
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* humberos, the latin kernel king.
* cdesai
...
Building Ubuntu Touch
First of all have your CM10.1 build up to date.. if you can't build CM10.1 then you shouldn't even try this.
[UPDATE 20130515]
Successful build for p1 and p1c!
Basically follow the Porting guide. Initialize the repo as instructed, using phablet-dev-bootstrap.
My draft for building... soon we will have the sgt7-ut repo that will do most of it for us.
Not necessarily in order.. you might have to start compiling untill you get the error and come back and check the steps again.
Code:
## our manifest
copy the roomservice.xml to .repo/local_manifests/
## clean
rm -rf out kernel
make installclean
make clean
* edit as porting guide:
kernel/samsung/aries/fs/proc/array.c
* add extra lines from the porting guide to the end of:
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1ln_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1c_defconfig
* also change the following config in each of the 3 kernel configs:
CONFIG_TOUCHSCREEN_QT602240_ROT90=n
## prepare stuff
source build/envsetup.sh
breakfast p1
breakfast p1c
./get prebuilts in vendor/cm/
comment P1Parts, tvouthack and Torch from device/samsung/p1-common/device_base.mk
copy from your cm10.1 build - out/target/product/p1/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
copy from your cm10.1 build - out/target/product/p1c/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
?? cp out/target/product/p1/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1/obj/EXECUTABLES/make_ext4fs_intermediates/
?? cp out/target/product/p1c/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1c/obj/EXECUTABLES/make_ext4fs_intermediates/
Add chmod line in device/samsung/p1-common/init.p1-common.rc, like this:
# System server can control backlight brightness
chown system system /sys/class/backlight/s5p_bl/brightness
chmod 0666 /sys/class/backlight/panel/brightness
## Now build!
source build/envsetup.sh
breakfast p1
time make -j3 bacon # use -j1 to check for errors in their right order
breakfast p1c
time make -j3 bacon
.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="humberos/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="humberos/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" revision="cm-10.1-dev" />
<project name="humberos/android_device_samsung_p1" path="device/samsung/p1" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1c" path="device/samsung/p1c" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1-common" path="device/samsung/p1-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>
Change ro.sf.hwrotation to 0 in build.prop!
reserved 3
reserved 3
Wow, thnx! I'm downloading!:beer:
send from my Nexus
:beer::thumbup:
Sent from my GT-P1000 using xda app-developers app
That is one of the ubuntu, unless my eyes are cheated by some spell
Nice Ubuntu Logo in CWM
Hi,
first test. Don't get nervous, while unpacking ubuntu file lasts (4.5 minutes)
Also be patient during boot, first time i thought the Tab went off.
ubuntu boots, i can activate the start menu, but no further actions.
Thank you for your great work, alroger and humberos!
cinq
So, I sort of flashed this and nothing happened. It's just a fresh CM installation. Am I supposed to build something on device?
Edit: had a brain fart, got it generally working.
Sent from my SCH-I510 using xda premium
alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)
cdesai said:
alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)
Click to expand...
Click to collapse
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?
alroger said:
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?
Click to expand...
Click to collapse
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.
cdesai said:
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.
Click to expand...
Click to collapse
Cool, it works!
Hey, isn't there a ROT180 to use to invert the landscape? Or can you point me to the right file to edit this ROT90 config?
EDIT: Found it.. gonna try hacking a new ROT180 config.
EDIT2: Yay, I did it! My first customized kernel config: CONFIG_TOUCHSCREEN_QT602240_ROT180
Have you fixed the touchscreen bug? Can you please reupload the recompiled cm?
Thanks!
UPDATE 20130515 it works!
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build! let us know if it boots!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation
Building tips in Post #2.
Ubuntu Saucy
It works with the latest Ubuntu Sacy Salamander, but no wifi. Download link added.
Must edit /usr/bin/ubuntu-session manually in the ZIP and change:
Code:
# defaults
GRID_UNIT_PX=8
QTWEBKIT_DPR=1.0
FORM_FACTOR="tablet"
Don't use hdpi*zip on this one.
Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.
UPDATE 20130515 rotation fixed! brightenss fixed!
dexterash said:
Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.
Click to expand...
Click to collapse
Rotation fixed! New uploads!
Camera is aligned with then screen now.
Brightness fixed - uncheck Automatic brightness and you can choose your brightness.
Enough for today...
Is WiFi and mobile data working?
Sent from my GT-P1000 using xda app-developers app
Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app
areshinakya said:
Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
No, the base ROM is the base for any UT. But as I said it's working only with that build. Saucy worked also but without wireless.. there are new daily updates for raring and saucy every day... gotta keep on trying.
Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/knowledge-base/open-source/android-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?
anybody? please help
thsecmaniac said:
anybody? please help
Click to expand...
Click to collapse
Do pm to a developer.like abhinav2,or deadwar,op of carban rom
Sent from my LT26i using xda premium
thsecmaniac said:
Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/kno...droid-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?
Click to expand...
Click to collapse
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk
What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
abcdjdj said:
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk
Click to expand...
Click to collapse
thsecmaniac said:
What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
Click to expand...
Click to collapse
These files are known as the vendor blobs. They are proprietary files whose source code is not available to the public. Some of these vendor files are used by various components of the phone like the camera etc. The ones on the Sony website are very old so if you use them, it is quite possible that the camera might not function properly. As Sony released official updates, if I remember, they even fixed laggy 1080p recording. So it would be much better to use the latest blobs.
Sent from my Xperia S using Tapatalk
PSA: as of date there are new Official Havoc OS builds maintained by @ClintT available in the telegram channel Havoc-OS OnePlus 6/6T or on [email protected]. these include both cams and twrp. builds with and without Gapps are available.
there are currently no builds of Official Havoc OS here come some works-for-me-why-not-for-you builds of Havoc-OS for Oneplus 6/6T.
The ROM is based on the Havoc-OS manifest, Illusion kernel and modified Lineage sources at the time of building.
It includes recent Urnyx's Gcam mod as well as OOSCam and Gallery.
for
Oneplus 6 - A6003 (enchilada)
Oneplus 6T - A6013 (fajita)
Disclaimer: have fun, no guarantees, your warranty is now void, there's always the sun (for at least some time from now)
Note: The Oneplus 6T (fajita) build is released completely untested, while the Oneplus 6 (enchilada) is tested and works as expected. For known issues/not working check the sections below. Feel free to drop a line below if/how it runs on Oneplus 6T (fajita) so i can update the status.
Requirements:
- you might need to update to latest stock beforehand, get the Android 10 based OxygenOS(OOS) zips over at Oneplus support
- Mauronofrio's TWRP 3.3.1+ for Oneplus 6 (enchilada), Oneplus 6T (fajita)
- backup everything before install to be on the safe side, to be extra safe backup the backups from device to a harddrive (in the case you lose access to the data partition)
- wipe data when upgrading from another ROM
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP6/OP6T!!!!! You will loose data decryption keys up to the need to reinstall via Fastboot or MsmDownloadTool.
Installation:
Clean flash
1. boot into TWRP (Mauronofrio's TWRP suggested)
2. flash latest OOS
3. flash TWRP installer zip
4. reboot to recovery (switches active boot partition)
5. flash OOS again to make sure its on both slots
6. flash TWRP installer zip
7. reboot to recovery (switches active boot partition again)
--
8. flash ROM (Havoc-OS-*.zip)
9. flash TWRP installer zip
10. wipe data and cache
11. reboot to recovery (switches to the boot slot the ROM was just installed to)
12. flash Opengapps (optional)
13. flash Magisk (optional)(flash after setting up device)
14. reboot system (fingers crossed)
Dirty flash (when coming from earlier Havoc-OS 3.x)
1. flash Havoc & TWRP installer zips
2. reboot to recovery (switches to the boot slot the ROM was just installed to)
3. flash Gapps (optional)
4. flash Magisk (optional)
5. reboot system
Suggested apps/kernel:
- Eng.stk's unified Blu_spark kernel for OP6/6T xda thread, download
- Urnyx05's Gcam mod https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/
Not working:
dunno
Known issues:
you tell me
Download:
Oneplus 6 (enchilada) builds
Oneplus 6T (fajita) builds
Sources:
ROM-Manifest
https://github.com/Havoc-OS/android_manifest
Device trees
https://github.com/bdhay/havoc_device_oneplus_enchilada
https://github.com/bdhay/android_device_oneplus_fajita
Kernel
https://github.com/AOSiP-Devices/kernel_oneplus_sdm845
Others
see roomservice.xml below
Thanks:
to all Havoc-OS, LineageOS developers and everyone who contributed to this ROM
@AnierinB for helping to get OOSCam going
Mini-howto:
1. setup build env on a linux box as outlined on https://github.com/Havoc-OS/android_manifest, mainly install repo command from distro or google and init repository in a folder that will hold the build
Code:
mkdir -p ~/havoc
cd ~/havoc
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
2. after 'repo init ...' save roomservice.xml with the following content
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/oneplus/enchilada" remote="github" name="bdhay/android_device_oneplus_enchilada" revision="havoc-ten" />
<project path="device/oneplus/fajita" remote="github" name="bdhay/android_device_oneplus_fajita" revision="havoc-ten" />
<project path="device/oneplus/sdm845-common" remote="github" name="bdhay/device_oneplus_sdm845-common" revision="havoc-ten" />
<project path="kernel/oneplus/sdm845" remote="github" name="AOSiP-Devices/kernel_oneplus_sdm845" revision="ten" clone-depth="1" />
<project path="vendor/oneplus" remote="github" name="bdhay/proprietary_vendor_oneplus" revision="ten" clone-depth="1" />
<project path="device/oneplus/common" remote="github" name="bdhay/device_oneplus_common" revision="ten" />
<!-- inaccessable just now, uncomment if you want the cameras below built in
<project path="vendor/addons/google/camera" remote="github" name="Evolution-X-Devices/vendor_addons_google_camera" revision="ten" />
<project path="vendor/addons/oneplus/camera" remote="github" name="Evolution-X-Devices/vendor_addons_oneplus_camera" revision="sdm845" />
-->
</manifest>
to
Code:
.repo/local_manifests/roomservice.xml
Note: the folder .repo/ should already exist, just 'mkdir .repo/local_manifests' before adding roomservice.xml
the file contains the repos making the devices known to the build tree.
3. sync the repos
Code:
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
4. init environment
Code:
source build/envsetup.sh
5. check if device is there
Code:
breakfast enchilada
# or
breakfast fajita
and finally
6. start build
Code:
brunch enchilada
# or
brunch fajita
Changelog
2020/09/01
- fix OOSCam support
- include Urnyx05's Gcam mod and OOSCam
- Alert-Slider working now
- switch to Illusion-Kernel
2020/08/24
- initial release
buddhay said:
reserved
Click to expand...
Click to collapse
Cool....
chandu dyavanapelli said:
Cool....
Click to expand...
Click to collapse
Did you tried? How's it?
sschacko said:
Did you tried? How's it?
Click to expand...
Click to collapse
I try it soon buddy
chandu dyavanapelli said:
I try it soon buddy
Click to expand...
Click to collapse
Ok
Thought I would try and build from what you posted... #### failed to build some targets (13:32:46 (hh:mm:ss)) ####
Gotta love a fail LOL.
TrOjAnUK said:
Thought I would try and build from what you posted... #### failed to build some targets (13:32:46 (hh:mm:ss)) ####
Gotta love a fail LOL.
Click to expand...
Click to collapse
still waiting for peeps to say how the ROM is working out and the first real comment is 'Bob The Builder' gotta love xda folks
how about posting a longer stack? the above says just that it didn't work.
just to make sure i repeated my mini-howto after posting it. works for me :good::angel:
buddhay said:
still waiting for peeps to say how the ROM is working out and the first real comment is 'Bob The Builder' gotta love xda folks
how about posting a longer stack? the above says just that it didn't work.
just to make sure i repeated my mini-howto after posting it. works for me :good::angel:
Click to expand...
Click to collapse
Ahh sorry... wasnt asking for help.. just thought it was worth a post to amuse people after a 13 hour build.. I`ll get it fixed, wanted to try and get the OOS camera working.
Apologies for being a Bob the Builder
TrOjAnUK said:
Ahh sorry... wasnt asking for help.. just thought it was worth a post to amuse people after a 13 hour build.. I`ll get it fixed, wanted to try and get the OOS camera working.
Click to expand...
Click to collapse
ahh, nice! please share the recipe if you succeed. i am wondering if including the OOS Camera is not violating the GPL but obviously several roms do so on xda.
btw. consider enabling CCACHE=1 with a folder preferably on SSD/RAMdisk. speeds up subsequent builds considerably. obviously not if nothing changed, but after repo updates or when compiling the "other" device.
After a Day, it works for me without issues! (Enchilada) Everything is top. No FCs or something.
Baron1971 said:
After a Day, it works for me without issues! (Enchilada) Everything is top. No FCs or something.
Click to expand...
Click to collapse
nice!
still waiting for fajita owners to say their piece.
Not sure if I had a bad download or what I didn't even look to see how big zip was after it finished downloading but twrp kept telling me to boot to other slot after I'd already flashed OOS 10.3.5 on both slots and then rebooted recovery and was attempting to install havoc. Twrp would appear to begin install then stop and say reboot recovery or something like that..Using a 6t here. I'm downloading it again and will check to see once it's done then try and install again. Thanks for building Havoc for 6/6t! :good:
Will report back in a few.
Has anyone booted fajita Havoc 3.8?
When i attempt to flash Havoc on fajita in twrp (I used
twrp-3.3.1-32-fajita-Q-mauronofrio.img and also the twrp I've been using for months which is black themed 3.4.0 v1) the result is my attached screenshot. ?
Sidenote: I made sure I had a complete download..
Edit added: update.. I checked md5sums. I still am not successful at installing. I've probably flashed about 1k times on this device alone and owned three AB partitioned devices previous to this one.. Never had anything just not install in twrp until now. I find it almost impossible that nobody else with a 6t has flashed...? Anybody? Nothing is wrong with my device. Anything else flashes fine. ??
flash713 said:
When i attempt to flash Havoc on fajita in twrp (I used
twrp-3.3.1-32-fajita-Q-mauronofrio.img and also the twrp I've been using for months which is black themed 3.4.0 v1) the result is my attached screenshot. ?
Sidenote: I made sure I had a complete download..
Click to expand...
Click to collapse
that's not saying much. my guess would be an incomplete/broken zip file.
can you show an 'ls -l' of the zip file?
also please do an md5sum of it and compare it with the one on the download location.
ok, just read your 'Sidenote'. please proof you have the complete/proper download via checksumming.
buddhay said:
that's not saying much. my guess would be an incomplete/broken zip file.
can you show an 'ls -l' of the zip file?
also please do an md5sum of it and compare it with the one on the download location.
ok, just read your 'Sidenote'. please proof you have the complete/proper download via checksumming.
Click to expand...
Click to collapse
I just flashed enchilada, seems to be beautiful. I'm not gone deep, but any how really appreciated
I'm facing a brightness bug where adjusting the slider doesn't do **** I'm worried about my phone staying on max brightness all the time please fix this issue
Aduser345 said:
I'm facing a brightness bug where adjusting the slider doesn't do **** I'm worried about my phone staying on max brightness all the time please fix this issue
Click to expand...
Click to collapse
which device? works for me on enchilada. if auto is enabled or not makes no difference too. cannot test on fajita.
maybe try a clean flash. see OP
Hi, i want to build Havoc myself. I followed your Instructions, but i get the following Error:
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
Code:
Traceback (most recent call last):
File "/home/ivt/havoc/.repo/repo/main.py", line 49, in <module>
import event_log
File "/home/ivt/havoc/.repo/repo/event_log.py", line 167, in <module>
_EVENT_ID = multiprocessing.Value('i', 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
return Value(typecode_or_type, *args, **kwds)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 108, in Value
lock = RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
return RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
What can i do?
Baron1971 said:
Hi, i want to build Havoc myself. I followed your Instructions, but i get the following Error:
repo init -u https://github.com/Havoc-OS/android_manifest.git -b ten
Code:
Traceback (most recent call last):
File "/home/ivt/havoc/.repo/repo/main.py", line 49, in <module>
import event_log
File "/home/ivt/havoc/.repo/repo/event_log.py", line 167, in <module>
_EVENT_ID = multiprocessing.Value('i', 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
return Value(typecode_or_type, *args, **kwds)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 108, in Value
lock = RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
return RLock()
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
What can i do?
Click to expand...
Click to collapse
well https://www.google.com/search?q=_multiprocessing.SemLock+repo&oq=_multiprocessing.SemLock+repo first result https://forum.developer.parrot.com/t/repo-sync-permission-denied/9341 suggests it's a permission error. try that.
also i am not sure that repo is still supposed to run on python2. try python3.
Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!
I suspect that by reverting this commit :
https://github.com/LineageOS/lineage_wiki/commit/3c7f61f7c5e2353202427d6ff44587770b644ce3
and with a few more hacks even newer versions of android could be built for the Oppo Find7, any gurus out there that could help with this task?
Just tried to compile LineageOS 17.1 sources. I'm taking a look at the oneplus one device tree because they use the same SoC and it has already received even LineageOS 18.1. To compile successfully I need to repopick 279639 279641 279647 and 266411.
There is no MindTheGapps 10 so I tried OpenGApps pico but could not flash due to limited space.
Finally I tried to boot anyway but with no luck like @farmatito with LineageOS 16. So yes we need a guru, maybe @mikeioannina jump on the train again?
As mentioned by @farmatito BiTGApps can be installed. And i got it boot but i could not take a screenshot because of insufficient memory. screenrecording was possible though
Hi,
this is great news, I hoped this would be possible! Keep up with the good work.
With a little help this could be a fully usable phone as the OPO is still supported IIRC.
P.S.: in the next week when high season is over I hope to post a new build of LineageOS 16.
I think you must compile ones a migration build to switch from official to your builds without wiping data. I have done it in the past with this script from lineageos.org.
Hi,
I've read about the script but had not the time to implement it, also I suspect that it would not be a good idea
to migrate users to user-debug keys but that you need to generate a private key. If I would use my private key
for this I suspect that it would have security implications for the user. So best would be to generate a private key
for every user at installation time to protect his privacy and security but then where do we store this key? onto the
device itself seems not a good idea...
This crypto stuff scares me as I don't fully understand it.
Best would be every body compiles it on his computer and uses his own key.
I don't know why LineageOS never officially integrated LVM support, but for me having only 3GiB of internal storage was always a problem. 16GiB looks much better, I think. And since twrp officially supports lvm as well...
Yes. I know. OmniRom had LVM working and I still somewhere have the zip files to flash but the build system needs also to be patched (there was a patch for this from omnirom to lineage but I lost it). It scares me to touch that pile of code and I hate git. There would also be chinese partitioning, should have the the exe somewhere, but even for that the build system needs to be patched with the new partition offsets (and the kernel?).
At least encryption doesn't work on my LVM build at the moment and there is no auto-detection whether LVM or not. So the user can decide if he wants to use LVM or not.
I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output
gcs88 said:
I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output
Click to expand...
Click to collapse
fdisk -l /dev/block/mmcblk0 | grep system
14 294912 3006463 1324M 0700 system
Hi,
I will try to build with your repo as soon as I have some spare time, at the moment I am busy with another
project that has some kind of deadline.
Ciao,
farmatito
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.
gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.
Click to expand...
Click to collapse
Thanks for your try. Installed 6th October build and basics are working well. Didn't test much but Wifi/Bluetooth/Phone are just fine. Update from last official Lineageos required flashing twice (first went straight back to recovery, second time booted to system).
Gapps (tried OpenGApps nano no chance: got code 64 in recovery). I will try Bitgapps next free time slot
Keep up with the good work.
gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Click to expand...
Click to collapse
Hello and many thanks for that rom.
I do have a question but don't know if it exactly belongs here. Maybe someone can tell from experience.
I did change to "Chinese unification storage method" using "X9007_Android5.0_16G_20150520" for a Find7a (X9006) as explained in this post.
My device storage now is 16 gigs, 4 already used after a clean install of Lineage OS 17.1.
Weird for me is the "mobile storage" which now shows
a corrupted sd-card which can not be formatted (seems to be like a left over from the previous partition, like its there but not) and
my external sd-card, which works fine
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.
los 17 flashed using bitgapps and it works pretty fine. no screenshot saving issue
install procedure
- do unified storage procedure (LVM to Chinese unified storage thread)
- flash setup lvm and remove lvm zips (might not be required)
- wipe system, data and cache
- flash los 17, bitgapps then cm 13 unified patch
- boot up.
if you get wallpaper glitch on the lockscreen just change wallpaper.
color os stock cam doesnt work anymore on android 10. use bacon camera from playstore
open gapps pico may not work. it flashes normally but you either get bootloop, stuck on setup (wifi wont connect) or google play services will be broken.
morTimar said:
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.
Click to expand...
Click to collapse
Yes, that's ok for Chinese partitions. I have this problem on all versions of lineage
Sounds like for ringtone, notification or alarm can not be selected.
"android.process.media keeps stopping"
But good trial. At least I was able to flash Android 10 on my old Find 7 just for fun
farmatito said:
Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!
Click to expand...
Click to collapse
地址怎么用