Database Info

Torch Mobile Iris Browser v1.1.3 for Windows Mobile 5/6 (Updated 02/25/09)

There are many surprises waiting inside, including support for the Flash Lite ActiveX control, big performance gains, reduced memory usage, preliminary RSS and SVG support, the highest Acid3 score of any shipping mobile browser, and HTC accelerometer support.
Click to expand...
Click to collapse
Source: http://www.torchmobile.com/blog/?p=18
Download Link: http://www.torchmobile.com/download/ (You're only required to provide a name and email address for download)
If you've tried it before, give it another chance as they've been making improvements. I would best describe this browser as what Fennic beta/alpha should have been.
It's based on the WebKit rendering engine (same engine used by Safari and iPhone browsers). It's a later version of WebKit since it gets further in the ACID 3 test (100/100) than the release versions of those browsers, and much further than any other Windows Mobile browser. So it's a good choice for those heavy CSS/Javascript web pages.
For the full feature look here:
http://www.torchmobile.com/products/iris.html
Here's a video of Iris in action on Windows Mobile:
http://www.youtube.com/watch?v=KpX5JZWtu-g
Here are my observations:
Pros:
Free
Fairly fast
Very standards compliant (100/100) on Acid 3 tests
Native support for HTC Touch Pro/Diamond accelerometers
Direct, doesn't go through a proxy like Opera Mini or Skyfire (which is good if you're paranoid about security/proxy availability)
Tabs
Can simulate a mouse cursor in "Mouse Cursor" mode
Downloading support, though did silently crash once when trying to download Google Maps cab
Cons:
Can't figure out how to copy/paste text.
No text reflow/reformat on zoom-in like Opera Mini and certain versions of Opera Mobile 9.5
Extremely basic UI, every function has to be accesed through menus which gets kind of clunky
Zooming is clunky, zooming in more than one level/accessing the URL bar requires you to go through the menu system
Getting Flash Content to Display:
(From PPCGeek's member Torx)
Install Juggalo Flash CAB (attached) into main memory (if you don't already have Flash Lite 3.1 installed).
Unzip NPFL3ppc.zip (attached) and copy NPFL3ppcdll into the \Program files\Iris Broswer\plugins folder.
Restart Iris, and Flash content will be replaced with a black box and play button. Press the play button to play the Flash content!
Note: YouTube videos seem to display, but not play, other embedded Flash content works.
Additional Notes
Reports of some HTC Touch Pro (aka Fuze) and Diamond phones freezing. They believe this is due to a driver bug on the phone and they are working on a workaround. Please check their blog for updates.
http://www.torchmobile.com/blog/
Tip: Tap and hold link to go to visit links and give focus to certain form fields (checkboxes/textboxes).
Changelog
v1.1.3 (Updated 02/23/2009) - Touch Pro (Fuze), Diamond Users (maybe) Rejoice! It appears that while this fixes the problem for some users, it doesn’t fix it for all. We’re continuing to search for the problem and will post another update soon.
Other fixes/changes include:
Plugin (like FlashLite) interaction fixes
Animated GIF fixes
Re-activation of an optimization for some JavaScript intensive sites
Many editing bugs are fixed (yes, you can blog with it again!)
All known and reported crashes are fixed
Improved memory management for large images
Minor canvas improvements
Performance improvements, including 12% faster JavaScript
Source: http://www.torchmobile.com/blog/?p=20
v1.1.2 (Updated 02/20/2009) - Contains numerous fixes including one for low-resolution devices, several crashes, text shadow, some potential Touch Pro / Diamond freezes, and problems with some iPhone libraries.
Finally, we’ve done a lot of work to make sure we’re really one of the most compliant, precise, and high-quality rendering mobile browsers. We now score 100/100 on Acid3 with only a couple of minor rendering glitches. Those happen to be related to fonts, where we deliberately cut some corners for better performance. It’s not likely we will eliminate those glitches anytime soon. Iris Browser is also highly compatible with the popular iPhone websites, making it a great alternative for those who prefer other devices. We think the approach we’ve taken strikes a great balance between performance and functionality, and we’re just getting started!
Source: http://www.torchmobile.com/blog/?p=19
v1.1.1 (Updated 02/17/2009) - Fixes some reported problems with the Diamond/Touch Pro (check the comments section of the blog entry above for more information).
Source: http://www.torchmobile.com/blog/?p=18#comment-71

Thanks for the update
I've been using Iris for awhile and I'm very happy with it. I'm eager to see what improvements they've made.

wow, this is really a nice update.
I was using 1.0.6 and though it was nice (using iphone optimized versions ) it was a bit buggy. this new version is a lot better!

Bump for v1.1.2 update, and instructions on how to get flash to work.

Have a look at Zinio with Iris
If you don't know, Zinio.com is a site where you buy and view digital magazine subscriptions. Doesn't usually work with WM. Meh. But . . browse there with Iris, look under Zinio Labs, and tap IPhone. You now can read a bunch of FREE magazines on your phone, zooming and panning at will. I could not believe the selection. I could'nt look at these for free on the PC even, but if they think you have a JeebusPhone, they throw free stuff at you.
Anyway, Ithought it was cool, and hope you will too.
Webkit FTW!

TalynOne said:
Source: http://www.torchmobile.com/blog/?p=18
Install Juggalo Flash CAB (attached) into main memory (if you don't already have Flash Lite 3.1 installed).
Unzip NPFL3ppc.zip (attached) and copy NPFL3ppcdll into the \Program files\Iris Broswer\plugins folder.
Restart Iris, and Flash content will be replaced with a black box and play button. Press the play button to play the Flash content!
Note: YouTube videos seem to display, but not play, other embedded Flash content works.
Click to expand...
Click to collapse
Where are these attached flash cabs?

v1.1.3 released
v 1.1.3 is now released.
Source: http://www.torchmobile.com/blog/?p=20
Fixes include:
* Plugin (like FlashLite) interaction fixes
* Animated GIF fixes
* Re-activation of an optimization for some JavaScript intensive sites
* Many editing bugs are fixed (yes, you can blog with it again!)
* All known and reported crashes are fixed
* Improved memory management for large images
* Minor canvas improvements
* Performance improvements, including 12% faster JavaScript
And some fixes for Touch Pro/Diamond users.
Seems like there's still some bugs there, but it's improving with every release. At least it's quite usable these days.

Thanks willl, OP updated.

TalynOne said:
Thanks willl, OP updated.
Click to expand...
Click to collapse
Cool! I've also linked to your thread from my latest Web browsing article (see http://forum.xda-developers.com/showthread.php?t=485315 )

They've just posted a new "Under The Hood" post on their blog for anyone who's interested.
They posted some interesting benchmark results using SunSpider:
* Access NetFront 3.5 2388.7s
* Opera Mobile 9.5 (built-in) 219.0s
* Pocket IE (built-in) Unable to complete
* Iris Browser 1.1.2 115.0s
That said, benchmarks run by vendors sources should always be taken with a grain of salt!

Tried out iris and liked it overall. As mentioned above, the lack of text reflow is unfortunate. One thing that hasn't been mentioned is I found it difficult to click on links. Either I'm doing something wrong, or you have to press and hold for a second to click a link. If you just tap the screen quickly, as I normally do in all other browsers, it doesn't register with iris. This must have something to do with how the browser differentiates between scrolling and clicking?
In any case, I plan to keep it installed, as it's nice to be able to flawlessly access the iphone versions of sites like facebook and gmail. However, for most of my browsing, I'd rather use opera mobile, or even better, opera mini. I like speed!
-Ben

You are right. To activate a link you have to kind of press and hold for a moment. This does not bother me too much but the problem of no proper text reflow is what is preventing to make this my daily use browser. If this is sorted out I am sure this will be my primary browser.
Regards

Well, with a non-touch screen phone you have no such problems
Joking aside, they've released another new version (1.1.4).
Which includes the following changes/fixes:
* Fixes for zoom scale
* Performance improvements in various areas
* Fixes for some EUC-JP encoded sites, other encoding fixes
* JavaScript fixes for some sites
* Rendering artifacts fixed on some dynamic sites like Google Reader iPhone edition
* All reported crashes fixed (potentially also the HTC Touch Pro/Diamond freezes some users still see)
* Minor improvements to the key configuration for Smartphone Edition
* Some additional registry keys to disable or override behavior, including backlight keep-awake, animations
* Check box to disable automatic zoom to fit
* WebFonts, resulting in “pixel perfect” Acid3 rendering
Also, if you have bug reports, send them an email with reproducible steps - feedback-wm [at] torchmobile.com (replace [at] with @).

Thanks for the info
Just updated.
Initial impressions: Big improvement in page loading speed, and in response to screen taps.
Nice update

great application! thks for info, 4 updating...

v1.1.5 Update now available
Almost seems like, another day another update! At least you know they are actively developing the app. I think it's actually quite usable as is, but improvements of minor bugs/quirks is always nice.
This time it's another minor bug fixes/performance improvements.
From their blog:
Iris Browser 1.1.5 for Windows Mobile was released today. As with all 1.1.x releases, this release is focused on bug fixes and performance enhancement. Some highlights include:
* Noticeably faster scrolling
* Up to 25% improvement in page load time
* Improvements to text input
* Rendering and layout improvements
Click to expand...
Click to collapse
To update your version of the browser select the Page menu > Options > Preferences
Then click on the last button that says "Check for update". It'll then check for the latest updates and if a new version is found will update you to the newest version.
The OP probably needs to be updated again

Wow, new updates are happening quite fast now.
It's up to v1.1.6 now.
# Performance improvements
* Some pages load up to 25% faster
* Scrolling performance improved
* Painting speed improved
# History fixes
# New registry flag to control the minimum and maximum zoom levels - use at your own risk!
# Zoom scheme changes based on user requests and bug reports
# Some site specific fixes
# EUC-KR support improvements
# Some hidden features
Click to expand...
Click to collapse
To me, at this stage the browser is quite usable/stable for most of my needs. But unsure if it'll ever be my "default" browser. I still use PIE for a few things here and there, as well as Opera Mini.

The latest version of this software (as of apr 1st) is awesome!
-mark

They really have to work on at least two things: Text flowing and easier zooming.
The way Opera 9.5 does zooming makes sense to me.. Double-tap and it zooms a bit, if you double tap-hold it seems to zoom in farther. If you double-tap when zoomed in, it zooms out. Plus there is the zoom tool on the screen, and some versions you can use the volume wheel to adjust zoom.
Zooming on Iris is painful. For me it seems like the only zooms that are useful are 50% and 100%. 50% is easy to scroll around and find stuff, but not interact or read it, and 100% is too large. Hopefully they'll sort this sort of thing out soon.
Otherwise, it seems to scroll pretty well, haven't noticed it "bounce around" like Opera does (scrolling down a page, suddenly it ZOOMS off some random direction) but the font rendering at <100% is pretty poor. Seems I can read the unzoomed text in Opera and not have to zoom in quite as far.
Launching links works fine for me, although I think they need to document how to do it somewhere. IS there documentation anywhere? In Opera I all-too-often accidentally re-zoom rather than open a link, Iris it seems to be very consistent.
So there are rough edges, but generally it works pretty decent. I haven't used it extensively yet, just looked at the rendering of a few of my own websites and such. I'll give it a 'real world' test sometime on this forum and some other complex websites.
Oh, built-in updating is nice too. Skyfire is a pain to update, although honestly I like Skyfire less and less so it's not really a big deal. I'll still probably use PIE as my default as it launches instantly and it works as a general purpose browser. But I have a mortscript which opens the current PIE URL in Opera, I'll have to update it for Iris now.

with adobe lite 3.1, youtube works.
video a bit choppier than my E71 (symbian s60), but still works, and audio is smooooth... this is on my treo pro, wm 6.1
THANKS!!

Good New's cupcake" development branch Merged to The master project

The changes introduced in the cupcake branch have been merged into the master branch, preserving all of the previous commits to master. The same will happen for each future drop to cupcake.
So soon you will can use the video recording ,Stereo Blue tooth ,etc ....
Applications
* MMS
o New features
+ Save attachments from MMS.
o Significant bug fixes
+ Faster conversation list scrolling
* Email
o Significant bug fixes
+ Accounts that were marked "never check" are not auto-checked.
+ Date & time displayed using user preference (e.g. 24 hr vs. AM/PM).
+ cc: displayed in message view.
+ Relaxed POP3 parser rules so it works with non-compliant email servers.
+ Password quoting bugs in IMAP. Makes it work for users with funny chars in their password (e.g. spaces).
+ Various sources of errors in auto & manual account setup.
+ Improvements on how we report various connection errors. Makes it much easier for user to diagnose failed account setups.
+ New-mail notifications for POP3 accounts.
+ Properly recover from POP3 connection failures, so that the next connection has a chance of working properly.
+ Remove automatic accounts setup entries that were broken or not testable. Minor fixes to a few of the remaining entries. Improvements to warning dialogs used for a few special cases.
+ New accounts are now set to check every 15 minutes (instead of defaulting to "never").
+ Fixed a bug causing approximately 1 in 25 outbound messages to freeze up the IMAP connection (to a Gmail based server) when transferred to the Sent folder. This broke the entire connection so new messages could not be downloaded either.
+ Unit test framework so Email can be extended & tested more reliably.
+ Fix IMAP manually-created accounts so message delete works properly.
* Alarm Clock
o Significant bug fixes
+ Alert now plays audio/vibe directly, rather than through AlarmManager. AlarmClock alert starts playing audio/vibe in its IntentReceiver, rather than on activity start. These changes should prevent alarms from being blocked by modal dialogs.
* Package Installer
o Significant bug fixes
+ Bugs related to replacing existing applications.
* Settings
o New features
+ New menu option to list running processes in Settings->ManageApplications.
* Music
o New features
+ Music playback fades in after suspending for phone call.
+ New media search intent allows for 3rd party apps to launch or respond to media searches based on artist, album, or title.
Affects: Music Player, YouTube, Browser applications.
* Browser
o New features
+ Updated WebKit browser core, synced with Nov 2008 WebKit version.
+ Support for new, optimized JavaScript engine (SquirrelFish).
+ Copy / paste is enabled in the browser. To copy with touch, press and hold the shift key and select the text. Releasing the shift key or ending the touch drag copies the text. To copy with the trackball, press and hold the shift key, move the cursor to the selection start, click the trackball, and move the trackball to the extend the selection. Releasing the shift key, or clicking the trackball a second time, copies the text.
+ Find is enabled in the browser. To find text, choose it from the menu and type the text to find.
+ Drawing has been sped up substantially by supporting partial content invalidates and partial screen invalidates. Pages with animations are 5x faster.
* VoiceDialer
o New features
+ VoiceDialer supports 'open app' command
* Camera/Gallery
o New features
+ Video recorder mode
+ Share intent for videos
+ Video thumbnails
+ Local file playback
Download manager
* New features
o Support for HTTP codes 301, 302, 303 and 307 (redirects).
o HTTP code 503 is now handled, with support for retry-after in delay-seconds.
o Downloads that were cleanly interrupted are now resumed instead of failing.
o Applications can now pause their downloads.
o Retry delays are now randomized.
o Connectivity is now checked on all interfaces.
o Downloads with invalid characters in file name can now be saved.
Framework
* New features
o Support of touch events in WebView.
o New JavaScript engine (SquirrelFish) in WebView.
o Input method framework, for soft keyboards and other on-screen input methods. Includes new APIs for applications to interact with input methods, and the ability for third party developers to write their own input methods.
o Access to the raw audio data for playback and recording from application code.
o New PendingIntent.FLAG_UPDATE_CURRENT option.
o Support for top-level boolean resources.
o Tactile feedback to the LockPatternView. Tactile feedback can be enabled/disabled by going to Settings > Security & location and then checking/unchecking "Use tactile feedback". Note that this can be used independently of the visual feedback of the lines ("Use visible pattern"). Thus it gives users a middle ground between showing the lines on the screen and having no feedback at all.
o PackageManager changes to support un-installation of partially installed applications. Added new flag PackageManager.GET_UNINSTALLED_PACKAGES to include partially installed apps in all relevant PackageManager api's. ManageApplications screen now lists such partially installed apps and the user can uninstall these applications completely.
o Support third party updates of system applications. New menu options in Settings->ManageApplications to list updated system applications.
o Framework support to list current running processes. New API in ActivityManager.
o Framework feature to declare required configurations by applications. New manifest attribute uses-configuration in android manifest.
o Hardware accelerated video encode (video recorder) in opencore.
o Simplified SREC speech recognition API available.
o Streaming audio I/O for applications.
* Significant bug fixes
o Fixed issues with saving state in the view hierarchy, so that you can properly subclass from something like TextView and create your own state that inherits from that provided by TextView.
o TextView now implements onKeyMultiple(), so that flinging the trackball will result in accelerated scrolling. This required some changes to movement methods, and included some improvements to the acceleration computed when flinging.
o Framework bug fixes in PackageManager to share/un-share permissions for applications with shared uid's.
o Significant rework of Settings->ManageApplications Performance and UI enhancements.
o A number of settings in android.provider.Settings.System were moved to android.provider.Settings.Secure. Only system software can modify these settings. Additionally, a new permission, WRITE_SECURE_SETTINGS, is required to access these settings. The old constants in Settings.System have been deprecated. It is possible to read settings values via Settings.System using the deprecated constants. However, attempts to modify these settings via Settings.System will result in a log message and the setting value will be left unchanged.
o Many bug fixes in the media framework
Bluetooth
* New features
o Support for A2DP & AVRCP profiles.
* Significant bug fixes
o First connection after pairing always fails on many carkits.
o Mini Cooper and some late model BMW cars fail to use Bluetooth or take 2 minutes for Phone Book transfer.
System software
* New features
o New kernel based on Linux 2.6.27.
o Improvements to the wakelock API.
o Work to transition to the USB Gadget Framework underway.
o Basic x86 support.
Radio & Telephony
* New features
o SIM Application Toolkit 1.0.
o Green CALL button is no longer a shortcut for "add a new call". This has been a rarely used feature and confusing if triggered accidentally.
o Longer in-call screen timeout when using the speakerphone.
o "Show dialpad" / "Hide dialpad" item added to the in-call menu, to make it easier to discover the DTMF dialpad.
* Significant bug fixes
o An obscure case where the Phone UI could cause the device to not go to sleep on its own. This would happen if user bails out of the in-call screen by hitting HOME, followed by the call disconnecting remotely.
o Don't allow a single tap to open the in-call dialpad. It is now required to touch and drag it. This makes it much harder to accidentally open the dialpad by touching the screen with your face.
Build System
* New features
o The functions in build/envsetup.sh should be much more useful

wait, this sounds great? but what are the implications really?

i know one of the big worries I had regarding this was support for previous applications, etc. It sounds like by the comments at the beginning about preserving all previous commits, full backwards compatibility won't be an issue.
Sounds good. Just push it to my G1!!!!

Bluetooth
* New features
o Support for A2DP & AVRCP profiles
like this feature can bluetooth with a2dp

you know that merged it a few months back right?

i was about to say, what kind of deja voo is going on here.

"Work to transition to the USB Gadget Framework underway"
means there is possibility of android having support for usb peripherals. that would be amazing..

Yeah, but apparently Google has transformed into just a couple of people.
"xmoo,The Source,Haykuro, and barakinflorida".
They are the only ones bringing us cupcake right now.

{
"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"
}

TuXeyM11 said:
Yeah, but apparently Google has transformed into just a couple of people.
"xmoo,The Source,Haykuro, and barakinflorida".
They are the only ones bringing us cupcake right now.
Click to expand...
Click to collapse
That isn't cupcake. It is a closed source side branch from HTC.
And last I checked the merge wasn't 100% complete. Yes the started the merge and the major part is finished but small portions still need to be merged for bug fixes.

I know you guys think its old news, but i just did a repo sync and its grabbing a HUGE amount of updates/merges (i had updated yesterday so this is def new stuff). Be interesting to see if its buildable and the differences can be see.

smacknca said:
This is what I thought too, but i just did a repo sync and its grabbing a HUGE amount of updates/merges (i had updated yesterday so this is def new stuff). Be interesting to see if its buildable and the differences can be see.
Click to expand...
Click to collapse
Let us know... Don't care to start VMware up right now as I am about to leave.
BTW anyone seen this http://www.htc.com/www/support/android/adp.html

There was a recent merge but I think your changelog lists the old changes, not the new ones. FYI using master is probably not a good idea -- if you want to put stuff on devices, you should stick to cupcake, not master.
See: http://groups.google.com/group/android-platform/msg/0eeae1b3113b8f43

I can't wait till these updates are rolled to us consumers.

this is not pointed at the OP, but more the Android, Goog & the T-Mob Powers that be.
el_rhma said:
o Tactile feedback to the LockPatternView. Tactile feedback can be enabled/disabled by going to Settings > Security & location and then checking/unchecking "Use tactile feedback". Note that this can be used independently of the visual feedback of the lines ("Use visible pattern"). Thus it gives users a middle ground between showing the lines on the screen and having no feedback at all.
Click to expand...
Click to collapse
why can we have tactile feedback globally?!?
el_rhma said:
* New features
o SIM Application Toolkit 1.0.
Click to expand...
Click to collapse
Its about time this was to be added in RC33, this is required by some EURO carriers, from what Ive read.
el_rhma said:
o Don't allow a single tap to open the in-call dialpad. It is now required to touch and drag it. This makes it much harder to accidentally open the dialpad by touching the screen with your face.
Click to expand...
Click to collapse
THANK GOD, everybody who calls me will thank you...
Id also like to see 1 click of the red button "while in-call" would put the screen to sleep and a "double tap" hangs up.
I can't count how many times I tried to get around the face problem by turning the screen off while "in CALL" by pushing the red button and hanging up on my caller, my suggestion is just one of many that could fix the problem.
the updates should come out faster rather than waiting on these mega jumps in the codebase, why not update less stuff more frequently, put out whats ready when 3 or 10 fixes and/or added features are ready to go, not wait months to get a huge laundry list.
I also hope the hard work from here, is getting into the RCs and credited, xda has done more for my G1 at this point than "the trifecta" aka ANDROGooGMobile, I say send tmobile and their toys, home, they are messing up the whole party...
just a rant, sorry if I offended anybody,
Bhang

neoobs said:
Let us know... Don't care to start VMware up right now as I am about to leave.
BTW anyone seen this http://www.htc.com/www/support/android/adp.html
Click to expand...
Click to collapse
Have you tried any of those?

What is with PDF und Office Support ?????

[CUSTOM FIRMWARE] TheXSample-SXELROM v2.0 for JXDS7300B

TheXSample - SXELROM v2.0 for JXD S7300B
​
This is a summary of the original article (in Spanish) is in my blog .
For updates on this article, I suggest visiting one of the links above.
_____________________________________________________________________
UPDATES
04/02/2013: Patch_Xsample_2.1.rar
Mirror Mega
Change log:
Tincore KeyMapper
AutoProfiles. By enabling this option, the KeyMapper automatically load profiles, depending on the application that is running in the foreground.
AXIS Investment Selection
Dialogos selection list of options
Elimination of unnecessary controls
UI Enhancements (simpler interface)
Better integration Holo
Scalable Icons
Component Selection pressing physical controls
Renaming profiles
Exporting profiles *
Importing profiles *
* With these options opens the possibility to share applications among users profiles.
Driver Tincore
Acceleration of the driver
Investment AXES
Accelerometer support *
Fixed some bugs
Support for specific calibration D-PAD **
Added hot-key [VOL-] & [L2] to reset current profile ***
* Now you can assign horizontal or vertical tilt to one of the axes of the sticks. With this option, you can play many N64 or PSX titles (preferably on emulators that support analog), and the inclination to use the console to control the action in games. Example: Mario Kart 64 may play a "Wiimote Style" or Forsaken, can be controlled by tilting the tablet.
The D-PAD ** console, as already explained is analog, but which behaves as digital.
There is a problem with the D-PAD and their center (neutral position) is shifted to the right, so the analog calibration can influence the response of the D-PAD, for example, that in some games and emulators respond correctly to one side, usually to the left.
To avoid this, in games / emulators that specifically use a d-pad instead of analog, recalibrate the driver is suggested to use the D-pad as the main entrance. To do this, simply open the tool and select "Calibrate" in the Stick 0, and use the D-PAD to calibrate the device.
Note: The calibration is stored in the profile of the game, so it will not affect other profiles created with KeyMapper.
*** This combo is useful if you experiment problems or get stucked with your current keymapper layout. You can use in any time to reset profile to <RESET TO DEFAULT> values.
Requirements
Having installed the rom-SXELROM TheXSample v2.0 before installing this patch.
Instructions
Unzip the zip in the root of the microSD
Start the console with [Vol +] and [POWER] and select "Apply upadte from EXT".
Select the patch you want to apply:
- Patch1200
- Patch1320
- Patch1500
App is installed in the data, that is, as user application, and eliminates the above.
_____________________________________________________________________
List of changes
Here is a short list of changes included in this version of firmware.
Later in this article, there is a section with extended information about these changes.
Firmware
New kernel changes allowing more CPU settings and more conservative values ??(donation version includes SetCPU)
This includes new governors set for the console hardware
Minor changes in memory management.
NTFS writing enabled.
Speed ??1.2GHz default rom
All changes to the stock rom v1.7, as the inclusion of the new Full Screen option
Tincore Driver
Support for multi-directional swipes.
All controls can be swipe-type (Support up to 20 swipes configured simultaneously)
Establishment of standard joystick driver for the device. It works and is recognized by the system as analog joystick 4 axes and 16 buttons
Improvements and optimizations in the driver code, to get even less lag.
New algorithm for pointer modes sensitivities
Support for remapping keys
http://www.youtube.com/watch?v=MlJxrGBvews
(Dead Trigger mode driver with Joystick)
http://www.youtube.com/watch?v=xRRowLsgyGw
(Temple Run using the full interface with console controls)
Tincore KeyMapper
Changes and improvements in the user interface of the tool
Improved display rotation tool wing pair.
Self adjusting menus always leave visible objects / widgets on screen
Defining swipes using drag & drop, to start and end points
Simplification in the definition of areas for pointer modes
Highlighting groups of objects / widgets
Calibration Sticks in two modes: Auto and Manual
Basic implementation for remapping controls for mode "Key"
http://www.youtube.com/watch?v=hj-ZNQWQoQw
(Modern Combat 4 Touch mode, with Swipes activated to switch weapons)
http://www.youtube.com/watch?v=uvM8mgOl0aU
(Nova 3 Touch mode, with Swipes activated to switch weapons. You can see that there are no breaks in the 360 ??º turns, and changing weapon swipe too fast)
Download Links
TheXSample - SXELROM v2.0
Rom - Google Docs Mirror (GDrive)
Patch speeds and Swap
Patch - Mega Mirror
Patch - Mediafire Mirror
Thanks
Many people involved directly and indirectly in the development of this Rom: Christian Troy, fun_, Lomax, fuser-invent, Tincore, Namco69, Yoshi41, Skelton, Deen0X and who stay to name.
Special mention of Durruti, inspiration especially for TheXSample and Tincore
I hope this rom will please and utility of those who wish to try.
=============================== Older Versions ===============================
TheXSample - SXELROM v1.0 para JXD S7300B
​
Usage of this article
Usage of this article is alowed by copy or link reference to anyone with the only condition of keeping original author and a reference to the original source of this review. The mentioned reference is the following:
Source and Updates of the info from this article.
Original (in Spanish) is in my blog.
For updates I suggest to visit any of the mentioned links.
About this article
This article is a summarized version and only contains the most relevant features..
To read the full article check the previous link
Features
http://www.youtube.com/watch?v=Zz_YYYRiCz4
(SXELROM beta, showing some features)
Only features present
at the time of the writing of this review are listed.
​
(Separate external and internal mount points)
Based on Skelrom v1.0 for JXDS7300B, private 1.4stock firmware sources and JXD 1.5. Includes all Skelrom and last official firmware fixes.
Clean code. Official sources only. No alien code.
New mount points. Now internal and external mount points are at the same level in the filesystem and not one inside the other. Swap is easier.
Deep sleep improvements. WiFi disable when sleep saves a lot of battery.
New Kernel features by Skelton andTincore (check Kernel chapter)
New specific governors tailored to device hardware. Specially new "ondemand" scores more than 10000 Antutu points with console processor running at 1.3GHz (No cpu stress needed)
New "ondemand" governor allows cooler execution.
50Hz to 60Hz screen fix, The same that we suggested JXD to incorporate in his 1.5 firmware (Check screen refresh note)
New Tincore input kernel driver. It provides lower input lag and lots of extra configuration options to support new sticks and buttons operation modes.
"Tincore Keymapper", UI Mapping tool to configure specific input kernel driver options (check Tincore Keymapper chapter)
About new Kernel
​
This firmware's kernel has been created using JXD 1.4 sources. Those sources, whith some small chanes, have been released as JXD 1.5 firmware.
​
(new governors added)
More important kernel feautres:
Chanes in CPU and voltage to improve temperature and stability.
Support CIFS/NFS for seamless net shares filesystem mount.
I/O schedulers and NAND optimizations. Improve read/write operations and memory access.
Mali driver optimizations to speed up 2D and increase graphical memory cache buffer.
​
(Antutu Benchmark result with new firmware improvements, governor “ondemand” and 1.32GHz. Reaching 10000 points which is a bit better than 1.5GHz with performance governor)
About new input kernel driver: Tincore Driver
Tincore provided a new kernel driver to improve latency and support many missing features in original drivers.
​
(Keymapper, with new features like pointer mode)
Driver improves response times because it is more optimal and faster than the original. This reduces input lag
New driver enables key events for all sticks when mapping tool is disabled, This allows to use right stick as a key pressing digital stick. Because of this it can be used by emulators and games that can be controlled with keyboard.
http://www.youtube.com/watch?v=BPntj4ojtq4
(Showing some of the new features of the Tincore's Driver)
Keymapper tool features
​
(Keymapper using original JXD driver)
The new mapping tool supports both JXD driver and, naturally, the new Tincore driver.
The tool supports multiple stick modes (split/combined/pointer...) and allows to define where is the screen pressed when a button or stick is operated.
The tool supports profile save and restore and portrait mode.
Because of its backwards compatibility the tool by itself is a good replacement for the JXD mapping tool. Ley profile support is already a great addition.
Download links
TheXSample - SXELROM v1.0
Rom - Mirror Mega
Patches
The patch includes a file folder with different kernels at different speeds (1200, 1320 or 1500 MHz) as well as the possibility of exchanging the SWAP and the external memory and return to conventional partition system JXD. Within each folder is how to install and that is what.
Patch - Mirror Mega
For more updates check original article.
How to install:
​
Download the file and extract the contents of "TheXSample-SXelrom v1.0 for JXD s7300B.rar" to your sdcard root
With the deviced tunerd off, insert the microsd with the files, press and keep pressed the button [VOL+] and, without releasing, turn on your device with [POWER] button
Keep [VOL+] pressed until you see an android image with a progress bar. The firmware will be installed automatically and at the end of the process the device will reboot.
Your device is updated!
Thanks to:
This firmware has been possible thanks to the work of several persons. All valuable contributions have been in the form of coding, suggestions, testing...
Thanks go to Tincore, Skelton, Christian Troy, fun_, fuser-invent, LomaX, Namco69, Yoshi41, Deen0X and more.
Also thanks to web shops Willgoo y Zococity that provided testing devices that allowed tetst and feedback for the team.
(Because I have more than one console, I was able to perform a series of tests in parallel to obtain useful information that was used in the development of some of the features of the firmware)
I also want to give special thanks to the couples (wives, etc) several of whom have been working on this project, that it takes patience and an understanding that we do this because we love, and we want to share it with more people.
I hope this project is the starting point for more projects of the same type, which are extremely rich in both technical knowledge in general, but especially on a personal level, because in my case I meet interesting people, who always is rewarding and I hope to keep in touch. ^_^
Zalu2!
Deen0X / TheXSample

Update, check the first post...

Update, check the first post...

[APP][4.0.3+]Device Info HW

Device Info HW
version: 5.8.3
Device Info HW is a hardware and software information app for Android devices.
App trying detect components of your smartphone to provide complete information about device's hardware.
Now detection is supported for lcd, touchscreen, cameras, sensors, memory, flash, audio, nfc, charger, wi-fi and battery; if that possible for your device.
I think app is interesting and useful for users and developers who build kernels or android.
App has a quick navigation, fresh design. Also supports dark, black theme (in PRO version or 2 week in free)
You can switch by tab or use navigation panel. Many items are clickable and you can go to another tab or menu.
On recent devices reading some information is blocked.
App trying provide maximum information as possible. If you have root, app can read more (switch in settings)
Components
LCD - model. For recent android detection require root.
Also you can check the colors in lcd test.
Touchscreen - show model, also you can check how much fingers are supported in multi-touch test.
Camera - hardware info (model, vendor, resolution) and software info by API.
If can't detect camera model, sometimes available a list of supported cameras.
Detailed info about SoC in you device
CPU : model, cores, clusters, family, abi, governor, frequency
GPU : model, vendor, opengl, frequency, list of extensions
Click on the clock speed to open CPU monitor
System: complete info about your firmware build.
Memory: type lpddr and for some devices operating frequency.
Flash: chip and vendor emmc or ufs (scsi).
You can go to the memory tab and see usage of memory and storage.
Battery: base info and for some devices available extra info:
- Discharging speed is current consumption
- Charging speed is charge current minus current consumption
- Power profile - encoded by manufacturer for calculate consumption
* Kernel profile
* Model
Thermal: temperatures by thermal sensors
Sensors: availability of basic sensors and tests for them
Applications: you can quickly find apps and see info about it, also provided system apps
Drivers: you can find other chips used in your device.
Partitions: list of partition and their sizes.
PMIC: list of power regulator voltages which applied to the components.
Wi-Fi: info about connection
Bluetooth: supported features
Input devices: list of input devices.
Codecs: decoders and encoders, drm info
USB: connected devices by otg
Extra options:
- Show i2c address of the chip
- Open engineering menu for mtk and xiaomi
- List of CPU codenames for Qualcomm, mtk, HiSilicon
Devices database
You can find info for other devices, compare and check similar drivers. It available on web page: deviceinfohw.ru
Also you can upload your device info. See to the Info Center.
PRO VERSION
• Theme
Supports all a light, dark and black theme, choose what you like.
In the free version, black available 2 weeks for the test.
• Report
You can create a report with information about the device.
It will be saved in file HTML or PDF format.
You can open it or send to email by share button.
See example:
deviceinfohw.ru/data/report_example.html
• Copy text
Copy text by long press in info lists.
• New design of battery tab with charge / discharge chart
• Device list
List of i2c, spi devices.
It's useful when available many chips or they uncategorized.
Also this supports development to improve app.
Note:
Not for all devices can read drivers info, it's depend on soc, vendor. If you want help, then upload your device info.
If you want translate app for your language or have interesting ideas or found bugs, write me to email or forum.
Requirements :
- Android 4.0.3 and above
Permissions :
- INTERNET is required for upload device info. It's use only for manual upload.
- CAMERA is required for getting camera software characteristics for old camera api.
- ACCESS_WIFI_STATE is required for info about wi-fi connection.
Google Play:
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
{
"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"
}

Awesome App. Well Done!
Tested on more than 10 Mediatek Devices, no issues found. I'll start to upload all my device's hardware info to your database as soon as possible.

Nice App Sir Keep Up The Good Work! :highfive:

Hey OP! Thank you very much for this app :good:
Version 3.0.5. Now we see in the Camera tab
I would like to that looked so
Please, if possible....

Good work bro

New version 3.3.1 released.
- Support samsung exynos platform: detect cameras, wi-fi (tested on galaxy s7)
- Improved cluster detection.
- Added audio chips and nfc detection.
- Improved components detection.
- Added Net tab with wi-fi info.
- Fixed crash on some 7.0 devices.
- Bugs fixes.

good app

New version 3.5.0 released.
- Begin support Huawei HiSilicon platfrom. Display detection (need root).
On some devices available all supported cameras.
- Improved components detection.
Fixed display detection on some devices samsung, htc (qcom).
Improved sensor detection for 2 in 1 chips (acc + gyro) .
Improved components detection for samsung devices.
- Added new tab Input devices
On mtk available touchscreen model and fw version (tested on goodix).
- New app icon.
* Who has samsung with 4.2.2 with crash or bug write to me for test. (Navigation View class not found on this devices)

New version 4.0.0 released.
1) Added battery charge / discharge speed.
a) For 5.0+ via Android API
b) For mtk special variant. Tested on mt6752, mt6589.
Discharging speed is current consumption. Ids = Ic
Charging speed is charge current - current consumption. Ics = Icc - Ic
2) New navigation panel.
3) Battery experimental.
mtk
Added battery profile from kernel. According to my data, in most cases it differs on +-5% from real capacity of the factory battery.
qcom
Added battery profile from kernel and battery model. Tested on msm8992.
4) Improved components detection.
5) Spreadtrum
Added detecting lcd id (need enable root in settings)
Exmple: ID066108 it means id 0x066108, found name is s6d77a1a01.
In camera tab added list of supported camera models.
6) Samsung
Exynos
Added detecting lcd id (need enable root in settings)
Exmple: ID_0x404024 it means id 0x066108, found name is S6E3FA0.
Detect camera models for spreadtrum, qcom, marvell pxa, broadcom. (need test)
7) Qualcomm
Added list of supported camera models.
8) List of system apps. Open from apps tab from last item.
List of OpenGL ES extensions.
9) Fix codepages in some lang.
10) Fix bugs and crash on some devices.
11) Device Info HW+ (PRO)
You can create a report with device information.
Saving in html file format. See example:
http://www.deviceinfohw.ru/data/report_example.html

