Related
Hello all
I have been attempting to enable a framebuffer console on the LG Nexus 5 device for debugging purposes while enabling extra kernel features, and also ideally to be able to boot Debian with Xorg directly on the phone. I am currently using rooted Android 4.4.2-based custom ROM with a kernel I have built from the unmodified source of "android-msm-hammerhead-3.4-kitkat-mr2" branch.
For testing X and framebuffer console, I have enabled framebuffer console options (kernel config here). With this kernel, I only get the standard Google boot logo and boot animation, no framebuffer console. The kernel command line arguments include "console=tty0,115200 fbcon=font:VGA8x8", which I can confirm are not overridden by the bootloader by checking /proc/cmdline after bootup.
While running the same kernel, a Debian chroot with LXDE/Xorg installed with a shell access via SSH, I can run "FRAMEBUFFER=/dev/graphics/fb0 startx". If the Android UI is currently active, the display is filled with random pixels and stops responding. I can kill X via the SSH session, but there is no difference, although after about 5 minutes the display resets and returns to normal android screen. I have tested using the default charger app (located at /charger on standard image), and it produces the same effect if UI is running at the same time.
If I disable the Android UI through ADB shell command "setprop vold.decrypt trigger_shutdown_framework" (this disables all android services except for ADB, including zygote and surfaceflinger), I am able to run /charger successfully (which results in the charging icon appearing on-screen when the power button is pressed - this is the same program that is run when the phone is plugged into a power source while powered off).
Using the Debian chroot, running the startx command results in a blank screen except for a brief flash of an inverted-colour LXDE desktop when X is shutting down (CTRL+C in shell used to run startx) before the display goes blank. This is as close as I have got to getting X working on the Nexus 5 with the default xfree86-video-fbdev driver.
Another thing to note, running the command
Code:
cat /dev/urandom > /dev/graphics/fb0
with or without the Android UI running has no effect on the display.
According to this thread and some amazing work by Tasssadar, framebuffer console can be enabled with MSM chipsets, however LG Optimus One uses the older MDP3 framebuffer video driver instead of the Nexus 5's MDSS framebuffer driver. It seems like the MDSS framebuffer implementation (in drivers/video/msm/mdss/mdss_fb.c) has some differences that make it incompatible with standard framebuffer devices. I would attempt to modify the driver in the kernel source so that it would function as a standard framebuffer device and ideally be compatible with framebuffer console and Xorg. I have little experience in kernel development and have no idea where to start with regards to fixing the issues with this particular driver.
The dmesg log when I run /charger with Android UI running is available here. Charger app is started at system time 80.140298, and the errors start immediately after. At the end you can see when the kernel resets the driver and this is when the display resumes normal function.
I would like to know if anyone has tried this before, and if they have been able to get any further than me with regards to a framebuffer console or running Xorg either in a chroot or natively on a Nexus 5.
Also I would like to know if there is anyone who would be interested in trying to develop a working framebuffer driver for this device.
Thanks to everyone who can help with this
Any luckwith the MDSS fbcon?
Hi
I am new this forum and hope this is the right place for my request - thank you for advises.
I want to test smartphone (Samsung S4/S5/S6 & Motorola latest models) displays using a phone as tester. The displays (matching the phone type) will be connected by an extension flex, connector.
Many displays will be tested with 1 phone. Here is an example of testing S6 display.
1. Connect S6 display no1
2. Turn on S6 ; the actual smartphone acts as a tester - capable of testing many displays ; turn ON must be within few seconds (max 3 - unlike the standard boot up process)
3. User runs application - testing display (running several standard color patterns), touch sensor test - by drawing a rectangle around the perimeter of the display, nav key test
4. Pass/Fail - user evaluates - with an option of repeating the test if necessary
5. Turn OFF S6 - this should be within 1-2 seconds
6. Disconnect S6 display no1
7. Connect S6 display no2
There are already existing quite a few apps with testing the display however none of them offering SAFELY display removal. Its only possible (I think) when the device is completely OFF, but then it
has to be turned ON and with a standard BOOT up just this process could take a minute. The phone does not have to be turned off if there is an application which allows to SAFELY disconnect
not killing the circuitry on the actual main board and neither on the display! Otherwise I beleive it would need a modified root/operation system which only loads a min processes needed for the test.
The actual TEST phone can be reflashed, does not require any additional mobile functionalities (like the main radio transceiwer,amplifier, WIFI, camera, sensors, etc) just the test app which only controls the DISPLAY.
Please let me know what would take ($$$ & time) to make such application?
Thank you
Hi,
I recently bought a Tolino Tab 8 with a Intel Atom Z3735 processor, running on KitKat 4.4.4. Everthing works fine but every time i switch between apps the screen brightness changes depending on the background of the app e.g. when i open twitter (mostly white background) the screen brightness goes up and when i go back to the home screen (black background) the brightness goes down. No matter if i enabled auto dimming in the settings or not. I've read that has something to do with Intels Display Power Saving Technology which is used to extend the battery life of the tab. I tried to edit the build.prop (mentioned here http://forum.xda-developers.com/showpost.php?p=65422943&postcount=1786 ) to turn it off but nothing worked so far. I also tried to find the driver settings itself ( mentioned here https://forums.lenovo.com/t5/Lenovo...Tab-S8-50-Screen-Dimming-Problem/td-p/1873040 ) but could'nt find the right settings.
The Tablet was manufactured by Trekstor if this matters somehow.
Hope you guys can help me to solve it.
I also have a minor bug where i can't change video resolution in the youtube app above 720p even the Display has the resolution of 1920x1200 which i think has something to do with 4.4.4.
So I've tried to pitch the idea to LG, KitePhone and posted it on other Samsung A9 YouTube videos [Gaining 3 invisible Likes, this could boost Samsung's MicroSD Card Sells] about how they seem to add more cams than SDCards because of how Google's Android brags about expandable space, but you have to root in order to Expand your Internal Storage & RAM in order to install more apps.
I've decided to just lay out everything here [Multi-MicroSD, Dual Battery, RAM Saver & LG G6Jaw].
Also I would have loved to post this in LG G5, Moto Play or Off-Topic Threads, but I'm sick and tired of newer OS's & more Cameras, but the features we need aren't being improved on and hope to garner support (Probably a Chipset).
I'm sorry in advance if this belongs to off-topic.
Multi-MicroSD: Why Dual Card Trays?
Experience: If you know of configure Swap Memory, Partition a MicroSD Card, Assign ext2/3/4 Filesystem and Linking Apps2SD (Mostly big OBB Data for Games) to install more Apps or Store more (For Apps that can't move any of their content to your User Card), but encrypts your MicroSD (Removed while Running OS == Need to Format) then you know how to expand your Internal Storage by experience.
Rumors:
- Internal Storage is a Gloried MicroSD Card (pre-Lollipop Phones)
- Swap Filesystem uses more MicroSD Life-cycles (If True, hence 3rd MicroSD = easy swap & cheap replacement)
- Apps run slower on MicroSD Card (Due to Old Phone Specs, but Today's Phone Specs with 2.x - 4.x vs 5.x - 9.x Apps and newer MicroSD Cards)
Concept: If we had a 2nd to 3rd MicroSD Card or a 2nd Card Tray (To prevent confusion) then we wouldn't need 512GB Internal Storage & 10GB RAM Phone Prices like iPhone, but we can pay $60 for Expand add 32GB to Internal Storage and 16GB to RAM or $100 to add 64GB to Internal Storage and 32GB to RAM for 64-96GB to Internal Storage and 20-36GB of RAM (Not faster ram though, but for those "You need it to run in the Background" replies).
Android & Technology has come a long way in Specs that running Apps and/or just OBB Data from a Class 10 MicroSD Card (Samsung S3Mini, Kitkat 4.3, 1GB RAM, 8GB ROM, LinkApps2SD: GOF2, GTA:SA, H&C2, KOTOR's OBB off a Class 6 MicroSD Card) runs with little to no drops in speed or response...unless the app is built bad or should require higher specs.
- Apps are 50-200MB avg (rarely 300-500MB) in size with OBB/Cache Data from 1-4GB Average with a 32GB ROM after OS, OS Apps & etc, 20GB is for the User allows 100Apps if all Apps/Data/etc were 200MB avg with OBB Data moved to User Card vs 40 Apps if each app were 500MB
- Some apps haven't been completely updated to use Lollipop Permissions feels like Android has less and less
You would Go to Settings > Storage > Expand > Basic (Pick/require Whole MicroSD Cards as ROM and/or RAM and attempt different ext if ext4 doesn't work) or Advance (Partition & assign Filesystems to Specific MicroSD Cards)
Dual Battery: Dual MicroUSB + Dual Charging
Experience: So after May 2010, I tweeted about a Laptop with 2 CPUs(Motherboards)/GPUs/HHDSlots/DiscDrives/Battery/MorePorts(Charging/USB)/etc (Mobile Tower), a Add On Half-Laptop and a Phone with Split Motherboard (The word I was looking for is Modular) for in case it breaks you replace only the Broken parts vs the Whole Phone to Dell Micheal (I had a D800 Latitude and saw a lot iPhones breaking on the TV & news).
From there I was happy to see Blockphone & Project Ara, but sadden by its fall (Cause Google OS would need new Updates per 3rd-party/New Blocks).
During that time I came across Androids from the same company with similar sizes, but different Batteries and thought Big Phones should 2 Batteries that 1 Battery can fit into a smaller phone (Its more complicated than that).
Concept: I later realize with the whole "replace 3.5mm Jacks with MicroUSB", having 2xCharging Ports (Cause sometimes where they are isn't great and now Multi-Choose) and Dual Battery = Dual Charging...which doesn't mean its 2x faster than Quick Charging because it depends on AMPs from the Wall Charger, but 2 small batteries are being charged at the same time for 2 Ports.
Also cause the battery is used in more phone Models...you might buy extra batteries == Swap without Hibernating...and make Cellphone Batteries into PowerBanks may be a better quality than PowerBanks from their go to LG G6Jaw.
So know you maybe you can config in Battery Settings that 1 Batteries charges the other or the phone uses both Batteries, from their you have your Dual Charging (Ports on Both Ends of Phone, use a 3.5mm2MicroUSB3.1 Adapter...unlike Apple if they had 1 Port then the Adapter should split into 2 for twice the Courage) and you can change both Batteries...1 for an Instant Half Charge if the Batteries a Powerbank stored & charged the Cellphone Battery while the other keeps the Phone running.
RAM Saver: Focus on My Apps Android!!! To Save Battery
Experience: Since the introduction of Power Saver and up until Oreo (OS 8), we couldn't go into power save mode while plugged in. If you had a Samsung and Cleared RAM from the built-in Task manager would say 32 apps have been shutdown...and your thinking to yourself I didn't/don't need that many apps opened at once, but when you search on forums, your reply is "You need those apps to run in the background to quickly start them, make your phone work or blah blah"...no I don't especially if its using up my RAM, Battery and causing other apps Force Close.
- The only app that needs to run is Android System (Force Closing via Root Task Manager = Restart)
- Developer Mode has No Background Apps and does a great job of saving RAM
Concept
- Some apps like Launchers or Task Killers usually are "I only need you when I open you" meaning "CloseLock" if I'm using a Download/Frequently-Used App, "BackRun" if I seem to switch back and forth from Launcher or if I set the App from Recent Apps to BackRun when I use the Home or Back Key
- Some Apps have a "Double-Tap Back to Exit" (Great & sometimes works), but NavKeys need/can hold 2 Inputs: Tap Back (Go Back until App Switch to another App or Exit, not the Launcher) & Hold Back to CloseLock (Meaning Force Close & don't run in the Background), Tap Home (Go to Home, don't need 2 keys doing the same Job) & Hold Home (Lite App Drawer...LG take notes...Basically a Quick Image of the App Drawer that launches apps based on Coordination), Recent (Recent Apps, Configure "RAM Config") & Hold Recent (Menu Key, Task Manager or Any other Key)
- Some Apps should be preset by User: "RAM Config"
++ Other than Disable/Hibernate, Downgrade/Factory Reset/Version Vote, Force Close and Clear Data/Cache
++ CacheResume (Start from Cache)
++ Limit Access (If you don't need it & can't disable then Stop all Permissions, Background Data & Notify Bar)
++ PersistClose (For App that reboot and can't be Disabled)
++ Save-Sensitive (Apps like Games, Browsers or Document Editing meaning don't reset if phone sleeps or app is BackRun unless android can detect when Game/Doc Editor has slept)
++ Tool Manager (Needs to run in background to do job, but can be Reset to clear Ram)
++ Foreground Only (For things like HomeLauncher/Lockscreen/Task Manager that you only need while Using it)
++ Blind Run* (For apps you don't need Bright/On Display and somehow use Keys to Control App)
*New
From their Google and Manufactures have to be honest of what needs to run from what doesn't...which might not happen.
LG G6Jaw: Concept of LG's G5 next Phone
Pasted from my F3Q phone (A Keyboard Slider that allows me to Type anywhere unless people think I'm rolling a Weed Joint...then I have to stand in the front of the bus, beside the Bus Driver so they and the many Cruisers can see my hands). I did this for Samsung T699 and later realize while Tri-Bezel was out, Non-Bezel was easier to achieve on a Keyboard Slider Phone.
Other ideas like HipBones & JawBones is a simpler version BlockPhone and the rest is unfinished (Samsung came out with a SmartWatch with a Sim Card)
LG G6 Jaw
Ask LG when they didn't have an app drawer, why didn't they just use the Shortcut for NavBar's Keys in the Settings to have it set by Default to Open the App Drawer when you hold the Home Button or simply add a App Drawer Key like you did for a Pulldown NotifyBar?
Non-Bezel 6" Display (720p, 60fps)
- Specs: CPU (4Core 1.6Ghz & 4Core 2.4Ghz), RAM (4GB), ROM (32GB), GPU (Adreno 650, Vulkan 2.0), CAM (Rear 16MP w/Flash & Front
5MP), OS (Android 8, 64-Bit), Battery (2x1500mAh), Ports (Top/Bottom MicroUSB-C for Audio/2xCharging/2xSDCard, Rightside Jaw)
- Overside: Far-Right MicroUSB-C Port, Infared Remote, Cam Microphone, Angled Case (Sensors & 5MP Cam), LockJaw Button
- Underside: Centered MicroUSB-C Port, Talk Microphone, LockJaw Button
- Frontside: User-Replace/Upgradeable by Tool to a 1080p 60fps Amoled Display, 6" Digitizer & 3xTempered Glass ($150)
- Backside: LoTop-Center PowerKey w/ScrollZone, HiTop-Center 16MP Cam w/Rightside Flash
- Leftside: Chip, Mid 2xCard Trays (OS: 2xMicroSD, User: MicroSD/SIM), Top-Side Volume Rocker, Bottom-Side TriggerZone (perApp)
- RightSide: Jaw, Top-Side Reciever/Speaker, Inner 2xBattery Slots, LockJaw Buttons (Top/Bottom Right)
Concepts
- About OS MicroSD Slots: Encryted Expansion for ROM (Internal Memory, OBB2SD) & RAM (Swap Memory)
- 32GB or 16GB ROM: Use ROM for Kernel/Driver Storage, RecoveryMode (or Recovery OS), Confirm Format/FileSystem/Partition, ROM
Install (Run/Read Only on ROM or Store Apps/Data on Card)
- Footage Specs: Phone =8MP Rear CAM & Jaw =16MP w/8xZoom, 32MP & 48MP w/Detachable ZoomLens, Soft/Pro Flash, 8GB Capture Buffer
- MicroSDuo Card: If 512GB = 1xMicroSD, therefore 64GB = MicroSD w/Polar Connectors, 2xStorage Spaces, Access by DuoSlot & DuoCPU, It
draws files from both sides
> Slot/Class Boost: SDcard w/Faster Class, MicroSD2SD Adapter w/ClassBoost, SlotBoost for MicroSD or SD CardBoost Compat- PrismMirror: Front Cam & Sensors facing upward and a Glass-Covered Mirror Topside to reflect Cam & Sensors on angle
- Sandwich Display: Sandwich Digitizer/Display/Protector into 1, when changing simple switch sandwich from while Rightside Out
- Sound Sets: Remove Back/Bottom Speaker, Combine Speaker/Reciever, w/Vol-Keys & Vol-Sets
> 15 Sets: Pass Lowest = Vibrate/Silent < 1-5 Hush w/1-10 Normal > Hold Vol-Up = Loud (Multiple Current Vol)
> 20 Sets: Pass Lowest = Vibrate/Silent < 1-10 = Hush Mode (1-5 Hush, 1-5 Normal)> Pass Highest = Loud (5-10 Normal, 1-5 Loud)
> 30 Sets: Pass Lowest = Vibrate/Silent < 1-10 Normal > Hold Vol-Up to Tog 1-10 Hush/1-10 Loud (Select)
> Auto-Volume: Possibly undelayed sound to keep audio at normal hearing level when their is whispering or shouting
> Default Volume per App, Not Silented, etc
- RAM/Battery Saver: When unplugged/plugged w/Battery Saver either lower power use or CloseLock (Hold to Close)/BackRun (Tap
Back Space to go to previous app) apps also pre-select how apps should auto-close/cache/etc
> Persist: For apps that undo options automatically (By holding key with start can disable options, in case of glitch)
> Disable: If option is avail or doesn't stop the phone from functioning properly then stop from startup and/or running
> Stored Link: Disable and leave a link to redownload later from app store, saves storage
> Downgrade: Save app's previous versions then when user wants to downgrade or a factory version they can pick/vote on version
> Limit Access: If unable to disable them limit Permissions, Background Data & Notify pop-up
> Foreground Only: Only need it when I open it like HomeLauncher/LockScreen/Task Manager, CloseLock instead of BackRun
> Save Sensitive: Closing would restart Game Level, Commenting or Document Editing
> RAM/Cache Save: I can leave off from where I started
> Tool Manager: Has to run in background to do job, but need to reset to clear RAM Buildup
Home to BackRun App & Go to HomeLaunch
>> Tap =Recent Apps (BackRun), Hold =HomeLaunch (BackRun)
Back to go Backwards in App's Pages, then 2xTimes to Exit to previous App or HomeLaunch
>> Tap =Go Back Page, Hold =CloseRun
Recent to switch between Apps, Task Manager, Remove from BackRun
>> Tap =AppDrawer, Hold =Menu Key
Menu to Open Menu + Any other action (Tog UI, Rotate Screen, Shortcut)
Main Jaws
- "Wordplay": Keyboard & Gamer Jaw w/+2 Battery Slots (2xSwap, 6000mAh), Keyboard Slipout (Lucid Bump Layout w/Slit for 2side Language/Config), Controller Backout (Switch Keyboard by taking off the back of Jaw and placing in Layout Holder), BackTouch, over a Digitizer and/or Plugin w/Closedown Clamp & LockJaw Buttons, VolSlider-Up/Down/MidKeyTop, TriggerSlider-Left/Right/MidKeyBottom & PowerButton
- "Theater": Projector & Speaker Jaw w/Shake/Move Stablizer (Gyro Projector, StayPlace-Capture/ManualLock/Feedback & Extreme Angle Rendering), able to project display with a Front Facing Projector& have a loud speaker to hear, MicroUSB to HDMI/AV Adapters, USB-C for OTG use w/Games to Project Games, +1 Battery Slots (1xSwap, 4500mAh), 2xHookLeg/2xGripLeg
- "Footage": Dualling/Wideshotting 16MP w/Phone, 32MP Follower & ProPhoto 48MP w/Detachable ZoomLens, +2 Battery Slots (2xSwap,
6000mAh), 4xReConfigable Keys, Zoom Slider/Dialer, SDCard Slot (For fasting Capture Buffer), Soft/Laser/ProFlash
+ Troop Casing (Proof-Shock/Water/Dust w/Key/Watch/Glass/App Control/MiniView, Vision-Virtual/Night/Lamp, ZoomHorn)
+ Adapt Casing (Non-Proof, allows Tablet or Different Size Phones from 8" to 4" Non-Bezel)
Sub Jaws
- "Powerhub": An Enclosed case of +4 Battery Slot (4xSwap, 9000mAh) that can latch under certain Jaws or connect via Retrofit
Jaw or MicroUSB-C 4xPorts. Jackless Charging via HandCrank, Shake, NFC or SwapBattery (Also a reusable PowerBank & USB/HDMI
OTG-Hub) w/4x1500mAh Batteries & 1x3ft MicroUSB Cord, 1xMicroSD Card Slots
- "Retrofit": UnderChin/SideJaw Adapter to use Chin/Jaws on any phone: Expand Biter w/2xLandPinch/2xSkyPinch, SpinTighten/
AdjustHandSide, GrillBack to cutout for Camera/PowerKey, Short Removable MicroUSB-C2C/B Cable, NFC/USB/Bluetooth Connect, App Manager for Jaws, 1xMicroSD Card Slots
Concept Jaw
- "Biracial": PC7 Runner Jaw by GDP (PC10, PS4, PSold, N-All, AllRace), View PC on Phone Screen via NFC/Beam/Cast/Jaw/
MicroUSB/Threater, 6xBattery Slots (2xPhone & 4xSwap, 12000mAh), Back Cutout SATAslot to SATAcase w/SATAport to Connect
Jaw2Case (or Jaw2Case2Cord2Cord2Case2Cord2Case, Jaw2Cord2Cord2Case2Cord2Case), 2xUSB-C Ports (Spaced Downward), 2xMicroUSB-C
Ports, 3DPrint Swapout Keyboard2Controller Layout, MouseStick/ClickLR, UnderMouse/ReleaseClick/HalfScroll/SpaceScroll, OS
Dual-Boot, Input2Android or Windows, CPU (Intel 2c/4c*2.2Ghz, Intel 5000 GPU), Nvidia 820M/840M/860M (PC7 LoConfig: ES5/JC3/
GRWL/AOM)880M/940M/960M (MidConfig: RDR2/DMC5/RAGE2/JC4), 980M/1060M/1080Mti/2080Mti (Other MidConfig: RDR2/DMC5/RAGE2/JC4)
+ Casepack: CaseSides: 2.5" SSD LeftSlot w/or 2xPCIe RightSlot, CasePCIe: 4xPCIe Slots, CaseSpace: 2x2.5" Drives LeftSlot w/
or 1xDesktop Drive RightSlot, CaseTower: 2xPCIe LeftSlots & 1xDesktop/Laptop Drive RightSlot
+ Cordpack: 3x1m SATA2Female/Male SATA Cord
- "Satellite": Global Calling from Open Area, Wifi/Bluetooth Booster, FM/AM/XM Radio Transmitter, Telephone/Either Jackport
SOFTWARE
- Jaware: Manage/Control/Config Jaws, Jaw2Jaw Functions (Footage w/Threater Lighting)
- Expander: Storage Settings > FileSystem Partition (ext2/3/4, Swap), Format/Encrypted for OBB2SD for OS & SwapMemory for RAM
- Hard Touch: Use Keyboard to Control any App (Joystick 2 Keys, Gesture/Swipe/Fling)
- Dot9 OS: 4/6/8, 5/10, 5/7/9 or 6/9/12 > Pack needed Features (Permissions, Battery Save Mode, Vulkan) into older OS
FUTURE
Non-Bezel Keyboard Slider F3q Sequels
- LG F5q: 5" Non-Bezel, 2xMicroSD Slots, 2xBattery Slots, 2xMicroUSB-3.1 Gen2 Ports, 2x1.8Ghz, Adreno 320, 2GB RAM, OS4.9 > 6.9
+ Front Cam/Sensors on Keyboard Half, Back Cam/Flash Display Half and Angled-Drilled Speaker/Reciever on Top of Display
or Keyboard Half, Use Keyboard to Control Cam w/ShotSets, Vol Hush/Loud ModeSet
+ F6q: 6" Non-Bezel, 3xMicroSD Slots, 2xBattery Slots, 2x1.6Ghz, 2x2.2Ghz, Adreno 530, 4GB RAM, OS6.9 > 8.9
+ F7q: 7" Non-Bezel, 3xSDuo Slots, 2xBattery Slots, 2x1.0Ghz, 2x2.0Ghz, 4x3.0Ghz, Adreno 740, 6GB RAM, OS8.9 > 10.9, Waterpro
+ Replaceable Language Keyboard Layout (LG 3DPrint Layouts), Dual Thumb-Bone Pyramid-In Axis-Sticks (Left/Right for
Line&Letter2Word/Smooth2Page Scroll, Display/Page/Mouse Scrolling), Center Numpad (For Ergonomical Alphabet), 2x1500mAh,
Sandwich Display+ Blackberry: KeySideA, KeySideB, KeySideC
> Key3: 6" Non-Bezel, 3xMicroSD Slots, 2xBattery Slots, 2x1.6Ghz, 4x2.4Ghz, Adreno 640, 4GB RAM, 16GB Storage, OS9
- LG G7 HipBones: Dual Tablet, Adaptive2Laptop, SpecStrips (Written Specs, OverCase), Android Emulator (Later to LG G8 JawBones)
+ Lo/Mid & Mid/Hi Tablet Board (Min = Built into Board to allow DOS/Recovery Mode) aka Project "The HipTop"
+ SpecStrips: "Process"
> Lo1: Adreno 530, 4GB RAM, Qualcomm 2x1.6GHz/2x2.2Ghz or w/Mid Process
> Lo2: Adreno 750, 6GB RAM, Qualcomm 2x1.8GHz/4x2.4Ghz or w/Mid2 Process
> Mid1: Nvidia 820M 2GB, 8GB RAM, i3-4th 2x1.6Ghz, Intel 4000 GPU
> Mid2: Nvidia 940M 2GB, 12GB RAM, i5-5th 4x1.8Ghz, Intel 5000 GPU
> Hi1: Nvidia 1060M 4GB, 16GB RAM, i5-7th 4x2.0GHz, Intel 6000 GPU
> Hi2: Nvidia 2080M 4GB, 32GB RAM, i7-9th 8x2.4Ghz, Intel 6000 GPU+ SpecStrips: "Energy" (4xSlots for Phone Battery Charging, 6000mAh) w/Performance Battery, Charging Port, 4xMicroUSB-C
+ SpecStrips: "Storage"
> Mid1: Slot/Ports: 2xSSD/2.5" Sata Drive, 2xSD Card, 2xUSB3.1, 1xUSB2, 1xHDMI, 1xVGA, BlueRay DiscCase w/LineLaser
> Mid2: Slot/Ports: 4xPCIe, 2xSD Card, 2xMicroSD, 2xThunderbolt, 2xUSB3.1, 1xUSB2, 1xHDMI, 1xVGA, BlueRay DiscCase+ SpecStrips: "Connect": Wifi, Bluetooth, GPS Card, 2xGSM Card, Signal Booster, 1xEther, 1xFibreOptics
+ SpecStrips: "Media": SlideUp Speakers/Front 5MP (If Strip is at top of Display Half), Back 8MP/Projector (AutoAdjust)
- 2ndSIM Watch:
- Phone Battery to charge Bike Battery:
Click to expand...
Click to collapse
Theory why Project Ara didn't work. I watched a Video saying they had trouble with Software (Android was 5 years old by then) and remembered seeing something about how the Drivers & OS are 1 (=ROM, why each Phone Model has its own ROM) while the Kernel is separate (I've replaced one without Touching the OS).
So I figured that Android at the time wouldn't be able to keep with new Blocks (Chips) based on the way Project Ara was Modular and/or maybe way to far ahead.
What I assume "Fuchsia" is a Fusion of Project Ara & Android by allowing or have Chips/Blocks with Built-in Drivers (Something I wish Windows & Samsung had like LG G5's Built-in Driver Installer vs the Extra Drivers Windows XP had or searching for them) to work with a Generic Android OS (Windows can do vs Android can't do) on a customizable spec phone...maybe the whole point of Android is to make a Perfect OS and Android 10 is actually Android 1.0...but that is just a Theory...a Crazy Theory
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Hem981,
I can confirm #7 is an issue on mine as well.
The power menu is an android 11 change not an OOS change.
I upgraded from OOS 10 to OOS 11 no wipe and don't seem to experience the other issues that you are having, except the obvious changes they made to the firmware. Have you tried clearing the dalvik-cache and rebooting? Mine was super buggy before doing this, but then again I just upgraded without wiping.
One issue I've personally noticed is the cell radios were a lot better on OOS 10, and I'm assuming that is the cause of the battery life to be worse.
Another that could be due to doing some debloating is when I take a screenshot and the little preview pops up in the bottom right corner if i click on it the UI will freeze after clicking back. The Nav buttons still work, like you can click on recents and the recent menu appears, back and home work but the screen is frozen otherwise until I force a reboot.
Yeah, I've tried factory reset and then wiping dalvik-cache... The performance was better before i performed the factory reset, i think. Anyway, there are quite a few games/apps where the performance impact is easily visible. Also, the power button thing is an Android change, but i really hoped OnePlus to have done something to make it more easily accessible (OOS is not pure Android). I couldn't find the issue with the cell radio you mentioned (as I've tried in areas in which i already had poor reception, and the performance was what was expected). Anyway, I really hope some of these (at least the performance, battery drain and the brightness slider issue) will be fixed soon over updates.
(For me, the SOT has gone down from 9.5 hours to 7 hours under similar use cases)
Yeah SOT has definitely taken a hit on mine as well, standby time seems the same. I also have noticed that the screen brightness needs to be set higher for the same brightness as OOS 10. The cell radio sometimes seem normal, but most of the time they are about 5-10 dBm higher at my house. I'll probably give a clean flash a try this weekend to see if it clears up.
One more issue found:
Weird red tint on screen auto dimming
The whole display has a weird red tint just before the device is about to lock/turn off screen after the timeout, when the display dims. It is easily noticeable if you have a white screen displayed. It only happens if you have set the brightness slider to anything other than the bare minimum (even a single step above the minimum brightness is able to replicate this issue)
I found something interesting: issue #3, the brightness slider being slow to respond to changes, seems to be fixed by disabling all animations from developer options. Should the window animator duration scale have any effect on the responsiveness/quickness of display brightness adjustment? I think that's stupid.
Also, I am starting to thing we need something like 0.1x duration scale for the animations (all animations on Android, or at least OOS), because honestly, with each new implementation, the animations are being too slow that it degrades the whole experience. 0.5x feels a bit better, but i really think something like 0.4x would match the animation speed of android 10.
You forgot to mention the vibration motor effect which has deteriorated since the update. The device now feels like any other cheap device.
It's kinda weird in my situation, just upgrading from 10.3.8 using an old version of xXx NoLimits to 11.0.0. The phone was super buggy when I first installed, but after rooting, wiping the delvik cache, debloating, removing the xXx module, and time to settle in the only issues I have are the screenshot popup, and the lower cell signal which I'm sure is causing a hit on battery life.
I was going to reinstall this past weekend, but for the time and inconvenience it's not worth the time compared to the minor issues I have.
Edit: Even the screen resolution seems normal now.
Again, don't know if this is an issue for anyone else (and i don't think OnePlus is going to change this): While everything else became bigger on the phone, the buttons/number keypad for typing in the screen lock pin became too small.
Hem981 said:
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Click to expand...
Click to collapse
Hi! Oneplus 7 ownere here.
Try to answer all the points:
1) i don't notice any difference between OOS10 and OOS10 on the heat of the phone
2) I don't know for the gaming performance but i don't play any games...overall, the performance are good, no system lags or freeze BUT I have the same issues with the notification...when i tap a notification, I often have delay, maybe it's just the animation but I remember the same issue on a Oneplus 8t that i tried for 20 days in last November
3) same issue here, very annoying
4) not just you, have same issue
5) battery drain is the same in my case, in standby maybe is less than before
6) me too, but maybe they change this as they planned?
7) yes, same thing. i changed the DPI from developer options too
8) no crashes here
9) this is an Android 11 change from Google, maybe they don't want your device to power off ahahah
10) never had this problem luckily
11) don't know, never tried this
12) i noticed this after reading this point, true on my device too
13) i faced the same issue on the notification sound, the other things works fine
14) me too, if i wanted One UI, i would have bought a Samsung...
15) sometimes happens to me, maybe it's bad ram management?
16) this is ridicolous, why they doesn't remove this app??
17) never tried
I also have an issue on the vibration. Now it's HORRIBLE, i have disabled because it's unusable
So, this is my question: change phone or rollback on android 10?
There's one more addition to the list: Always on display sometimes seems to override the notification lockscreen privacy settings. I have some notifications put as "view private content only when unlocked", but the notification contents are visible just when it arrives on the always on display (though it's content is hidden in the actual lockscreen)
I've reported almost all of these bugs, and hopefully we will see new updates fixing most of these.
Can someone on OOS 10 on OnePlus 7 confirm if the "style preferences" settings in sound settings is greyed out while the output is phone speakers (or no other sound output devices connected)?
New hotfix patch OTA rolling out now...
Here is what's fixed and what's not:
1,2 : Yet to test
3: Not fixed
4:Fixed
5: Yet to test
6: No changes
7: No changes(or not easily noticeable maybe?)
8: Not encountered any "ghost" app crashes yet
9: No change
10: DC Dimming is not back, so no change
11: Not fixed Is it that hard to remove 'headset' text from the UI?
12: Don't know if it's because my eyes adjusted to it, but it seems a bit better now
13: Not yet tested
14: What can I say?
15: Fixed
16: The ghost of Google Play Music still remains
17: Not fixed
Edits: Nothing much is fixed
Performance: Marginal improvements
SoT/Battery: Even worse. Getting almost half the SoT I got on OOS 10 under similar use case and network/tenperature conditions
Ghost app crashes reduced a lot (that might be the only fix) , but is not completely gone (saw that 1 or 2 times)
Haptics is still as bad as before
I'm just worried about this weired bug which has rendered my parallel whatsapp very difficult to use to share media. Any fix for this is highly appreciated - https://forums.oneplus.com/threads/whatsapp-media-problem.1411292/
Thanks and regards
OOS11 - Stable
I have no problems on my device until now (for games I dont know why I do not play)
I noticed, because I have tried both roms(beta4 & stable).Open Beta4 has better "battery management" than stable! Αs strange as it may seem but is a real for me..
Well yes .Battery drain higher than openbeta4
wifi works fine to 5ghz band & generally my device works quite well so far. Patience is needed and all problems will be fixed...
https://postimg.cc/gallery/YtQpVDm
After the recent OS 11 update ,the media in my device ( photos and videos) not being shown properly in Whatsapp. Some of the videos and pictures which I've already deleted in the gallery are appearing again only in whatsapp in unsupported file format.
I'll be glad if someone confirms that it's a bug in OOS 11.0.2 and that my phone is not the only one which is affected.
I'm using WhatsApp and Parallel Whatsapp. Also have setup a Work/Office profile on my phone.
Does anyone have any solution to this issue?
Thanks and regards!
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
itdiestoday said:
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
Click to expand...
Click to collapse
Try wiping cache from recovery
Update 11.0.1.1
I feel like this is a big joke.
Even more battery drain (yes, i did a factory reset).
Brightness slider issue still not fixed.
Performance still degraded (but i think there is a little bit of improvement)
Not sure about Wifi issues as i never had them.
Weird red tint on screen dimming
Still many ugly and inconsistent ui elements
Color profile is back to being broken (the yellow tint returned)
Update: I've started having the wifi disconnection issues, after 11.0.1.1 update. This is way too annoying.