Related
Hi guys,
it started with the search for a shortcut for the "secret" Samsung *#0*# dialer code, to enable the hidden Samsung LCD Test App...... and it ends with a little app called "Hidden Features Free Sammy Edt" ...(special tailored for the Galaxy S2)
This app provides a lot of hidden (stock) firmware functions with just a few clicks:
* Samsung LCD Test + Quick Test Menu
* Data Usage Status
* Phone Lock Status
* OTA Firmware Menu
* Change Browser UserAgent
* HSDPA/ HSUPA Menu
* RF/ Base Band Menu
* System Dump Menu
* Android Info Menu (including disable GSM)
* GTalk Monitor
* Show Android ID
* etc.
Check it out:
...discontinued due to changes in samsung firmware
There is also an ads free PRO version available, but please try out the FREE version first, to ensure that these hidden functions are available on your device .....
------------------------------
Have fun!
Installed thanks
Amazing thank you
Sent from my SGH-T989 using XDA App
np
regards
ascsa
... any additional suggestions/ comments?
Great! Thanks
...any suggestions regarding additional features?
Thanks,
But it doesn't works for me. I click in differents buttons but it does nothing.
I don't know if could be because I have installed a MIUI Rom in my Galaxy.
Hi mmm286,
yes, it is probably because of your custom rom ... This app uses hidden features within the Samsung stock firmware ... no Samsung stock firmware --> no hidden features
But you can try the second tab (with the little Android ) ... Perhaps the "pure" android features will work .... but again depends on your specific rom ...
feedback would be nice
regards
ascsa
https://market.android.com/details?id=com.lidroid.sgs.secretcode
Sent from my GT-I9100 using Tapatalk
Update available
-> New Features via custom codes tab:
- Manage (Add, Edit, Delete) carrier specific (USSD) codes
- Manage device/ manufacturer specific codes
Or use the custom codes tab as a simple, hidden, non-sync (Google, FB, WhatsApp etc.) phone book ...
regards
ascsa
Added shortcut for ICS Rocket Laucher
Enjoy this little hidden ICS gimmick
* Ice Cream Sandwich (Android 4.x) only *
any feature requests?
OK,
made some ICS related updates and fixes and said "Goodbye to the Menu Button"
Not only is this a cool app, but for some strange reason, it enabled the STK (sim toolkit) for my sim which was previously hidden somewhere on my phone. I am using a rooted Galaxy 2s shw-m250s Korean variant, with Villain 3.0 rom, and all functions worked fine. My unit is flashed with DCKL1 radio for "T" models and PDA I9100XXKI3.
Hi drummer, thanks for the feedback! Glad you like it and it solved a problem..
Sent from my Nexus S using xda premium
20 mio galaxy s2 sold !!!
http://www.engadget.com/2012/02/23/samsung-galaxy-s-ii-20-million/
And most of them missed this app ...still room to improve the numer of downloads
Hmm, still waiting for the official ICS rollout for my SGS 2 .....
Does anyone know which hidden touchwiz features still work on ICS ?
(LCD TEST, Test menu, Phone lock status etc. ????)
regards
ascsa
Yes, they still work, but not all. Cannot push your app to the phone to test right now, unfortunately. For example the LCD test works, but 8999 codes don't (taken from here).
VAXXi said:
Yes, they still work, but not all. Cannot push your app to the phone to test right now, unfortunately. For example the LCD test works, but 8999 codes don't (taken from here).
Click to expand...
Click to collapse
Hi vaxxi, thanks for your feedback!
I think the 8999 codes never worked on my SGS 2 .... like some other codes from the list ... so I think this is not a ICS related issue, but I could imagine that samsung removed some of the codes working on a 2.3.+ device ....
I have built Android 4.2.2 from AOSP and produce a working ROM. Currently there is no big problem and can be used as a daily driver. Please report in this thread if you encounter any problems.
Status
Working
Everything not in the not working list
Not Working
Gesture typing
Additional Features
USB OTG support
root access
Advanced quick settings (click to switch and long click to settings)
Advanced power menu
OTA update
Charging light (display settings)
Dynamically switching between phone and tablet UI (user interface settings)
CPU overclocking (developer options)
Downloads
My Android 4.2 for Xoom Wi-Fi (20130217)
my_wingray-jb-mr1.1-20130217-signed.zip
MD5: bb523abaf353d8ad06381f387f1c2a54
SHA1: b99513418a63dc20c7d26496b4370fad1598504b
Google Apps (20130221)
gapps-jb-mr1.1-noneon-20130221-signed.zip
MD5: 00d59870122baf6446b614daed347938
SHA1: 98d392876b2aa37f7e252eb354361be5dc371486
Issues
No obvious issues, please report in the thread if you found any.
Changelog
20130217
Update to Android 4.2.2
Fix mount point for USB storage
Improve I/O performance
Revert quick settings of status bar to stock
Remove GPS from quick settings of system bar
Hide developer options by default
20130127
Fix partition problem for some devices in Hong Kong and Taiwan
Enable Unicode support for FAT/NTFS filesystems
Add support for init.d scripts
Revert GPU overclocking for stability and battery
Revert I/O performance tweaks for stability
Merge hot word detection for Google Now into Google Apps
20130114
Fix layout of navigation keys with tablet UI
Fix notification prompt for multi-user support with tablet UI
Improve I/O performance
Enable NTFS read support
Move system bar setting to user interface settings
Add BusyBox
20130103
Fix default widget in lockscreen
Fix built-in clock widget in lockscreen
Fix available size in storage settings
Fix crash with unsupported video snapshot
Fix hot word detection with latest Google Search
Add setting for charging light (display settings)
20121227
Fix HDMI output
Fix volume change on docked
Fix OTA updates for compatible recoveries
Improve performance of graphics system
Add setting for dock audio
Support dynamically switching between phone and tablet UI
20121221
Fix multi-user support for Bluetooth
Fix multi-user support for quick settings
Fix duplicate IME swtichers on system bar
Fix clock quick settings on status bar
20121216
Fix notifications for multi-user with tablet UI
Fix icon on system bar when Bluetooth connected
Support OTA updates with OTAUpdater
Add Wi-Fi, Bluetooth and GPS switches
Use Simple I/O scheduler as default
Use new implementation for legacy hwcomposer support
20121209
Switch to stock kernel with overclock capability
20121207
Fix HDMI but included in unstable package
Fix settings for clock dream
Fix carrier info in lock screen
Fix music search
Support cpu freqeuncy scaling in developer options
20121130
Update to Android 4.2.1
Fix Wi-Fi and Bluetooth
Fix write access on SD card
Support USB storage
Keep Google Apps when flashing My Android
Switch to Superuser
20121125
Fix photo sphere camera
20121124
Switch back to stock keyboard
Installer and remover are provided for keyboard with gesture typing
20121123
Switch back to stock kernel
Fix null EGL config
Fix video chatting in Talk
Support switching between phone and tablet UI in developer options
Add Email app
Remove some unused stuff
20121119
Switch to Tiamat AOSP Kernel
Switch to keyboard with gesture typing
Add advanced power menu
20121117
Initial release
Source Code
Manifest for My Android
https://github.com/dreamcwli/android
Kernel for My Android for Xoom
https://github.com/dreamcwli/android_kernel_moto_wingray
Review (thanks to Freshly_Snipes)
Screenshots
downloading, will try and report! thanks!
Awesome.
Sent from my Galaxy Nexus using Tapatalk 2
everything running great here!
---------- Post added at 04:27 AM ---------- Previous post was at 04:08 AM ----------
if you need help or questions about any fixes, talk to mmuzy. I know its for the galaxy nexus, but I'm sure the bugfixes for aosp can translate over
Struggling to find issues with this, but it's only been an hour or so.
WELL DONE!!!!!!
Regards.
swimdude1120 said:
if you need help or questions about any fixes, talk to mmuzy. I know its for the galaxy nexus, but I'm sure the bugfixes for aosp can translate over
Click to expand...
Click to collapse
Since Galaxy Nexus is maintained in AOSP, it should work without fixing anything. Anyway I will build for Galaxy Nexus and test to see if it has any problems. Thanks for your suggestion.
Bugs And ISSUES
When I Get A Notification From Gmail The Sound Stutters and takes 10 seconds to complete Alot Of Apps Crash EX. Quadrant Not Sure If Rom ISSUE and homescreen is laggy is i no this is a very early build but there the bugs i have encounted
extremetempz said:
When I Get A Notification From Gmail The Sound Stutters and takes 10 seconds to complete Alot Of Apps Crash EX. Quadrant Not Sure If Rom ISSUE and homescreen is laggy is i no this is a very early build but there the bugs i have encounted
Click to expand...
Click to collapse
You can try to restart Wi-Fi as I describe in the issue list. I think there is something wrong with Wi-Fi and entire system resource is consumed. Restart Wi-Fi make it back to normal state.
installed
Thank you very much. I first started by installing 4.2 gapps on top of previous version of CM10. Worked pretty well. This is very nice. I will have to update all the software later in the day. So far all working.
Great work bro! Is it possible to make for the Xoom 3G MZ601?
Sound interesting, lets give this a try
Gesture input doesn't work for me.
Sent from my Xoom using xda premium
mongday said:
Gesture input doesn't work for me.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I have noticed this. Since I didn't see gesture input introduction on Nexus 10 page, I think maybe gesture input isn't available in large tablets by default. Will check this after finishing the essential part of this ROM.
Spherical camera force close for me.
Sent from my Xoom using xda premium
mongday said:
Spherical camera force close for me.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I forget to include some binary files in Google Apps, will re-upload it later. Thanks for your report.
Can not launch the Google now by saying "google" like the previous android version.
Sent from my Xoom using xda premium
dreamcwli said:
I have built Android 4.2 from AOSP and produce a working ROM. Since there are many small problems, I suggest using this ROM only for testing purpose. Please report in this thread if you encounter any problems.
Downloads
My Android 4.2 for Xoom (MZ604) (20121117)
my_wingray-20121117-signed.zip
Google Apps (20121117)
gapps-jb-20121117-signed.zip
Issues
* Wi-Fi not working on every boot after flashing Google Apps but fine if Wi-Fi is manually restarted
-- System becomes laggy if no manually restarting Wi-Fi on every boot after flashing Google Apps
* Some Bluetooth devices not working
-- Motorola Bluetooth keyboard not working for me
* Camera makes whole green pictures sometimes
-- This happends to me on taking first picture after flashing this ROM
Click to expand...
Click to collapse
Great ROM and congrats on being first. I am having trouble seeing my files and writing to internal storage after having flashed the ROM. On the storage section of settings I can see how much is used and how much I have left but the amounts quoted and what they are allocated to appear to be incorrect. Using file explore and or root explorer I can not see files or items stored to internal storage. Strangely however my pictures that I had stored to internal storage show up on gallery....!?
mongday said:
Can not launch the Google now by saying "google" like the previous android version.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I am not familiar with this, can you provide some information?
sibax said:
Great ROM and congrats on being first. I am having trouble seeing my files and writing to internal storage after having flashed the ROM. On the storage section of settings I can see how much is used and how much I have left but the amounts quoted and what they are allocated to appear to be incorrect. Using file explore and or root explorer I can not see files or items stored to internal storage. Strangely however my pictures that I had stored to internal storage show up on gallery....!?
Click to expand...
Click to collapse
Due to the multi-user support, the internal storage structure has changed. Generally speaking, data originally located under /sdcard have been moved /sdcard/<number> based on your current user number (started from 0). The storage summary shows storage size used by every user.
There is also another problem due to recovery. Currenty recovery wipe all content under /data excepts /data/media on factory reset. On Android 4.2, when system boots it checks if /data/.layout_version is existed. If not, it thinks user are updating from old Android version, and move content in /sdcard to /sdcard/0. If you factory reset several times, the content will move to /sdcard/0/0/.../0. ClockworkMod developers have made a workaround of this issue and hopefully every recovery will support Android 4.2 soon.
Great thanks for the quick response. Found all my stuff under the file marked 0 under sdcard .
Very good rom, gtalk video and sphere does not work: (, everything else perfect
I am new to PA (v6.03) running it on Sony Xperia Z2 (D6503) and chose it over the other roms because of the features it's celebrated for (Halo, Pie, super customization, etc). However, I cannot find any of this stuff in the settings, nor is there an app dedicated to these features that I can tell? All I see is a super stripped down version of Android. Which I definitely appreciate after using the bloated Sony version for nearly 2 years. But I want the cool stuff, where is it?? There are no questions on the net about this so clearly I'm an idiot, but help this idiot out, please! A guide, a pointer, something, Thanks!
Ok, for anyone else reading this thread and wondering the same as me, I found a guide on android authority as well as info on a bunch of other sites across the web, pm me for links.
But apparently Halo isn't what it was (declared dead by its own developers), it's basically now called "peeking" and doesn't have the floating notifications. You can still access the floating window features a few ways, so the meat of the feature survived to PA 6.03. Immersive mode, I found on my own, and was in the hidden elements in the quick settings. I had to tap on the add button to see options for immersive mode and floating peek. Once those were added to the shown quick options I could control immersive mode and peeking.
I tried the Floatifications app to get the halo style notifications back but it was clunky and annoying, so I uninstalled it. I'm just using the Halo app from the app store (which doesn't seem to do floating notifications at all, at least on Z2) and native controls to handle peeking, definitely not the glory days for that feature. As far as the customization-ability of PA I am extremely underwhelmed, after reading all the hype of previous versions. PA 6 is solid but it's an empty shell of it's former glory. I didn't even find the pie controls which are supposed to be part of immersive mode. I downloaded a third party pie controls app, it works but it's not pretty. I know a lot of people hate the pie controls but I'm finding it useful in clearing up real estate on my desktop, and not finding it at all in the way, as many complain about.
Anyway, I'm by no means an expert, only reporting what this PA newb is finding in my quest for knowledge. Definitely would like to hear what the experts here on xda think and know about PA 6, as I feel like I'm definitely missing something here, even after what I've found so far.
You're aware of what happened to the team right?
Several of the team went to work for OnePlus and some people quit working on the project altogether. It's mostly a new team with a few of the old members still hanging around working on what they can.
I still maintain the servers but the activity is all focused on creating a solid stable base to lay down features on top of.
As Android changes and matures, there are features that get left in the dust. Ideas progress and what was in a previous major version of PA, may not make it to the next version.
Pie hasn't been added back into the builds publicly and just because you have immersive mode doesn't mean pie is included.
Slim7
Samsung Galaxy Nexus (Unified)
[#WHATSSLIM]
Slim7 is the project name for SlimRoms based on Android 7.x Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
[#WARRANTY]
Download:
Unified tuna Slim7
[#DLGITHUBIO]
TWRP with hardware decryption support can be found here
[#INFOSLIM]
Disclaimer: SlimRoms are not responsible for any damages to your device.
[#DONATETOME]
XDA:DevDB Information
[unified] Slim7, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan, SlimRoms
Source Code: https://github.com/slimroms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2017-04-29
Last Updated 2017-08-18
Just uploading initial build, will be up in some minutes. Initial build uploaded.
First boot takes a while because i had to disable dex-preoptimization as it caused bootloop while connecting to WiFi.
Hello @Android-Andi,
first of all thank you for all you're doing to support tunas.
Here are two bugs I'm actually aware:
- green lines and artifacts previewing mpeg4 videos in gallery (just the static image, play them is OK)
- if you try to add a photo to owner profile in settings, phone reboots when saving image
Attached full boot logcat with both these bugs triggered.
Thanks again
yen
Tested on toro, working as expected. Meaning, everything works except mobile data for me. Behavior is exactly the same as Unlegacy 7, so no surprises there. I'm on Page Plus (a Verizon MVNO) and that complicates things sometimes. Still, I was hoping that maybe it would just magically work on Slim7. Oh well... Thanks anyway, it is a very sweet ROM!
It shouldn't complicate things at all
musical_chairs said:
Tested on toro, working as expected. Meaning, everything works except mobile data for me. Behavior is exactly the same as Unlegacy 7, so no surprises there. I'm on Page Plus (a Verizon MVNO) and that complicates things sometimes. Still, I was hoping that maybe it would just magically work on Slim7. Oh well... Thanks anyway, it is a very sweet ROM!
Click to expand...
Click to collapse
With PP now being a VZW MVNO, it shouldn't complicate anything (as long as your are running toro hardware). I took my toro to Tracfone (a split MVNO - between T-Mobile and VZW), and went specifically to the VZW side of things (two reasons - T-Mobile has always had signal issues here - or anywhere else, and VZW has Just Plain Worked - I'm a former VZW prepaid customer). Page Plus used to be a pager AND cellular service provider - with their own towers. I'm running Slim 7 beta because I wanted an SELinux enforcing ROM that ran N on my hardware; so far, Slim 7 is the only such. Even Lineage OS 14.1 (also unofficial) dropped back and punted to permissive - not enforcing. I won't touch MM with a ten-foot pair of chopsticks because performance bites compared to N on toro.
Followup - Slim 7 is now updating apps - all 77 of them from a previous ROM. Even better, for the first time on N, SafetyNet works (nothing broke it). I ran into a solvable problem with Android Pay, though - my VISA debit card doesn't support it (Android Pay, that is); rather amusingly, it DOES support VISA Checkout. Fortunately, that means that all I need to find is a debit card that DOES support Android Pay - time to warm up my Google-fu. (As expected, the Google-fu paid off; two banks near me have multiple branches where I can apply (and even pick up) a prepaid card on the spot - PNC and Wells Fargo (AKA Stagecoach Bank), and their prepaid cards are SPECIFICALLY supported by Android Pay. Rather oddly, a whole lot of prepaid cards are specifically denied - and from BIG banks, at that - CITI and AMEX tell their prepaid clients to hold the phone/phablet/tablet and don't even bother to try their prepaid cards. In addition to PNC and Wells, Bank of America says "si" to prepaid and Android Pay - the minus (for BOfA) is that they aren't the closest bank branch - rather amusingly, the closest bank branch where I can get a prepaid card used to be, in fact, a BOfA branch - it was acquired by PNC when BOfA did "the great branch thindown" in several states - and I don't live in either North Carolina (the current HQ of BOfA) or San Francisco (the historical beginning of BOfA and, interestingly, what is now VISA USA (originally BankAmeriCard).
PGHammer said:
With PP now being a VZW MVNO, it shouldn't complicate anything (as long as your are running toro hardware). I took my toro to Tracfone (a split MVNO - between T-Mobile and VZW), and went specifically to the VZW side of things (two reasons - T-Mobile has always had signal issues here - or anywhere else, and VZW has Just Plain Worked - I'm a former VZW prepaid customer). Page Plus used to be a pager AND cellular service provider - with their own towers.
Click to expand...
Click to collapse
There used to be no difference between the settings for PP and VZW, but on October 31, 2016, Page Plus switched from Verizon's APN to Tracfone's APNs. This 'should' get updated automatically in our phones., but it doesn't because something is broken between our old RIL and any version of Android newer than KitKat. So it may be possible that data could 'just work' for a standard VZW activation yet be broken for me.
I never knew PP did anything other than re-sell VZW, that is interesting.
musical_chairs said:
There used to be no difference between the settings for PP and VZW, but on October 31, 2016, Page Plus switched from Verizon's APN to Tracfone's APNs. This 'should' get updated automatically in our phones., but it doesn't because something is broken between our old RIL and any version of Android newer than KitKat. So it may be possible that data could 'just work' for a standard VZW activation yet be broken for me.
I never knew PP did anything other than re-sell VZW, that is interesting.
Click to expand...
Click to collapse
I'm on the VZW half of Tracfone; hence it mattering exactly diddly. In fact, the reason it doesn't matter for me as that I use mostly wi-fi for data (as I don't exactly have a high-cap data plan with Tracfone) - instead, I use wi-fi for data. Do you have cable-TV? Check to see if your cable-TV provider has a connection to a network of hotspots. (Comcast XFINITY, Cox Communications, and Spectrum have the Hotspot Network - literally, a network of hotspots which customers of all three cable TV companies can access via login from their respective apps (available on Google Play). The Android APKs (also available for iOS devices) work on any Android device - I have Comcast's version of the app on both my phone AND my tablet - it was on my tablet first (since I've had it longer than my phone) - and my tablet is NOT a phablet. SMS and MMS can be used over wi-fi as well; you just can't use Google Hangouts (as it doesn't support wi-fi). However, Google Messenger does - which is why it's on my tablet. (Rather amusingly, VZW Message+ can be used over wi-fi as well - it's also available on Google Play - at a cost of nil.)
As far as things being broke in the transition, that's on PagePlus - not you, and not even Tracfone, either.
I came back to post yet another followup - Magisk 12 DOES work on Slim 7, as does both Masisk SU for root (and Magisk Hide, to handle SafetyNet breakage due to being rooted).:victory::victory::victory:
I have uploaded a 2nd build silently which contains ffmpeg support (previous build was missing a small part). @musical_chairs yeah, i already thought Verizon still has broken mobile data here too, maybe we'll find a solution later.
PGHammer said:
Even better, for the first time on N, SafetyNet works (nothing broke it).
Click to expand...
Click to collapse
Very interesting, not only because safetynet works on @Android-Andi build but because it works also in my Slim7 home builds when it instead fails in UA7 builds. Both my builds are userdebug and uses the same UA staging kernel, so safetynet failure in UA7 seems not related to kernel or build type... any idea someone?
Sorry for OT, bye.
yen
Thanks, the only thing I've noticed is some artifacts on the edges of the boot animation. Didn't notice them on first boot but maybe I wasn't paying close attention.
Oh, and night light doesn't work but I think that's an issue with unlegacy. Cf.lumen only works in nonroot mode as well.
Feels snappier than the Dirty Unicorn builds too.
Thanks for this Andi.
I too saw the artifacts on the boot animation, but this will serve nicely as a backup car music player.
I wouldn't be able to test mobile data until my Verizon G4 bootloops.
I'm trying Substratum. I can apply themes per-app with the FloatUI, but when I try from the main interface it fails and fc, so some important system elements cannot be themed.
EDIT: tried versions 703 and 706
Nonno Cicala said:
I'm trying Substratum. I can apply themes per-app with the FloatUI, but when I try from the main interface it fails and fc, so some important system elements cannot be themed.
EDIT: tried versions 703 and 706
Click to expand...
Click to collapse
That's because slim roms haven't merged OMS commits AFAIK.. you will see "substratum legacy" on app, that means you can't theme system elements, or it will end in bootloop or force close failures.. theming any user apps will be fine..?
____Mdd said:
That's because slim roms haven't merged OMS commits AFAIK.. you will see "substratum legacy" on app, that means you can't theme system elements, or it will end in bootloop or force close failures.. theming any user apps will be fine..
Click to expand...
Click to collapse
Substratum says this ROM uses OMS7.
And I think it does because with the FloatUI I can change the theme per-app on the fly, without rebooting as I had to do with stock MM in the past.
Slim is missing the ThemeInterfacer. I tried to add a pre-built ThemeInterfacer.apk (v.50), it was recognised but didn't work.
Nonno Cicala said:
Substratum says this ROM uses OMS7.
And I think it does because with the FloatUI I can change the theme per-app on the fly, without rebooting as I had to do with stock MM in the past.
Slim is missing the ThemeInterfacer. I tried to add a pre-built ThemeInterfacer.apk (v.50), it was recognised but didn't work.
Click to expand...
Click to collapse
In my case,
All overlayers got installed without any errors and without themeinterfacer, but no changes took place, nowhere, not even in user apps, in substratum app it shows "up to date" but nothing change.. then tried floating button and most of apps got themed and some system elements too (without FC or any errors)...
PS. When nothing got themed then i added interfacer and then tried floater...
____Mdd said:
In my case,
All overlayers got installed without any errors and without themeinterfacer, but no changes took place, nowhere, not even in user apps, in substratum app it shows "up to date" but nothing change..
Click to expand...
Click to collapse
Same here, but if you try to enable an overlay from the "Overlay list", under Utilities, Substratum will fc.
____Mdd said:
then tried floating button and most of apps got themed and some system elements too (without FC or any errors)...
PS. When nothing got themed then i added interfacer and then tried floater...
Click to expand...
Click to collapse
After I tried to add ThemeInterfacer Substratum detected it but couldn't install any overlay any more, so I removed it.
It seems that we see the same things. My problem was that I like black themes, so with just some system elements themed I found myself with white text on white background somewhere, and black on black somewhere else. Since FloatUI just let you set overlays for current elements I didn't know how to let it select some important missing elements. But I found a workaround for the SystemUI and QuickSettings: disable SlimRecents and use the FloatUI in the stock Recents menu!
I've also been able to select Google Play Services from the Google Settings.
Now I'm satisfied with my theme.
Didn't even know nougat was possible for GNex. This is pretty sick. Question... Any way to do a Toro version? Cheers!!;
The Doctor04 said:
Question... Any way to do a Toro version? Cheers!!;
Click to expand...
Click to collapse
Same as @phaleg answered you in the Unlegacy thread:
phaleg said:
It's unified project for all tunas (maguro, toro and so on)
Click to expand...
Click to collapse
Just got this downloaded now and going to give it a spin. I am not using data, as I primarily let the kids use this device to play games, take pictures, etc. The fact that we can get the latest and great android working on a 5 year old device is just awesome. If I see any issues other that what is reported I'll post back. Big thanks!!
Had some trouble getting Google Play Services to work. Reflashed ROM and GApps, and it fired right up after that. So far everything is running as it should. I put an old Verizon sim in the phone to see if it would at least recognize Verizon, and it did. Device is very smooth and the animations are crisp/work as they should. I do notice a little bit of lag swiping up for unlocking the device, and then it takes a second to get into the device after I enter the pin. Other than that, this is pretty dope. Battery charged fairly quickly too. I'll have the rug rats put it through the paces when I get home tonight, but excellent, excellent work!
xda-developers
[https://secure-gravatar-com]*Mishaal Rahman
1 day ago
Categories:*Developments,*Featured,*Full XDA,*News,*XDA Feature
Tags:*Android Oreo,*emui 6.0,*Huawei Mate 9
Yesterday’s Google event finally brought us the*Google Pixel 2 and Pixel 2 XL, the*Pixelbook, and the*Home Mini/Max*but even though the Google fervor is now dying down, there’s still much for Android enthusiasts to look forward to in the coming weeks. The mighty*Huawei Mate 10*will soon make its debut on October 16th at a press event in Munich, Germany, and it will be the first public look we will have on Huawei’s upcoming EMUI 6 based on*Android 8.0*Oreo. Ahead of this event, we have obtained access to a*pre-release firmware build of*Android Oreo/EMUI 6 for the*Huawei Mate 9, and there are quite a few interesting changes to note for this upcoming update.
The Huawei Mate 9 was unveiled in*only November of last year*with*top-tier*hardware specifications, so it’s unsurprising to see this device receive an Android Oreo update. There were hints of early work being done on an Android 8.0 update*even as far back as April*of this year, though the build that was leaked at that time was fairly barebones. Now, the build that we have obtained is fully functional and can actually install right on top of MHA-L29C432 (the international Huawei Mate 9 variant) so we did just that to start digging in to what’s new in the EMUI 6 update.
EMUI 6 based on Android Oreo for the Huawei Mate 9
The Things You Would Expect
For starters, let’s get the uninteresting details out of the way. As you would expect, most of the required Android Oreo features are available in this build. That means picture-in-picture mode support, the*strict background app limitations, notification channels, and even that annoying “app is running in the background” notification that you can*thankfully still hide using an app.
[https://www1--lw-xda--cdn-com]
[https://www1--lw-xda--cdn-com]
We should note that although Huawei implemented notification channels, their notification importance controls is actually a holdover from EMUI 5 and not based on the AOSP version that you may be familiar with. I see this as a boon because it means you don’t need a third-party app to*bring back notification importance controls for apps that don’t target Android Oreo.
EMUI 6 Updates
Here is where things get a little bit more interesting. Overall, I would say there aren’t many changes between EMUI 5 and EMUI 6 on the surface, but there are a few new software additions that should make some people happy.
First up, there is a new “screen resolution” option in display settings. This builds upon EMUI 5’s dynamic screen resolution feature called “smart resolution” (which is also present in EMUI 6). While smart resolution would automatically switch between 720p and 1080p in order to conserve power, this new option allows you to manually change between the two resolutions. This method likely beats using the*ADB*“wm size” command, as that ADB command only adjusts the virtual resolution rather than actually having the display render at a lower resolution.
Next, there is a new button that can be placed on the navigation bar. When the button is enabled, it adds a small arrow to the left side of the navigation bar. Pressing this button will temporarily hide the navigation bar until you swipe up from the bottom. For those of you who like having the stock navigation bar but want to occasionally make use of the full-screen real estate on-demand, this new button beats the ADB command that*permanently hides the navigation bar*or*enables immersive mode. This button isn’t technically new as it is present on the Chinese Huawei Mate 9 firmware, but it’s new to the international variant.
[https://www1--lw-xda--cdn-com]
[https://www1--lw-xda--cdn-com]
If you aren’t a fan of the software navigation bar, then there is another new navigation option available for you to try. It’s called*navigation dockand what it does is it places a movable floating button that can replace the navigation bar for all back, home, or recent button presses. This is distinct from EMUI 5’s “floating dock” as that feature acted like a pseudo-pie control wherein pressing the button would expand a list of available navigation options. EMUI 6’s navigation dock instead uses gesture controls such as slide up to go home, slide right for recents, and touch to go back.
[https://www1--lw-xda--cdn-com]
[https://www1--lw-xda--cdn-com]
Lastly, in developer options, there is something strange that we found. The usual*Bluetooth audio codec customization*features are present, as is the ability to switch between various Bluetooth audio codecs—including*aptX*and aptX HD. aptX and aptX HD are proprietary Bluetooth audio codecs that are owned by Qualcomm, so companies that wish to use them must pay licensing fees to Qualcomm.
[https://www1--lw-xda--cdn-com]
[https://www1--lw-xda--cdn-com]
We’re not sure why Huawei even made it a selectable option as it doesn’t even work here (picking either of these options simply reverts the selection back to SBC), but then again this*is*a pre-release build so it’s possible these options will disappear in the final release. Perhaps with root access and a*Magisk*Module we can enable support for it much like*Google Nexus 6P*owners can.
Under-the-Hood Changes
You might be wondering by this point why we haven’t yet shown a screenshot of the “About Phone” section. That’s because, like every beta/testing build that Huawei releases internally, the software version is changed to mitigate leaks. Fortunately, it’s rather easy to verify the true software build by taking a peek at the build.prop file. In it, we can see that the following:
[ro.build.version.security_patch]: [2017-09-05] [ro.build.version.release]: [8.0.0] [ro.build.version.sdk]: [26]
and from a separate command, we can find the Linux kernel version
Linux version 4.4.23+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Sep 14 04:10:43 CST 2017
So, it’s pretty clear from this information that the Huawei Mate 9 build we have obtained is indeed based on Android 8.0 Oreo (SDK level 26). The*Linux kernel version is 4.4, updated from 4.1 in the Nougat-based EMUI 5 on the Mate 9. Furthermore, the security patch level is September 2017 which means that the Mate 9 is*safe from the Blueborne vulnerability.
Finally, there are a few things we discovered that are especially interesting to Android enthusiasts. First,*Project Treble*support is there. Though the*kernel sources for the Mate 9*have been available for several months, there aren’t any custom AOSP-based ROMs available for the device.*Maybe Project Treble support will change that, maybe not. This is still interesting as it is the*first confirmed device that has Project Treble support even though it did not launch with Android Oreo.
Last but not least, here’s a thing that nobody expected to happen:*Substratum*support in EMUI. Yes,*Substratum themes work on EMUI 6. This is all thanks to the Overlay Manager Service (OMS) commits that Sony made to AOSP that have finally made their way in a fully working state in Android Oreo. It’s thanks to this that Google Nexus and Pixel users are able to*enjoy full custom theme support*using the*Andromeda add-on for Substratum. We tested both the*command line interface*as well as a*dark theme*in certain apps and can confirm it does indeed work.
[https://www1--lw-xda--cdn-com]
[https://www1--lw-xda--cdn-com]
Substratum support may not seem as interesting at first glance since Huawei already has its own theme engine, but it should be noted that Substratum will allow you to theme more than just system applications as can be seen in the above screenshot of the Google Messenger application.
That’s all we’ve discovered in this internal, beta build of Android 8.0 Oreo for the Huawei Mate 9. Stay tuned to the XDA Portal as we have more to share about upcoming Huawei and Honor devices. The best way to follow the Portal is by installing the*XDA Labs*application!
The firmware was provided for me to install on my Huawei Mate 9 by*FunkyHuawei.club, a service which lets you install pre-release Huawei firmwares, recover bricked devices, and rebrand/convert China region phones to international variants. The service will support the Mate 10 upon release.*
Sent from my BLN-L22 using Tapatalk
It's not very ideal to copy and paste a portal post.
chrisleLP said:
It's not very ideal to copy and paste a portal post.
Click to expand...
Click to collapse
why im not making any sort of money from it
just to share
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
why im not making any sort of money from it
just to share
Click to expand...
Click to collapse
I mean, you can edit it to make it a little shorter or maybe you can put like, "[SHARE]" to the tags. Even "1 day ago" and other unnecessary things were included in your post.