4.2.1
- Huawei on qcom: improved support.
- List of supported cameras with vendor and resolution.
- Samsung on exynos: added gpu freq.
- Qualcomm: added lcd panel without root from sysfs.
- Engineering menu moved to navigation panel + miui cit.
- Updated components detection and fixed errors.
- Updated sensors tab (using Sensor Test 1.4+).
- Build with new sdk.
- Begin spanish and polish localization by Radek Strycharz.
- i2c device list groupped by bus [PRO]

ANDR7E said:
4.2.1
:
:
Click to expand...
Click to collapse
Awesome...
Can you add switch to show free RAM from /proc/meminfo?

hyperion70 said:
Awesome...
Can you add switch to show free RAM from /proc/meminfo?
Click to expand...
Click to collapse
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.

ANDR7E said:
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.
Click to expand...
Click to collapse
OP, thank you very much for the update 4.5.0.

New version 4.6.3
Version 4.5.0
- New material tab bar.
- Screen Test (lcd color, multi-touch, touch drawing)
- Cpu Monitor (press on clock speed)
- Dark theme support (2 week or PRO)
- Updated components detection.
- Optimizations.
- RAM from kernel (meminfo) + swap
- Some fixes for HiSilicon cpu detection.
Version 4.6.3
- Added partition info for some platforms.
- Added new lcd color tests.
- Added tab with USB devices
- Updated components detection.
- Asus qcom: try detect cameras.
- HiSilicon: added gpu freq.
- HiSilicon: try detect cameras (with root).
- CPU operating time (click to core count item)
- System: device features: list of the features enabled in firmware.
- System: extra sys info (click to system build fingerprint item)
(modem mtk, vm mem size, some vendor info)
- Try fix opengl bug for some devices.
- Try deep detect mt6757 P20 series => P20 / P20 series / P25 / P25 series
P.S.
Who want help translate app to own language, I provide strings resources https://github.com/andr7e/DeviceInfoHW_translations/

Partitions + Project (Nvidia Tegra 4)
ANDR7E said:
New version 4.6.3
Version 4.6.3
- Added partition info for some platforms.
Click to expand...
Click to collapse
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
The information below will help you doing that. There is a link to two partition screenshots of this tablet in our XDA thread.
[Q] How Root Toshiba Excite Pro AT10LE-A-108
https://forum.xda-developers.com/showpost.php?p=74227484&postcount=39
So, here is partitions info of this tablet (attached file in black)
And their names (attached file in black)
According to Nexus 7 development thread, these are common names on Tegra tablets:
APP -> system
CAC -> cache
LNX -> boot
MDA -> encrypted userdata
MSC -> misc
PER -> per device calibration
SOS -> recovery
UDA -> userdata
USP -> bootloader
We are trying to unlock the bootloader of Toshiba Excite Pro AT10LE-A (Nvidia Tegra 4 device). There is a protection by the sealime.ko security module blocking some partitions. To defeat sealime.ko we need all the information available on partitions.
Another request is the Project information that is missing on Nvidia Tegra 4 devices. It has valuable information on LCM, modem, etc. Can you include it, please?
Thanks and best regards!

YuriRM said:
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
Click to expand...
Click to collapse
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c

great.
add a option to show some sensor info on notification/notification icon may be useful

Tegra 4 Technical Reference Manual
ANDR7E said:
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c
Click to expand...
Click to collapse
I hope this helps!
Regards
Tegra 4 Technical Reference Manual
https://developer.nvidia.com/embedded/tegra-4-reference
The Tegra 4 Technical Reference Manual ("TRM") is a technical document of over 2,600 pages targeted at those working on open source or other low level software projects that use or target the Tegra 4 processor. The TRM focuses on the logical organization and control of Tegra 4 Series devices. It provides information for those modules that interface to external devices, or those that control fundamental chip operations. The modules detailed in this document provide an overview, any necessary programming guidelines, and a register listing for that module. Internal functional units such as video and graphics hardware acceleration are controlled by NVIDIA provided software and not documented.
NVIDIA provides access to the Tegra 4 Technical Reference Manual to registered developers only. To become a registered developer, please sign up for our Embedded Registered Developer Program.
If you are already a Registered Developer, you can download the TRM from our Download Center.
Table of Contents
Introduction
Address and Interrupt Map
Interrupt Controller
Arbitration Semaphores
Atomics
Clock and Reset Controller
CL-DVFS
Timers
Multi-Purpose I/O Pins and Pin Multiplexing (Pinmuxing)
Power Management Controller
Real-Time Clock
Boot Process
Host Subsystem
GR2D
GR3D
Encoder Pre-Processor (EPP)
Keyboard Controller
CPU
Flow Controller
Memory Controller
AHB
APB
USB Complex
Audio Hub (AHUB)
Display Controller
MIPI-DSI (Display Serial Interface)
Serial Transport Stream DTV Controller
High-Definition Multimedia Interface HDMI CEC MIPI-CSI (Camera Serial Interface) MIPI D-PHY Calibration for CSI and DSI Video Input (VI) SD/MMC Controller MIPI-HSI (High Speed Synchronous Serial Interface) I2C Controller UART and VFIR Controller Serial Peripheral Interface (SPI) Controller
One Wire Battery Controller
PWM Controller
Thermal Sensor and Thermal Throttling Controller

ANDR7E said:
tegra4 didn't find.
Click to expand...
Click to collapse
Tegra 4 device - Tegra Note 7
https://github.com/Shaky156/Tegra-Note-7/blob/master/arch/arm/mach-tegra/board-aruba-panel.c
https://github.com/Tegra4
Tegra 4 Device tree, kernel and vendor binaries for Gigaset QV1030 aka. Quanta FG6Q
https://fg6q-dev.github.io/
https://www.notebookcheck.net/Gigaset-QV1030.114384.0.html
https://www.notebookcheck.net/NVIDIA-Tegra-4-SoC.87052.0.html
Sent from my takee 1 using XDA Labs

YuriRM said:
Tegra 4
Click to expand...
Click to collapse
I wrote about your toshiba device, tegra 4 source is available. LCD model name is not set, only lcd params.

[APP][6.0+][UPDATED] FrontFlash Notification v2.5 (20190424)

{
"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"
}
What is this?
Basically by installing this application, as soon as you receive a notification there is a flash as your phone starts blinking for the LED notification.
It can be useful to anyone that has a device without the LED notification, but instead have a flash next to the selfie camera.
It also extends the concept of notification to the unread badges received from the applications (ex. the "Facebook like"). So, when an unread badge pops up, in the same way as a "normal" notification the flash starts blinking and you will be notified of what's going on.
Various settings are also available to better configure the application to suit your needs.
It works on all devices equipped with a front flash, regardless of whether or not they have the hardware LED notification. (read also the Hardware limitations section for more details)​
Main features
customizable activation based on the current display status and audio mode
pocket mode and recovery options
Samsung AOD support
single or double blink
optional custom delay for the first blink
use also the rear flash when the device is upside down
additional flashing loop with customizable frequency
three different gestures to dismiss the flashing loop
customizable exclusions for the incoming call, the missing call and the text messages
customizable exclusions for all the installed user applications
flash notifications for the unread badges received from compatible applications and customizable by app exclusions (only on Samsung devices with TouchWiz based ROM)
suspend on low battery
suspend during a customizable time slot
integration with the Android "Do not disturb" settings
custom quick setting tile in the quick settings panel to easily turn on/off the service (only on Android 7.x+ devices)
custom shortcut pressing the application icon to easily turn on/off the service (only on supported launchers and on Android 7.1.1+ devices)
built-in black list to avoid the flash for useless, fake or annoying notifications from some applications
optimized for memory usage
battery-friendly (usually takes up 2% in each 24 hour period)
dark theme
RTL support for Arabic languages
no ADS
no ROOT ACCESS needed to work
and more...
Languages
English
Italian
Arabic (Egyptian) @yshalsager
Arabic (Syrian) @mozzafar alali
Croatian @dugi9991
Czech @novas78
French @Primokorn
German @supergrobi94 / @Oswald Boelcke
Greek kynigosg
Polish @emcom
Portuguese (Brazilian) @Taivotat2 / @justjr
Russian @gaich
Simplified Chinese @ContactFront
Slovak @kubalav
Spanish @JHAM2005
Turkish @Fatih Fırıncı
Ukrainian @Alexiy_ua
Vietnamese @tphg
Privacy
This application is not ad-supported and can not collect and transmit any sort of privacy sensitive information.
This application can not collect, store or publish any user information.
This application can not use any data connection, detect your location or access your contacts. It also can not read any sensitive information stored on your device. This guarantees maximum security for your data and your privacy.​
Permissions
This application does not need any special permissions except for the one to bind the Android notification listener service. [android.permission.BIND_NOTIFICATION_LISTENER_SERVICE]
This is the only authorization required to properly interact with your incoming notifications (you will be asked about it explicitly when it is run for the first time).
Devices with Camera Hardware level: LIMITED (partial Camera2 API support)
On some devices the manufacturer implemented only partially the Android Camera2 API; this means limited hardware access to the camera for the developers. In this case the only way to let this application properly take control of the front flash is to use the old Android API and that's why you may also have to authorize the application to use the hardware camera. [android.permission.CAMERA]
With the first run and only if the application detects this limitation, as per the above case you will be asked explicitly to grant full camera access permission (even if the application should only use the front flash, the flash is strictly part of the hardware camera).
You must agree with providing access to your device camera, file system and audio recording for the application to function. This access is limited to user only. None of the data present in your device can be shared with me or any other person.
Keep in mind that if you deny any of these permissions the application will not work!
If you know how Android works and the meaning of application permissions, you can easily verify by yourself all the above statements.
So please, avoid claiming that we are a bunch of criminals here just to steal your data with this application... in doing that, you would be such an IDIOT!​
Hardware limitations
Lately several devices (mainly, but not only, running Android 8.x) are equipped with front flash with custom hardware that developers can not have access to. Furthermore, with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices.
Strangely enough, the front camera of your device may not be equipped with a "real" front flash for this application. When it "asks" through the Android API to your front camera some information about its front flash, the answer may be "no front flash available". There is no workaround this!
This is a software/hardware limitation imposed by the manufacturer (don't ask me why) and at the moment unfortunately there's nothing I can do. I understand your amazement, but if you experience this kind of issue at 99% of the time that's the reason why this application may not work and could report the non-availability of a front flash despite your eyes seeing a front flash.
Mainly only the branded (stock) camera application can handle this kind of front flash, using owned and reserved API.
Try it by yourself to install (from the app Store) an alternative camera application. Then shoot a front selfie and check if the front flash can turn on... or use any other application you expect to use the front flash (usually Instagram and Snapchat fail as well) and then let me know the results.
In addition, you can also try to install Device Info HW and then select the "Camera" tab and check all detailed information about the front camera of your device.
Finally, let me remind you that this app can't take control over the brightness, the color and the speed (On-Off phase) of a flash; unfortunately it isn't a LED... no way for the developers to handle these features.
All of them are strictly related to the hardware and its manufacturer and therefore vary from model to model.​
Main functioning
As you can imagine, this application must be able to take control of the front flash of your device to work properly. In an Android phone this can only happen in one way: through the front camera as the flash is strictly connected to it.
The developers in fact through dedicated instructions, can turn it on and off at will. But it always has a connection to the camera and not directly to the flash itself.
To handle all the incoming notifications, an Android service will run in background on your device.
These are the main functioning at the root of this application.​
Troubleshooting
If you installed any startup manager application (such as Startup Manager, Autorun Manager, AutoStart Manager, Advanced Task Manager, BootManager, etc) or any battery manager/optimizer application (such as Greenify, Doze, Brevent, Hibernator, App Freezer, etc) pay attention to avoid killing the running "Flash notification service" otherwise this application will not work!
I also want to draw your attention to the importance of the Android wakelocks in the lifecycle of this application (if you don't know what wakelocks are, disregard the sentance below).
If your device is running an application that detects and blocks wakelocks (such as Wakelock Detector, WakeBlock, No Wakelock, Wake Lock - PowerManager, etc), keep in mind that the main features of this application will not work as you expect. So add it to the white list if any, or if you are interested in using this application in any way avoid blocking the wakelocks.
In other words, because of unreasonable battery optimizations implemented by some brands but not only, you have to be careful not to put this application in hibernation without realizing it or maybe killing or blocking the background service without noticing it. These are the most common causes of the main problems you may experience!
Please verify the impact over this application by any system tools / Magisk - Xposed modules which you heavily rely on (especially if your device is ROOTED).
So, double check your system settings before reporting any issues, thanks.​
Battery consumption
It isn't strictly related to the application itself. What drains the battery is the flash not the background service in charge of managing your incoming notifications, I can't do more in terms of optimization.
Battery consumption mainly depends on how long you will let the flashing loop run before you dismiss it (the shorter it is the better for your battery) and also on how many notifications you receive a day.​
Issues & Known bugs
with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices, so this application stop working!!
System requirements
Android 6.x Marshmallow or later
a device with front camera and front flash (read also the Hardware limitations section for more details)
five minutes of your free-time and a little piece of your brain (just in case)
you do not need ROOT ACCESS for this application to work
Installation instructions
Just download the apk and open it as a normal application.​
Download
This application is available on the Google Play Store.
In order to keep in touch with the latest updates, I suggest you uninstall any previous version you downloaded here from XDA and then install the official version of the Play Store.
Get FrontFlash Notification​
Credits / Thanks to
thanks to @supergrobi94 for the graphic support
thanks to @Alexiy_ua, @ContactFront, @dugi9991, @emcom, @Fatih Fırıncı, @gaich, @JHAM2005, @justjr, @kubalav, kynigosg, @mozzafar alali, @novas78, @Oswald Boelcke, @Primokorn, @supergrobi94, @Taivotat2, @tphg, @yshalsager for the translations
Donation
Your donations are welcomed and appreciated, press the thanks button instead of saying it.
PayPal​
FrontFlash Notification
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2019-04-24
Created: 2018-01-13
Last Updated: 2019-04-24

Screenshots

Changelog
2.5 (current release)
migration to native Android Pie 9 (API 28)
updated internal black-list for the auto-excluded applications
minor bug fixes
2.4.9 (stable)
minor bug fixes
2.4.7 (stable)
under the hood fixes and optimizations
2.4.5 (stable)
minor bug fixes
2.4.2 (stable)
fixed the custom shortcut icon issue on Android 7.1.x devices
minor bug fixes
2.4.1 (stable)
migration to native Android Oreo 8.1 (API 27)
added the option to delay the first blink
added a custom shortcut pressing the application icon to easily turn on/off the service only on supported launchers and on Android 7.1.1+ devices
added the Simplified Chinese translation
added the Greek translation
added the Ukrainian translation
updated all translations
updated internal black-list for the auto-excluded applications
lots of under the hood fixes and optimizations
2.3.3 (stable)
Android 8.x users may experience general malfunctions
added the sub-option to keep screen on if the "Turn display on" option when a notification occurs is selected
added the Slovak translation
added the Turkish translation
added the Vietnamese translation
updated the Czech and Russian translations
stability improvement
minor bug fixes
2.3 (stable)
This update will reset all user preferences to default at first run!
fixed the pocket mode issue
fixed the time slot suspension issue
added a custom quick setting tile on the quick settings panel to easily turn on/off the service only on Android 7.x+ devices
major code rewrite for the graphical user interface (flash notifications settings)
updated internal black-list for the auto-excluded applications
minor bug fixes and various adjustments
2.2.7 (stable)
fixed the pocket mode issue on some devices
fixed the time slot suspension issue on Android 8.x devices
fixed the incoming call flash notification issue
fixed the consecutive notifications issue
renewed badge notification service for Samsung devices (some tests may be needed)
minor bug fixes and various adjustments
2.2.5 (stable)
fixed the issue of annoying blinks while the device is in use (user present/screen on) in some particular conditions or by specific applications
fixed the issue of the suddenly stop working blink loop
battery life improved
new max limit for the blink loop duration
new increase values for the blink loop frequency
minor bug fixes and various adjustments
2.2.1 (stable)
fixed the service force close issue on Android 6.0 devices
minor adjustments
2.2 (stable)
minor bug fixes
2.1.6 (stable)
minor bug fixes
translation update for some languages
2.1.4 (stable)
minor bug fixes
2.1 (stable)
main code reengineering
stability and compatibility improvement
removed the flashing loop duration setting, from now is always unlimited
better performance
2.0 (stable)
code optimization
stability improvement
1.9.5 (stable)
code optimization
minor bug fixes
unlimited duration for the flashing loop
1.9.4 (stable)
added the Portuguese (Brazilian) translation
added the Arabic (Egyptian) translation
added the French translation
added the Czech translation
added the Croatian translation
added the Russian translation
added the Arabic (Syrian) translation
new range values for the duration and the frequency of the flashing loop
1.9.2 (stable)
added the option to force the English language
fixed the Samsung Email application issue
stability improvement
added the light sensor management (if present) for the flash type auto-adjustment (single/double)
added the option to use the rear flash when device is turn upside down
added RTL support for Arabic languages
1.9 (stable)
fixed the service force close issue and runtime exception on some Motorola devices
minor bug fixes
added the Spanish translation
1.8.3 (stable)
official Play Store release
minor bug fixes in the notifications detection engine
added compatibility to Android 8.0 Oreo (API 26)
added the Polish translation
1.7 (stable)
extended support to both Camera and Camera2 API to properly detect and manage the front flash also on devices with limited access to the camera (e.g. new Samsung device series)
fixed the issue with Gmail notifications on Android 6.0 devices
fixed the missing installed applications issue in the excluded applications list
fixed the wrong low battery detection issue on some devices
added a "select/unselect all" toggle switch in the excluded applications list
integration with the current Android "Do not disturb" settings as an additional way to disable the service in certain situations
minor fixes and code optimizations
updated internal black list for the auto-excluded applications
some GUI improvements and adjustments
new dark theme
new application icon
some corrections to writing errors
added the German translation
1.6 (stable)
added the option to choose a custom time slot for the service suspension (tap on time slot)
minor fixes
1.5 (stable)
added Samsung AOD detection and support
added the option to choose which applications exclude from the unread badges notification (tap on See list)
added the option to choose a custom sound for the unread badges notification (tap on Set sound)
improved both memory and cpu consumption
1.4 (release)
added the accelerometer sensor management and the relative “by shake” option
fixed the issue with duplicate items between the unread badges notification and the "normal" notification from the same application
new GUI
added the Italian translation
1.3 (beta 2)
added compatibility to Android 7.1.1 Nougat (API 25)
added the option to choose which applications exclude from flash notification (black list)
added the unread badges detection and the relative flash notification for all supported applications (only on Samsung devices with TW rom)
lots of under the hood fixes and optimizations
1.2 (beta 1)
added the proximity sensor option and its management
added the notifications badge count over the application icon in the app drawer and its relative option (only on supported device: Asus, Huawei, LG, HTC, Oppo, Samsung, Sony, Xiaomi, ZTE)
fine tuning in the notifications detection engine to avoid fake flash notifications from system and user applications
performance improvements
1.1 (alpha)
added the option to enable a blinking loop for all the incoming notifications
added the low battery status detection and the relative service suspension option
added an option to suspend the service during a specific time slot
bug fixes
1.0
initial release

Support
Feedback
Please write in this thread any suggestions or bugs you come to know to help me make this application better and better.
What's coming next
none
Translations
All translations are created by community volunteers and open for contribution. If you want this application in your language and you are interested in cooperate, please send me a PM.

Hardware limitations
Lately several devices (mainly, but not only, running Android 8.x) are equipped with front flash with custom hardware that developers can not have access to. Furthermore, with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices.
Strangely enough, the front camera of your device may not be equipped with a "real" front flash for this application. When it "asks" through the Android API to your front camera some information about its front flash, the answer may be "no front flash available". There is no workaround this!
This is a software/hardware limitation imposed by the manufacturer (don't ask me why) and at the moment unfortunately there's nothing I can do. I understand your amazement, but if you experience this kind of issue at 99% of the time that's the reason why this application may not work and could report the non-availability of a front flash despite your eyes seeing a front flash.
Mainly only the branded (stock) camera application can handle this kind of front flash, using owned and reserved API.
Try it by yourself to install (from the app Store) an alternative camera application. Then shoot a front selfie and check if the front flash can turn on... or use any other application you expect to use the front flash (usually Instagram and Snapchat fail as well) and then let me know the results.
In addition, you can also try to install Device Info HW and then select the "Camera" tab and check all detailed information about the front camera of your device.
Finally, let me remind you that this app can't take control over the brightness, the color and the speed (On-Off phase) of a flash; unfortunately it isn't a LED... no way for the developers to handle these features.
All of them are strictly related to the hardware and its manufacturer and therefore vary from model to model.
Main functioning
As you can imagine, this application must be able to take control of the front flash of your device to work properly. In an Android phone this can only happen in one way: through the front camera as the flash is strictly connected to it.
The developers in fact through dedicated instructions, can turn it on and off at will. But it always has a connection to the camera and not directly to the flash itself.
To handle all the incoming notifications, an Android service will run in background on your device.
These are the main functioning at the root of this application.
Common issues & Troubleshooting
If you installed any startup manager application (such as Startup Manager, Autorun Manager, AutoStart Manager, Advanced Task Manager, BootManager, etc) or any battery manager/optimizer application (such as Greenify, Doze, Brevent, Hibernator, App Freezer, etc) pay attention to avoid killing the running "Flash notification service" otherwise this application will not work!
I also want to draw your attention to the importance of the Android wakelocks in the lifecycle of this application (if you don't know what wakelocks are, disregard the sentance below).
If your device is running an application that detects and blocks wakelocks (such as Wakelock Detector, WakeBlock, No Wakelock, Wake Lock - PowerManager, etc), keep in mind that the main features of this application will not work as you expect. So add it to the white list if any, or if you are interested in using this application in any way avoid blocking the wakelocks.
In other words, because of unreasonable battery optimizations implemented by some brands but not only, you have to be careful not to put this application in hibernation without realizing it or maybe killing or blocking the background service without noticing it. These are the most common causes of the main problems you may experience!
Please verify the impact over this application by any system tools / Magisk - Xposed modules which you heavily rely on (especially if your device is ROOTED).
So, double check your system settings before reporting any issues, thanks.
Battery consumption
It isn't strictly related to the application itself. What drains the battery is the flash not the background service in charge of managing your incoming notifications, I can't do more in terms of optimization.
Battery consumption mainly depends on how long you will let the flashing loop run before you dismiss it (the shorter it is the better for your battery) and also on how many notifications you receive a day.
Hope I have been helpful in understanding.

Thank you nice work
I will add Arabic language

Can't enable the front flash.. Its not enabling.. Greyed out.. I have j7 pro.. Ty..

The app doesn't know I have Front Flash (J7 2016)
Sent from my j7xelte using XDA Labs

ickoslash said:
Can't enable the front flash.. Its not enabling.. Greyed out.. I have j7 pro.. Ty..
Click to expand...
Click to collapse
Oh... this sounds strange! Be more specific please.
Which android version?
Which label is displayed at the left of the greyed switch?
Did the app ask for "Notification access permission" at first run?
Open Options --> Lock screen and security --> Other security settings and check manually the notification access permission (if it's disabled, activate it now) and let me know.
Thanks

Arnaud Créative Studios said:
The app doesn't know I have Front Flash (J7 2016)
Sent from my j7xelte using XDA Labs
Click to expand...
Click to collapse
You mean did you received the "Front flash not present, service disabled" message?
Thanks

spacejam said:
You mean did you received the "Front flash not present, service disabled" message?
Thanks
Click to expand...
Click to collapse
Yes
Sent from my j7xelte using XDA Labs

spacejam said:
Oh... this sounds strange! Be more specific please.
Which android version?
Which label is displayed at the left of the greyed switch?
Did the app ask for "Notification access permission" at first run?
Open Options --> Lock screen and security --> Other security settings and check manually the notification access permission (if it's disabled, activate it now) and let me know.
Thanks
Click to expand...
Click to collapse
Got error message front flash not present.. Already enabled it in notifications under lock screen and security.. My phone's j7 pro.. So technically it's nougat..

Arnaud Créative Studios said:
Yes
Click to expand...
Click to collapse
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
ickoslash said:
Got error message front flash not present...
Click to expand...
Click to collapse
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks

spacejam said:
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks
Click to expand...
Click to collapse
Yep.. Exynos chipset.. It would be awesome if you could fix it dude.. Tnx a lot for making this app.. Will wait for the update.. :fingers-crossed:

spacejam said:
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks
Click to expand...
Click to collapse
SM-J710FN,Exynos,Stock TW Nougat Rom with Stock Launcher
Sent from my j7xelte using XDA Labs

FrontFlash Notification
Issues & known bugs:
on some Exynos chipset based devices, take control over the front flash fails. Check yours by yourself and let me know. (I'm working to understand how to fix it)

Thank you for this app, I will try it.

Works great on my Moto Z2 Play. Even dual flash works too. Awesome work !

This will be very useful on my Honor 7 since the notification LED is so small it's almost invisible.
Haven't been able to get it to work yet though.
First issue I got was that the service was running but not enabled. I figured out it was due to the "suspend on low battery" setting even though my battery was at 80%.
I unticked that and now the service is running and enabled.
I'm trying to get a notification when receiving an e-mail(gmail) but nothing is happening. Gmail is not in the possible exclusion list at all, maybe that has something to do with it?
Edit: It works for other apps like the calendar app.
Thanks for the work so far.

FrontFlash Notification
Just an update for Exynos chipset based device users... the front flash detection issue is not related to the chipset.
For some strange reasons (don't ask me why), on the new devices series (Exynos of course), Samsung has implemented only partially the Camera2 API for the developers. Hardware level: LIMITED (partial Camera2 support)
This is why at the time been my app can't use the front flash on your device.
In the next few days I'm going to produce a new 1.7 version, where if Camera2 fails the app takes control over the camera and his front flash using the old Android API.
Based on the first tests, fortunatelly this seems to fix the problem.
Keep in touch