T280 - Ultra Stock [ARK3] Samsung Experiance
Based on the latest stock firmware, with limited Google and Samsung bloat. What was removed can be installed through Play Store, or Galaxy Apps Store.
Added apps and features are a compilation, that were hand picked from various OEM firmwares, both phones and tablets built between 2015 and 2016.
This is a system backup from TWRP so, please backup before restoring this copy of my backup.
WHAT'S INCLUDED
FULL FEATURED ACCESSIBILITY w/ SOUND DETECTION
FULL FEATURED SECURED LOCKSCREEN
PASSIVE KERNEL
100% OPEN GAPPS COMPATIBLE (Nano installed)
MIRRORLINK
NEARBY
SCREEN MIRRORING
MAGISK ROOT
BUSYBOX
DRIVE LINK
SIDE PANEL (Mini softkeys - portrait only)
CAR MODE
TABLET SVOICE (Customizable wake up command, Mic always on & minimized)
SPEN (Finger input)
SNOTE4
SCRAPBOOK
EHANCED VOICE RECORDER (3 Modes)
DUAL SAMSUNG VIDEO PLAYERS (STOCK TABLET & PHONE POP OUT STYLE W/ DLNA CLIENT)
INTEGRATED ENHANCED PHOTO, VIDEO & AUDIO CLIP EDITING
THEMES & FULL THEME STORE
FEATURES
MULTIWINDOW RESIZE AND POP OUT WINDOW
NATIVE HVEC DECODING (buggy... needs recompiled driver)
PIN TO SCREEN
MEMORY BUG oFIX/WORK AROUND
WRITE TO EXTERNAL MEDIA FIX
KNOX & UNUSED INTERNATIONAL INPUTS REMOVED
DISABLED SAMSUNG MEMORY MANAGEMENT
REMOVED SMART MANAGER AND ITS SYSTEM COMPONENTS
CLEANED UP NOISE & BOOSTED MIC RECORDING GAINS
UNLOCKED ACCESSIBILITY FEAUTURES & OPTIONS
INSTALL TO EXTERNAL SD CARD ENABLED w/ ALWAYS ON/OFF OPTIONS
UNLOCKED QUICK SETTING TOGGLES
J5 & TAB4 SETTINGS UI MENUS (TOGGLED REBOOT TO SWITCH)
J5 PHONE SPOOF (For more additional enhanced apps on the store)
WIFI & GOVERNOR BOOST ENABLE/DISABLE
MODDED HOST FILE w/ ON/OFF
MODDED CSC FEAUTURES
ADDED MISSING FRAMEWORKS AND PERMISSIONS
ADDED REQUIRED MISSING LIBRARYS AND ENHANCEMENTS
LOGGING IS CLEANER THAN FACTORY - (Because of framework was looking for missing components, and my minimal debloating of required system components, which most custom firmwares have hidden by turning off logging, which is a no no.)
OUTSTANDING ISSUES
NONE! Well, as far as I have seen in with my testing, smooth and stable, without any random app issues.
Well, there are known issues that dont effect function, and some of which have work arounds.
The minor issues are... with Enhanced Voice Recorder, not being able to create voice to text memo. This tablet has a different audio muxer schema than what the Enhanced Voice Recorder application expects, for voice to text function. It only effects creation of words from recorded voice. No errors, just a lack of text output.
Car Mode only has half of its functions, since the tablet is not a phone. Outside of not being able to answer calls and messages... voice commands to play music and route with maps are fully functional. Maybe there is a way to hook blue tooth phone through tablet to control messages and calls as a head unit would. Then if that is the case, the car mode function is 100% functionable.
Signature and face lock are functional, but the settings ui have different call routine than tablets frameworks. The issues also includes a few other minor areas within the settings menu, depending on which settings ui you use. So the reason to toggle between one settings ui and the other. Once you play around with each settings ui, you will find the disadvantages of the few broken settings areas cancel out, by their availability being on the other ui.
If wanting face lock, secure lock screen is a work around. It allows proper call routines to enable face unlock, location unlock, voice unlock, and the rest or googles secure lock features that samsung does nof implement on this tablet.
There are about four (2 to 3 wee issues on each of the two settings ui that are available) hardly used areas that have issues. One is motion, within motion settings, the hook is not proper for the tablet, since the ui is hooked for phone. Plus even if motion settings had a proper hook, the lack of light sensor and other required sensors would make the setting as useless as bonding or connection boost, which is within the phone settings ui. Sounds is broken in phone settings uil but is fully functional in Tab 4 ui. Most of the sounds settings can be done within the volume control, and the apps that have settings for alarms, such as calander.
The fix can be done by a dev, to compare stock settings ui and framework.apk, and the other two variants of settings ui and framework.apk from the firmwares i used.
Because the tablet framework.apk is 90% complete over a full featured phone, the last issue is video player. The res folder within the framework.apk is missing the images for media players and other things. Adding the proper res files should clear up the black boxes for missing buttons. The buttons work, just no lables or images to inform function. Anyway you will need to get familiar with the functions to enjoy the benifits of the phone video player with pop out display and.... drum roll... DLNA client.
I have a thread on what I have done to make this rom happen. For refreference and some details as to whats been done, can be read there.
https://forum.xda-developers.com/galaxy-tab-a/how-to/converting-tab-st-280-to-samsung-j500f-t3911418
DOWNLOADS
Final release... no updates will be made, so don't ask.
https://mega.nz/#!onRRxaqD!4xetR27vQhrcjGXyxoOhysyq8uU2kYGdFRJQlKCH-z0
Unzip in your twrp backup folder, and restore in twrp. Be sure to wipe caches.
Here are some screen shot images of some of what is available on this firmware.
{
"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"
}
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
A
yasars said:
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
Click to expand...
Click to collapse
Thank you for giving it a try...
This is a test build before i include all the script mods.
You will not have root or passive kernel until I finalize my build.
This test build will keep your existing kernel and root, if rooted. Just will not have super su console installed. That will need to be installed to control su, if needed. I understand magisk can control su, but never tested.
The reason i did not include the scrips in the build, is to make sure if any issues that may come about in testing are not because of kernel or scripts that i plan on including.
I am running the scripts myself without issues, unless you consider loosing about 1.5hrs of total battery run time an issue. I get around 13 hours continuous run time, and around 15 hours stock.
The benefits in keeping hicups minimal with streamed media and heavly decoded formats, outway having an extra hour or two of battery time.
Once I make the final build, it will include the scripts and latest stock kernel with magisk root and the passive kernel with magisk root, as an addon option.
The scripts will be within the system with the user to setup as they need them with the given utilities in the rom, or with tasker if one should choose.
There will be a tutorial on each script and how to use the tools to enable or disable them.
The only mods included in the test build are, build.prop, install to external, modded hosts file, modded csc features file, and its utility to edit along with a few other non stock utilities.
You can manually remove utilities not needed, and replace with what ever to suit your needs within the system. Just make sure you do not consume the system partions free space. I find between 200mb to 120mb free space as a minimum, any smaller could raise issues.
Also i forgot to add not fota or security updates...they have been disabled or removed, not completely just inactive. I doubt samsung will provide anything further with this tablet. As i never saw much for Note 8.0, which is a better and more top of the line tablet for its day. Its up to modders to push getting a kernel built for newer custom builds, in which one can move on to when the opertunity comes.
I admit the mods are not a requirement, but do come in handy at times, escpecially once you get to play with them.
thank you man !!! really nice job !!
Thank you for this, working really well and makes the tab much more useful with the version of android we are stuck with
yasars said:
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
Click to expand...
Click to collapse
mr_ppp said:
Thank you for this, working really well and makes the tab much more useful with the version of android we are stuck with
Click to expand...
Click to collapse
Thank you! Your the first that has responded back on trying my testing version. I will post a final next week some time. There has been a bit of clean up that did not transfer to the testing firmware. Some of which will require a one time run of a script to add a few files into data. They will allow mic calibration and some modules to load without logcat errors.
The main parts of the added functions are basic, but will make the basic functions more full featured like the bigger tablets. I am really liking the built in editing and finger stylus in most apps, and keyboard writing pad. Plus the voice recorder works very well, minus the lack of text conversion from spoken words.
Once the mic calibrates, you can easily record soft sounds without much hiss or digital noise. Though Svoice does mess with the internal mic settings, so as a simple fix to resolve mic gain issues, i recommend putting the tablet to sleep by pressing the power key, and wait 5 to 10 seconds and wake.
A hidden feature is backdrop screen saver. Its included in android tv, but will run fine on any device. It allows screen off when charging and sleeping. Once the tablet is fully charged it goes into dim backdrop images display. You dont need to touch the tablet to know its fully charged. If you dont want the backdrop to stay on, just press the power button once and the display will stay off.
It looks like nobody else has any comments, let alone any requests... not that I can do anything more.
It just would be nice to see a dev step in an consolidate the two settings ui apks into one and clean out the unused settings sections and correct the bad sections, which are small yet would make this a near perfect update for our tablets.
Have tested a functional smart face unlock, using secure lock screen. It is a work around for the broken settings section for face detection. Settings will not save after creating the face, and FC. Using secure lock screen will enable secure face.
Also this new firmware disables unsecure lockscreen options, which some may miss.
If using smart face for the first time, it may be a bit cumbersom, but it seems to work fairly well, once you get use to being detected.
After rebooting, face detect will not function for security. After unlocking, face detect will enable swipe once your face is detected. If not, it will stay in the unlock mode you set, until unlocked.
Blue tooth, location, and movement unlock will function similarly.
Signature lock is broken by the settings ui build being used by the system.
Voice note to txt is broken by the systems mixer and PCM mappings
I do not recommend using the voice to text function in voice recorder, mostly because it amplifies background noise and sets each word spoken as isolated audio, which may work with other voice audio to txt applications.
As a quick update... found the issues with voice recorder, and resolved it to be 98% reliable on the first try after reboot. Usually one would need to put the tablet to sleep and wait a few seconds to reset mic gain.
Found mic gain file missing along with other files that are not part of the latest build.
Will correct with a one time usage script to repopulate the missing files, which are not part of the existing system, into data
The mic gain will automatically adjust every reboot, if needed, and when voice recorder is used as well. It may take a few reboots or voice recorder uses to properly adjust once this firmware update is applied on a dirty flash.
No, i did not resolve voice to txt feature though voice recorder. But the memo feature does work just as clean as all the other recording options. Just with a 5 minute timer.
I also tested changing the wake up command to Svoice. You can reset the command, if you go into apps manager and clear out data for voice recorder and voice command. Svoice has a reset for itself in its settings.
Still messing around before finalizing and releasing my modded firmware.
I have noticed improvements overall, just looking deeper into obtaining more features if possible, like private mode and quick connect. As i touched upon them, but assumed limitations from framework and system ui.
Who knows, it may be some over looked files and such.
glad to see you are working in the t280. I still use this tablet for daily use but the stock rom it's not what I need.
I hope you release the rom very soon! Thanks!!! keep Going!
Lichsv said:
glad to see you are working in the t280. I still use this tablet for daily use but the stock rom it's not what I need.
I hope you release the rom very soon! Thanks!!! keep Going!
Click to expand...
Click to collapse
I am planning on releasing it soon... been testing a bit as i go. Mostly figuring out simplest way to have manual control over enhancements, while having some automation in the process. If i make it simple for me and leave out the abiltiy to revert back an option, many may find some issues that plague them.
Example, not all apps like being forced or moved to external sd card. Already found a few, and started toggling the option when needed. I will update my info to reflect that for reference for this fimware.
Also my hosts file is pretty intensive. It blocks some ads that other blockers dont block, but google has been working diligently in building its ad marketing scheme deeply into apk function. So some streaming apps may function slower than others when updating programmes. Play back may be effected by a delay while ads are not allowed to play, or not start at all unless backed out and restarted again. Old BBC America was that way. Depending of app, slider bar for skipping may not be shown, as all ad breaks are removed. Some show slider bar without ad breaks, and some have ad breaks but may limit half of the ads randomly depending on the server its connected to for ads. All in all, if you find an issue with internet connection or streaming playback, disable the hosts file and try again.
Hosts file and install to external SD, can be toggled on or off on the fly. The only reboot required option is to change settings ui. As each settings ui has a set of options that broaden the tablets abiltities, making it like two devices in one. Some settings carry over from being set by a different ui. So toggling may not be required as much until the tablet is fully setup. Though for my needs, i cant fully stay on one ui over the other, as the options are too varied without any other means to control or use without the ui.
Since nobody has mentioned any Samsung functions or unique apps missing or required... i limited my testing to wee bugs that may pop up on dirty flashes. Yes i have been dirty flashing over and over with different and updated system backups, to find the best or cleanest way to have an issue free update without creating issues if one should need to revert back to stock.
Once i have time i will lay out more updated information about features and included apps.
Okay, here is a snapshot of smanager once you restore my ti backup of the customized settings.
You will need to restore this file in ti backup... https://mega.nz/#!UjJzEa6b!Tl4osQhOUfrNy9i4ntFAvbitbAIKdTl7z787ujG94M4
To restore, just use menu and select import and point to the location of the downloaded backup file. Once restored, smanager will be setup properly for running scripts.
Notice the items in red... they are enabled and will only error when re-launched. All the other non red items are active for launching. Once launched the item will turn red, thus allowing you to quickly deturmine what has been enabled or disabled. They will stay as they are even after reboot.
I set up the defaults this way so there wont be any issues if one is to do a factory reset for a clean install of this firmware.
Notice the last item named run once... it fixes wee issues that the framework cannot install to data. They are small empty files, required for some features to function properly. Also there is a set of settings db files that will update toggles and enable universal functions that may not be seen without need of booting with a different settings ui.
The gear icon next to an item means it will run at boot up, on an internal delay by smanager.
The skull and cross-bones means su enabled. None of the scripts have su commands for safety.
The star means favorite, so like named items can be separated by enabling favorite to keep on top of non favorites.
Done! Updated original page and added a final version firmware for downloading. The previous reply is for final setup to enable features and mods.
gps not working?
juanysara said:
gps not working?
Click to expand...
Click to collapse
Your the first to have any issues, out of the many who downloaded and tried my system backup. Unfortunatly, I deleted by work files from many different factory firmwares, assuming everything was cool, since had very little feedback. I guess I could make another system backup, from my working tablet mods, to replace the one I uploaded on Mega, if others find any more issues.
If you have issues, revert back to your twrp system backup. I assume your model is not the same as mine. The system backup is for the 7.0 wifi only Tab A6.
Im continuously getting an error when i try to restore. extracttarfork() process ended with error=255
juanysara said:
gps not working?
Click to expand...
Click to collapse
emottau said:
Im continuously getting an error when i try to restore. extracttarfork() process ended with error=255
Click to expand...
Click to collapse
Try downloading again from mega, and try again. Else revert back to your system twrp backup.
Hello
I had to go back to the stock ROM and has already returned to work the GPS
It was the only way to make it work properly, I don't know if it's my device failure.
Too bad I can't use this ROM I've lost Snote, very useful to me is there any way I can use it in ROM stock PHE?
Thank you, for your time and your work and sorry for my bad English.
Edit: Sorry if you bother asking, but I'm trying to learn a little bit about android, I created a zip to install Snote, I got it to work but when I give it to create a da FC note Can you tell me it's wrong? thank
https://mega.nz/#!Vw5SEAxD!JAdpdtUQWpEWBQZa6AWdHd-UJDE280fnRwtXNCk02jw
Really tried it hard
Unfortunately GPS is killed and some UI issues in settings .... :crying:
I would really like to see a ROM with SD card integration (Android 6?) because this tab is so kewl.
Would you try to fix this ROM so we could give it a try? :angel:
Boot loop after restore
Tried this but just get a boot loop!
Same here boot looping
Related
Phab7 is an on-the-fly UI switcher: select Phone, Phablet, or Tablet, then tap the Change button. The switch happens immediately - no reboot needed. A separate option lets you switch settings screen layouts (e.g. the Settings app) between Phone-style (separate screens for categories and details), and Tablet-style (categories and details, side-by-side).
Unlike other solutions, Phab7 has no effect on your apps beyond for their Settings screens. In particular, it will not alter the size or layout of your launcher's icons or dock (nor will it cause the tablet-style app-drawer icon to appear).
Note: Google removed Tablet mode from KitKat, so it is not available if you're running Android 4.4.x.
Installation
Important: if you have a beta version of Phab7 (v0.9x) currently installed, you must uninstall it before installing v1.0. Android will refuse to install it if one of the betas is present.
if you don't already have XposedInstaller on your system, see this thread
install Phab7.apk the same way you'd install any other sideloaded app
enable Phab7 by reopening the XposedInstaller app and selecting 'Modules'
tap directly on the checkbox next to Phab7, then back out and reboot
after the initial reboot, you can open the Phab7 app and change UIs as many times as you wish without further reboots
Notes
Tablet UI mode is only available when running ICS or JB (v4.03 thru 4.3x). While Phab7 supports KitKat, it does not add back the Tablet mode that Google has removed.
Whether Phab7 works on your device depends almost entirely on your ROM's creators. If they removed the graphics and layouts needed for a given UI mode, SystemUI.apk is guaranteed to force-close when you select that mode. A "Keep-Or-Cancel" dialog will automatically restore your settings after 12 seconds if this happens when you choose an incompatible UI mode. Clear the "Unfortunately" popup and you're good to go.
the Settings-layout feature takes effect when an app is first launched. To see its effect on running apps (e.g. the system's Settings app). tap the "Recents" button and swipe the app away , then reopen the app.
File
Phab7.apk - v1.00
Credits
barrmulio - the first to identify the system changes needed to implement alternate UIs
_TB_TB_ - author of TabletUI trigger who first realized that UI-switching could be done by an Xposed module
History
2014/01/22 - v1.00 - initial stable release
2014/01/05 - v0.99 - added keep-or-cancel dialog
2013/12/13 - v0.97 - added scaling for all modes
2013/12/10 - v0.96 - fixed KitKat-specific bug
2013/12/09 - v0.95 - added Tablet UI scaling
2013/11/30 - v0.92 - added support for KitKat
2013/11/27 - v0.90 - initial release
Gonna try it on S4 v4.3
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------
Ring of FC ;p
Sent from my GT-I9505 using XDA Premium 4 mobile app
Tried it, changes fine to tablet mode. Just a few layout issues. And the nav glow doesn't fade.
See screenshot.
Xperia Z running eXistenZ 4.10 rom.
Subscribed, this looks promising.
{
"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"
}
Sent from Z Beast
For me with android 4.1 only settings work and status bar and nav bar don t work
Sent from my LT26i using Tapatalk
Great job. tested working on CM10. status bar looks monster
it could have better you provided DPI settings along with phab7. though i can manage with app settings
the give attachment is flashable zip i just extracted phab7.apk and installed normally
why this is not available in xposed Repo..
reversegear said:
why this is not available in xposed Repo..
Click to expand...
Click to collapse
I think because it's new and in beta
Sent from Z Beast
Now we need not wait for updated Paranoid!! OK Paranoid does do some of this stuff better/more consistantly than AppSetting and this module, but ...
Great!
Wanna outdo Paranoid: Tablet mode mostly more usable in landscape, so ... get the idea?
EDIT: Results using the mod on my LG P500 running cm-10.2 with 4,4 Google Now launcher: I can use AppSetting module to force this launcher to rotate but it does not handle this correctly.
Settings UIs work as promised! This is what I really missed not having Paranoid.
Navigation bar: Question -- what if I do not use one (phone has HW buttons--remember those)? Module should accept phone setting.
Anyway, tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Went back to default: Icon bar, no navigation bar.
If I remember from Paranoid, tablet mode put notifications bar on the bottom right. Phablet left it on top, opening to half-height, had to change dpi to fit it to screen width correctly. So tablet mode, once working, would either have both at bottom right justified or just the notifications as chosen in the phone's settings! Someone check current Paranoid.
Compatible with KitKat?
Wysłane z mojego Ascend G510 przy użyciu Tapatalka
Don't flash that zip!
reversegear said:
the give attachment is flashable zip i just extracted phab7.apk and installed normally
Click to expand...
Click to collapse
OMG!!!! My apologies! The zip that was posted (in error) was only for the Hisense Sero 7 Pro and contained a tablet-specific mod to SystemUI.apk.
The script in that zip checks for the model, so it should have failed if you tried to flash it on any other device. However, if somehow you succeeded in flashing it, you will have to restore your ROM's original SystemUI.apk. The original, along with SystemUI.odex if present, is in your /system/app folder with '-org' appended to it. If you have problems handling this, I can create an update.zip to do this for you.
Again, my apologies - it was late...
This's amazing. Thanks a lot dev. Looking forward for new versions:laugh:
Saeedblack said:
For me with android 4.1 only settings work and status bar and nav bar don t work
Click to expand...
Click to collapse
Dovidhalevi said:
tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Click to expand...
Click to collapse
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings.
Setting default ui to phablet didn't help either.
Debug log: https://www.dropbox.com/s/zlp89tbus6o23qi/xposed_debug_20131127_194414.log
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
for me it have been FC for first run and after reboot it never appear again but don t have FC
also here you are i attached log that you notice
No TabletUI in KitKat
MMeester said:
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings. Setting default ui to phablet didn't help either.
N7(flo)-Rastakat-franco.kernel
Click to expand...
Click to collapse
Is this a KitKat-based ROM? Sadly, all of the code and resources needed to support Tablet UI have been stripped from Android v4.4. Because Phab7 v0.9 doesn't make provisions for this change, the UI switcher doesn't work. I will fix that ASAP so that at least Phone and Phablet are available. Restoring Tablet UI may be more than an Xposed module can/should do, but I'll investigate...
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Dovidhalevi said:
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
Click to expand...
Click to collapse
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
dolorespark said:
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
Click to expand...
Click to collapse
I first tried it before rebooting, then realized that it cannot work that way and rebooted. Then Phab7 worked as described.
Since wisdonsky operates on the notifications bar, could be that the interaction with tablet mode trying to move that is what is noted.
dolorespark said:
Is this a KitKat-based ROM?
Click to expand...
Click to collapse
Yes.
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Click to expand...
Click to collapse
Sadly, no change in settings app after a reboot. Do you need any logs?
Thank you for looking into the issue.
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Any help appreciated.
Metallijim said:
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Click to expand...
Click to collapse
Phab7 is designed to do as little as possible to achieve its goals - in some cases, perhaps too little. For Phone and Phablet, it does some setup when SysUI starts and that's it. For Tablet, it has to be slightly more intrusive but not much.
Sadly, I had no way to test compatibility mode so I'm not surprised that it has issues. Recovery from most any problem should be as simple as switching to another UI. In this case, getting out of TabletUI, then returning without touching the compatibility button should cure what ails you.
If you get repeated FCs in SystemUI, one way out is to leave the toast up there, then from ADB, delete /data/data/com.e_vertise.dopa.phab7/shared_prefs/settings.xml. When you dismiss the toast and SysUI restarts, you should be back to your device's default settings.
Note: if I understand things correctly, Android may try to reload SysUI's Java code several times using the same process before it gives up and kills that process. Once it restarts SystemUI using a new process, you're certain to be back to normal if you've deleted Phab7's settings file.
We'll soon find out if it works on KitKat. Yes I know how to disable Xposed from recovery. Using it on KitKat doesn't seem to cause any crashes, but it doesn't do anything at all on KitKat.
Sent from my Nexus 7 using Tapatalk 4
I got a wireless charger for my Nexus 5 this Christmas, and was a little disappointed to learn that Android 4.2.2 added a notification sound that plays whenever a device is placed on a wireless charger, but provided no way to disable it. The reason I wanted to silence the notification is because I intend to use the charger in my bedroom, and if I'm up late the little jingle is more than likely going to wake up my wife (who would not be pleased).
Now that Lollipop has rolled out, I am no longer supporting this. I have no way to test it because I don't use Xposed anymore. Sorry. However, I'm working on getting a subset of these settings into the native Android settings instead. Once I've got that down I can post links to the relevant repos here, so that others can cherry pick the changes into their ROMs if desired.
So I decided to throw together an Xposed module to address the issue, since I couldn't find anything else that would work cleanly, and I decided to release it for anyone else who might find it useful.
The module is pretty straightforward, and it provides you with a handful of settings for wireless charging:
Play the system's notification sound when you put your device on the charger
Vibrate when you put your device on the charger
Play a custom notification sound instead of the system one
Wake the display when placing your device on or removing it from a wireless charger
You can enable these in basically any combination you want. Need total silence? Turn everything off!
Wireless Charging Xposed has only been tested on my Nexus 5 running CyanogenMod 11, but it should work on any AOSP based ROMs without issue. I don't know about other system ROMs, but it will work as long as the manufacturer didn't alter the part of AOSP that plays the notification. It does not appear to work on TouchWiz ROMs currently; I may look into this in the future if I have the time/resources, but can unfortunately provide no guarantees/ETAs.
I'm distributing the module here on XDA for now as well as in the Xposed modules repository (web link). If you think this is totally awesome or something, and you feel like "donating", I'm also putting it up on Google Play for $0.99 USD. There are zero differences between the paid version and the .apks here on XDA (i.e. the free one does not have ads). You're not obligated to pay anything if you don't want to. The Google Play page is here.
You can find the source code on my GitHub repository; it is licensed under the GPLv3: https://github.com/eldarerathis/Wireless-Charging-Xposed. Contributions are always welcome!
Feel free to leave questions or comments, and if you find a bug you can let me know in this thread. I may consider suggestions, but I make no guarantees; this is just something I put together with a few hours of spare time to fix something I found to be seriously annoying.
And of course, thank you to rovo89 for the Xposed Framework that made this doable.
Having problems?
Because of the way this module hooks into charging events, it can be a bit picky about the order that you enable things. It's something that I'm working on, but for now, make sure you perform the installation in this order:
Install the module and activate it in your Xposed Installer
Reboot your device
Open the module's settings page and configure it however you'd like
At this point, Wireless Charging Xposed is known not to work on Samusng devices that are running TouchWiz ROMs. If you have another device with a non-AOSP ROM, your results may vary. If you think you've found a bug, please take a peek at your Xposed logs (open the Xposed Installer and tap the "Logs" item) and attach anything that might be relevant.
Changelog:
v1.0 - Initial release
v1.0.1 - Fix a suspend blocker that may have caused excess battery drain
v1.1 - Add the custom notification sound setting
v1.2 - Add the wake on charge setting; Bulgarian translations (by mamutcho)
v1.3 - (apk removed) Add the wake on undock setting; fix the summary text of the custom ringtone preference
v.1.3.1 - Fix a potential crash when trying to resolve the custom ringtone name
This is exactly what I wanted and it works on stock ROM. I wanna pay for this app!
Sent from my mobile device using an app.
If you are going to add anything, maybe a way to select a sound to use as well.
Meowdib said:
If you are going to add anything, maybe a way to select a sound to use as well.
Click to expand...
Click to collapse
That was the one additional thing I was already considering, so I went ahead and added it this evening.
Buddha almighty! So happy! I hate the wireless charging notification with a burning passion. Thank you for the module!
Cool... I have used a workaround for this (replaced the wireless charging sound with a silent ogg file), but this is way easier.
Thanks!
I'm having a problem getting it to play a custom sound. It will play any stock sound that comes on the phone, but when I put sounds I download from the internet or the ZEDGE app, it will not play them. Any idea why?
JakeyEck said:
I'm having a problem getting it to play a custom sound. It will play any stock sound that comes on the phone, but when I put sounds I download from the internet or the ZEDGE app, it will not play them. Any idea why?
Click to expand...
Click to collapse
What type of files are they (i.e. MP3, OGG, etc) and where are they stored on your phone? I'll see if I can reproduce that when I have a chance.
I will note that the current implementation is intended to only allow you to pick things that are considered "notification sounds" by the system. The reason for that is because if you picked, say, a song file then when you put your device on the charging plate the entire song would play, with no way to stop it. That seemed like it would be kind of silly, so I write the code to support that scenario. Not saying that's what the problem is in your case, though.
eldarerathis said:
What type of files are they (i.e. MP3, OGG, etc) and where are they stored on your phone? I'll see if I can reproduce that when I have a chance.
I will note that the current implementation is intended to only allow you to pick things that are considered "notification sounds" by the system. The reason for that is because if you picked, say, a song file then when you put your device on the charging plate the entire song would play, with no way to stop it. That seemed like it would be kind of silly, so I write the code to support that scenario. Not saying that's what the problem is in your case, though.
Click to expand...
Click to collapse
It may sound silly, but I wanted it to play a Mario power-up mp3 file when it was put onto the charger. It was a mp3 file I had downloaded and stored on my phone. It probably isn't considered a notification sound by Android though.
EDIT:
Well I tried it just now and it is working like I wanted it to. I'm not sure why it didn't work the first couple times.
JakeyEck said:
It may sound silly, but I wanted it to play a Mario power-up mp3 file when it was put onto the charger. It was a mp3 file I had downloaded and stored on my phone. It probably isn't considered a notification sound by Android though.
EDIT:
Well I tried it just now and it is working like I wanted it to. I'm not sure why it didn't work the first couple times.
Click to expand...
Click to collapse
After having it for a day, it only seems to work with my downloaded mp3 file 1/5 times. I don't know what is keeping it from working all of the time.
JakeyEck said:
After having it for a day, it only seems to work with my downloaded mp3 file 1/5 times. I don't know what is keeping it from working all of the time.
Click to expand...
Click to collapse
Just out of curiosity, was your phone close to fully charged when you were testing this? I noticed the other day that the system doesn't fire the "charging began" event if your battery level is above a certain threshold (looks like 95% in AOSP). My assumption is that this is so that it won't notify you constantly once it hits 100%, because the charging circuit probably cuts out at that point, lets the battery drain a little bit, then bumps it back up to 100 (and repeats that cycle).
For what it's worth, I'm having trouble getting it to play any custom sound, even stock Android sounds. It does mute things nicely, though
Before installing this module, I noticed that the charging sound would frequently get clipped (cut off in the middle). Not sure if that's related. I also have Gravity Box installed, so it could be a conflict.
this is a very useful mod..
but still not complete.. hahaha
can add more features?
i have problem with overheated on custom roms/kernels.. not all but few of it.. sometimes im worried if my device is overheating and i have to keep unlocking my phone to see the temperature - thanks to dashclock battery extension
i still couldn't find any app to enable sound notification.. LED notification is not enough..
so can u add enabling notification if device is overheat?
anyway thanks a lot for this!! great work man! :good:
@eldarerathis
Huge THANKS for this mod and confirmation of functionality on purity 14/12. :good:
{
"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"
}
P.
[sntfrmnxs4]
eldarerathis said:
I got a wireless charger for my Nexus 5 this Christmas, and was a little disappointed to learn that Android 4.2.2 added a notification sound that plays whenever a device is placed on a wireless charger, but provided no way to disable it. The reason I wanted to silence the notification is because I intend to use the charger in my bedroom, and if I'm up late the little jingle is more than likely going to wake up my wife (who would not be pleased).
So I decided to throw together an Xposed module to address the issue, since I couldn't find anything else that would work cleanly, and I decided to release it for anyone else who might find it useful.
Click to expand...
Click to collapse
Love it, but the vibrate option doesn't work on my Droid MAXX, rooted and Xposed but stock beyond that. I can send you any data you need.
wireless charging sound
I have wireless charging installed and xposed but it plays no sound.no mp3 no stock sound nothing.want can i do?
waw this will work all aokp rom?
Sent from my V9 using Tapatalk 4
naifaharsy said:
waw this will work all aokp rom?
Sent from my V9 using Tapatalk 4
Click to expand...
Click to collapse
Make a nandroid and just try it, buddy.
P.
[sntfrmnxs4]
sgp77 said:
For what it's worth, I'm having trouble getting it to play any custom sound, even stock Android sounds. It does mute things nicely, though
Before installing this module, I noticed that the charging sound would frequently get clipped (cut off in the middle). Not sure if that's related. I also have Gravity Box installed, so it could be a conflict.
Click to expand...
Click to collapse
I noticed the clipping and some other aberrations on CM without any kind of Xposed modifications, so I'm wondering if it's something in the system that's causing it. I'm hoping that's not it, but if it is then I'm not sure if I can fix it
dtreth said:
Love it, but the vibrate option doesn't work on my Droid MAXX, rooted and Xposed but stock beyond that. I can send you any data you need.
Click to expand...
Click to collapse
Can you take a look at the Xposed logs and see if there's anything unusual? Just tap the "Logs" item on the Xposed Installer's main screen and check the most recent entries at the bottom. Also, does the sound work, or is that busted too?
kalowski said:
I have wireless charging installed and xposed but it plays no sound.no mp3 no stock sound nothing.want can i do?
Click to expand...
Click to collapse
I guess first would be some general troubleshooting, like checking to make sure your system volume isn't muted or anything. Does it play the sound without the module installed, completely stock? Is your battery below 95% when you start charging it?
Anyone having difficulty with custom sound files:
I can't reproduce the problem on my N5, but I re-implemented the piece of code that does the playback to use a different method. A test build of the .apk is attached to this post, so give it a try and see if it makes a difference. You may need to toggle the custom sound option off and then back on again before the first time you try.
If it doesn't work, check your Xposed logs and see if there is anything there. It should write some information if the playback fails due to an exception or error. If there's nothing there and it doesn't work, then let me know:
What kind of phone you have
What version of Android you have
What ROM you're using (or "stock", if you're not using a custom one)
...and I'll see if I can figure out what's going on.
System: Android 2.3.7 (Gingerbread) - Discontinued October 13, 2014
About:
NOTE: The instances of spontaneous reboots deactivating the SIM card slot mentioned below may have been the result of a dying SIM card. I have redacted the comments.
After using Traveller DSC for a while, I discovered one annoyance that I couldn't overcome. In Traveller DSC, at least on my Streak, leaving the WiFi on and letting the Streak sit idle for a period of time caused the device to spontaneously reboot. While the spontaneous reboot is a known issue with stock Gingerbread ROMs, on my Streak the reboot also deactivates the SIM card slot until manually rebooted. The SIM card slot being deactivated only appears to occur if there is no cellular service and if the SIM card from that cellular service is left in the Streak. After encountering this spontaneous reboot and having to deal with the aftermath on a regular basis, I tired of it and thus polished off a solution that I had sitting on my hard drive.
PseudoCream uses hPA's CyanogenMod 7 as the base ROM while adding what I believe are the best features of DSC/Traveller DSC, notably the dsc_firstboot post-install system. PseudoCream, like Traveller DSC, uses a swapfile to improve performance. However, based upon the discussions regarding the swapfile for Traveller DSC 2.4.x, only 64MB of RAM is reserved for the swap file in PseudoCream, which should provide a fair balance between memory usage and speed. Last, but not least, hunderteins SSL Ciphers improvements and Bash updates have been incorporated into this ROM. From the Cyanogenmod side of the equation comes full language support for Arabic as well as theme support using the Theme Chooser. Both eliminate the need to extensively modify apps to get the desired appearance.
Internally I refer to this ROM as Traveller DSC 2.5.0 and consider it an upgrade to Traveller DSC 2.4.6. Other than a forthcoming patch to reduce the size of the swapfile in 2.4.6 to 64MB, there will be no further updates to the 2.4.x series of ROMs.
Flashing Guide:
Download the ADB Tethering Drivers.
Download MultiFlasher.
Download PseudoCream.
Install the drivers.
Connect the Streak to the computer with the data cable.
Turn the Streak off. Hold the camera button down while pressing the power button to enter engineering mode. Press the fastboot button in the upper right corner of the screen to enter fastboot mode.
Open MultiFlasher, select a baseband (366 or 406 recommended), and flash it.
Reboot and enter fastboot mode again.
Open MultiFlasher and flash StreakMod or ClockworkMod recovery.
Reboot. Hold both volume buttons down while rebooting to enter recovery mode. If on a stock ROM, failing to do this will cause the new recovery to be overwritten.
Select "Software upgrade via Update.pkg on SD Card" to access StreakMod/ClockworkMod recovery.
Using the volume buttons, navigate to "advanced", then select "Mount SDCard" to be able to access the MicroSD card from the PC.
Copy PseudoCream to the root of the MicroSD card.
Unmount the card then press the back button until the opening menu appears.
Navigate to "apply sdcard:update.zip" and choose PseudoCream.zip, then press the camera button and select "Yes" to install.
When the installation is complete, press the back button to go to the main menu of the recovery and select "wipe data/factory reset".
Reboot and enter recovery mode again.
Select option 1 from the Dell recovery menu and let the device boot.
Aroma Bugs:
Arabic and Hebrew text in Aroma may appear backwards due to lack of right to left support. The ROM itself does not have this issue.
Touchscreen support in Aroma is erratic. Scrolling using the touchscreen does not function, and it may require a few taps to get selections to properly register. As an alternative, the volume controls and the camera button can be used to navigate and select items. This is likely a hardware issue and not fixable in Aroma.
ROM Bugs and Minor Inconveniences:
BUG: Very rarely, the Streak may fail to wake when idle for a period of time. Install SetCPU or a similar app and set the minimum clock speed for the CPU to 245MHz, which should help with this problem. Pulling the battery may be necessary to resolve this otherwise.
BUG: Google Maps may cause excessive battery drain. Freeze Maps or uninstall it if this issue is encountered.
BUG: USSD codes accessed without an active mobile connection leave the screen dimmed as if the notification shade were pulled down, requiring a reboot of the Streak to correct.
INCONVENIENCE: When reboot is selected on the shutdown menu, a menu appears with Reboot, Reboot Recovery, and Reboot Bootloader. The Streak does not support rebooting directly to the recovery or the bootloader, and thus the menu is useless. Disable the menu in Cyanogenmod Settings > Interface Tweaks > Power prompt.
INCONVENIENCE: The digital zoom of the camera appears to function, but the resulting pictures ignore the digital zoom. Since digital zoom results in a loss of picture quality, this isn't as much an issue as it appears. The zoom however does appear to function when taking videos.
INCONVENIENCE: App setup from dsc_firstboot.zip may take a while.
INCONVENIENCE: By default auto-rotation is not activated in settings. In addition, the phone dialer has its own auto-rotation settings that will need to be enabled. The call screen also has its own auto-rotation settings (located in Settings > Call Settings).
INCONVENIENCE: Checkboxes do not appear in the browser. Go into Theme Chooser, select the system theme, apply it, then select the ICS theme and apply it to fix.
INCONVENIENCE: The power toggles in the notification pulldown by default are in green. Changing the color, if desired, is in Cyanogenmod Settings > Interface Tweaks > Notification power widget. There is an option named "Indicator Color" to change the color, or the indicators may be totally hidden by using the "Hide Indicator" option.
Tips:
If you wish to bypass the setup wizard for some reason, tap the four corners of the screen in a clockwise manner (upper left, upper right, lower right, lower left). Tip courtesy of pocketnow.com.
Disable notifications in SuperSU for a clean look and to speed up the boot process.
SuperSU will receive updates from the Play Store. To save storage space convert the update to a system app.
HoloLauncher has the ability to hide apps in the app drawer. If you know you're never going to use a particular system app, e.g. the email client, hide it instead of deleting it from the ROM.
Customize dsc_firstboot.zip to meet your needs. For example, if you use Google Earth, rename the APK file to com.google.earth.apk and add it to dsc_firstboot.zip. For a tutorial, look here.
Google Car Home was left in /system/app because if uninstalled it cannot be downloaded from the Play Store.
The original release of the Hangouts 2.0 app (from Android 4.4) had a bug which allowed it to work on Gingerbread. If wishing to use Hangouts in place of the stock Messaging app, set the app to not be automatically updated in the Play Store or you will lose SMS capability when the app updates.
Included in dsc_firstboot.zip is an app named "Home-Dock Enabler". When the Streak is plugged in to its charger or inserted into its docking base, the app will call up the desk clock instead of displaying the lock screen. Home-Dock Enabler by default does not appear in HoloLauncher's app drawer but only in the app list in Settings. If wishing to uninstall this app, it must be done through the Settings > Apps menu.
Links:
ADB Tethering Driver (Mega)
MultiFlasher (Mega)
PseudoCream (Mega)
407 ROM (Dev-Host links removed)
Updates
NOTE: when a new patch is released, a new version of the ROM will also be released. The patch is a convenience for those who have already installed the ROM.
Update 6 to PseudoCream has the following enhancements:
Updated Play Store app to 5.0 version.
Updated SSL and Bash files.
Download (Mega)
First I would like to thank you for keeping this phone alive with newer roms.I'm trying to update mine .I have a Streak that is running a stock 2.2.2 rooted retail rom with baseband 360.Do I have to flash the 407 rom and recovery and then change the baseband (which one would you recomend?), then update to your rom?
I can really use your help before I try to do this.A while back I got stuck on the Dell logo and getting out of it was not fun!!
Thanks again
Sent from my Dell Streak using Tapatalk 2
mariasnowhite said:
Do I have to flash the 407 rom and recovery and then change the baseband, then update to your ROM?
Click to expand...
Click to collapse
No. Flash StreakMod recovery, then flash the baseband. From there install PseudoCream. The 407 ROM links are provided as a convenience. If someone encounters issues installing PseudoCream, installing the 407 ROM and recovery will give them a fresh starting point from which to try again.
mariasnowhite said:
Which one would you recommend?
Click to expand...
Click to collapse
The flashing guide in the first post gives the two recommended basebands, but any baseband will work as the kernel doesn't check for mismatched basebands. I personally use 406. Supposedly 366 has better call quality but I can't tell the difference.
"No. Flash StreakMod recovery, then flash the baseband. From there install PseudoCream"
Thank you you saved me some time there.
I had a rom in the phone that was causing the lights to blink all the time. I'm trying to avoid that with this one.
I'll give it a try soon. Thank you again!
Sent from my Dell Streak using Tapatalk 2
That's because the ROM in question used a stock kernel, which does the baseband check. The kernel here is not a stock kernel.
Strephon,
Just FYI, for the camera issue, I've test for the Video mode, the digital zoom is working for the recorded video using the zoom control from the display panel (-/+), unlike in picture mode where the zoom function is only working for viewing and not to the resulting picture.
This is my second day in using new DSC 2.5 (PseudoCream) with full of my daily app, previously I use Mokee ROM,
Here are my review:
- At the first start up, you might get confuse with google account registration setup wizard that will looping back couples time, but as already stated by Strephon, First, wait few seconds until all icons at the notification bar (on top bar) appeared completely (mobile signal, battery, cyanogen).. and then start to continue to select the first option of setup wizard.
- You might feel a lag and slow in navigating menu, but this happened only for the first startup because the system still installing the application (apk in dsc_firstboot.zip). just let it finishing the installation in few minutes. and reboot it again.
- After a second boot, the ROM is running more responsive.
- Mobile data, wifi, Auto switch wifi/mobile data, GPS, wifi/usb Tethering, USSD code, SMS/phone call, ear phone, USB data connection, (mm. what else,.?) all working fine. :good:
- There also some addition so called "Home-Dock-Enabler", nice :good:
- Terminal emulator might have a little bug (cannot exit by command), as Strephon said, that is because the apk is not up todate, I have test to install a latest version from google, and it working fine.
- As already stated by Strephon, the digital zoom of the camera appears to function, but the resulting pictures ignore the digital zoom, but in Video mode its working fine.
- Have never been experiencing FC so far..
- Tested to put it in idle condition for 3-4 hours, have no problem to wake it up.
- Antutu Benchmark result may vary, sometime high (3800), sometime low (3200). Could that be the CPU was set in conservative mode (?)
- battery power info seem to be inaccurate (clear battery stat in recovery mode, already), but that probably because I use highcap battery (?)
with 1% left, I still can play a game, music for an hour or more, running benchmark, etc.
That is my review base on what I use for my daily usage. I might missed in reviewing some other part.
Over all, I'm happy and satisfied with this room.
Thank you Strephon for giving another breath to our DS5.. :good::good::good:
Home/Dock Enabler is in there because CyanogenMod doesn't support the Dell Dock. While the enabler won't magically enable the HDMI output function of the Streak, at least the Streak goes into desk clock mode when plugged in to the cradle, or even if plugged in to the cable by itself.
I'll check out the updated Terminal Emulator myself, but your results sound encouraging in that regard.
Woah, new ROM for old DS5..
Thanks again for your hard work..
I've used DSC Traveller for long time, since there are no more stable ROM for DS..
I'll try this ROM and give the feedback soon :good:
Nice ROM
but should be have JB Patch as like PCM7 JB Patch ROM
I'm waiting for new update of added JB Patch on this ROM
Stability is more important to me than the look.
Under some very narrow circumstances Traveller DSC 2.4.x proved to be very buggy. The spontaneous reboots never really got solved, although I suspect reducing zRAM to 64MB helped. In my case the SIM card slot would be disabled on one of these reboots until I rebooted again. That gets tiring after a while, and I blame no one for complaining about it. Using CyanogenMod as a base and adding in the good stuff from DSC/Traveller DSC cured the stability issues to my satisfaction.
Regarding the look, you'll be waiting a long time. Using Sonny Sekhon's ICS theme gives me the "Touch of ICS" look Traveller DSC has, which was all I cared about in the looks department. I had no intention of making major appearance changes to the ROM and could have just as easily used Androidian, Cyanbread, or one of the multitude of free themes in the Play Store as the default. Reason being I have little free time available between book editing gigs and my day job and I prefer to spend that time away from the computer.
No...I mean...
I'm not talking about theme or look'n'feel...
I need JB Patch because I want setting menu on the right-top in status bar
{
"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"
}
and...there is no Disable Fullscreen on Tablet Tweaks menu???
It's not that you need it, but want it. I have no plans on adding such a feature. With HoloLauncher having a settings link in its menu the feature I feel is redundant.
As to that missing feature, this is straight CyanogenMod, meaning hPA's source ROM. As a result some things that may be in PCM7 and/or Mokee are not here.
Oh...
Allright if you say that...
But on this ROM,default net.ipv4 memory reserved buffersize in build/sysctl is 6144,xxxx...? not 4096,xxxx...?
How to edit this value permanently???
Sent from my Dell Streak using xda app-developers app
Pull build.prop to the PC, open it in notepad++, and make the changes there. Then push build.prop back to the device, change permissions to rw-r--r-- and reboot.
zane19775 said:
Oh...
Allright if you say that...
But on this ROM,default net.ipv4 memory reserved buffersize in build/sysctl is 6144,xxxx...? not 4096,xxxx...?
How to edit this value permanently???
Sent from my Dell Streak using xda app-developers app
Click to expand...
Click to collapse
I think you can use buildprop editor apk to edit it, but may I know what this setting for?, and what is the impact in changing the value?
Essentially he believes the settings in PseudoCream are somewhat wasteful in regards to RAM and he wants to adjust them. Either that or he's simply surprised it's not set to the default.
These settings determine how well the network performs. More details at http://www.cyberciti.biz/faq/linux-tcp-tuning/
Yes,you're right
Sometimes my network not stable when net.tcp is set 6144,xxxx...
But,I have question again...
When I charging Streak...the screen showing n running app 'clock'
what that's mean??? can I disable it?
Seems like disturb for me...
zane19775 said:
Yes,you're right
Sometimes my network not stable when net.tcp is set 6144,xxxx...
But,I have question again...
When I charging Streak...the screen showing n running app 'clock'
what that's mean??? can I disable it?
Seems like disturb for me...
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
System: Android 2.3.7 (Gingerbread)
[*]Included in dsc_firstboot.zip is an app named "Home-Dock Enabler". When the Streak is plugged in to its charger or inserted into its docking base, the app will call up the desk clock instead of displaying the lock screen. Home-Dock Enabler by default does not appear in HoloLauncher's app drawer but only in the app list in Settings. If wishing to uninstall this app, it must be done through the Settings > Apps menu.[/LIST]
Click to expand...
Click to collapse
Its called "Home-Dock Enabler", you can uninstall it.
---------- Post added at 11:38 AM ---------- Previous post was at 11:32 AM ----------
Strephon,
As explained that the SSL Ciphers already applied in this ROM, How can I check it?
The HTC Sense Car Mode app had some features removed or changed from the previous versions. Namely, statusbar pulldown has been blocked, along with switching apps and basically multitasking.
The reason for this is probably safety; to discourage drivers from tinkering too much with their phones while driving - and while I'm fully behind that I believe in giving people options - which is why I created this module!
So far it allows you to:
Bring back multitasking (status bar and 'recent apps' functionality).
Release the 'Home' button to let it go back to the default launcher.
Replace the default 3-Tap gesture action with anything you want!
Turn Wi-Fi and GPS on or off at startup and shutdown.
Bypass the exit confirmation dialog.
Automatically close apps opened from within the Car App on shutdown (requires root to be fully functional!)
And more features coming in all the time!
If you love the HTC Car app as much as I do, you'll enjoy this!
{
"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"
}
Download
You can find it on the Xposed repository right here.
(It's marked as 'beta' so set your installer filter accordingly).
XDA:DevDB Information
HTC Car Mode Xposed!, Xposed for the HTC One (M8)
Contributors
Ambious
Source Code: https://github.com/eladavron/HTCCarXposed
Xposed Package Name: ambious.htccarxposed
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2014-11-02
Current Beta Version: 2.3
Beta Release Date: 2015-05-15
Created 2014-06-01
Last Updated 2015-05-16
Changelog
Latest Versions:
Version 2.3 Pulled! This version seemed to cause other things to malfunction.
Version 2.2
Added Sense 7.0 Compatibility
Fixed an issue with the screen not staying on in older versions (Android 4.4)
(Not Tested on Sense 6.* Versions!)
Version 2.1
Fixed a bug that would cause the 3-finger gesture to crash the "Car" app even when not running.
Added a "Logging" option for better future debugging (saves log to file on the SD Card).
Version 2.0:
Now Lollipop Compatible! (not tested on KitKat)
Click to expand...
Click to collapse
Older Versions:
Version 1.9:
Added the option to turn off the screen when exiting the car-app - requires enabling Administrator Privileges (prompted when enabled).
Version 1.8:
Brought back the GPS startup and shutdown mods, should work fine now.
Version 1.7:
Added the option to override the "3-Fingers tap" gesture with either Google Hands-Free, Google Now or a custom app of your choice!
Fixed a bug with the Toggler where it would launch the settings app instead of the car if triggered by 3rd party app (such as NFC or Tasker).
Version 1.6:
Added the "App Toggler" which allows to shut down the car app through a global shortcut, or launch it if it's already closed.
Fixed a bug where Wi-Fi would turn off even by navigating away from the Car app and not just closing it.
Re-did the icon - again! (One day I'll be pleased with it).
Click to expand...
Click to collapse
Version 1.5:
Fixed "Multitasking"! Yes, the "Recent Apps" button now works and doesn't break anything! Thanks to the brilliant RichmondoUK for pointing me in the right direction.
Removed GPS mods - it wasn't working as well as I had hoped due to android privacy overrides.
Click to expand...
Click to collapse
Version 1.4:
Added 'Exit mods':
Change GPS and Wi-Fi states on exit
Close apps opened from the Car App (either using a regular shut-down which doesn't always work or the more powerful 'root' method).
Moved the "Exit without confirmation" option under this category
Some code touch-ups
Still no fully-working multi-tasking mod, sorry... that's one tough nut!
Click to expand...
Click to collapse
Version 1.2:
Default settings will bow be applied upon installation.
Added an option to bypass the exit confirmation dialog
Added the option to turn GPS and Wi-Fi on or off at startup.
You can also choose to - obviously - not change them at all.
I'm still working on turning them on and off when exiting the app, it's not working so well so far...
Click to expand...
Click to collapse
Version 1.1:
Interface added! You can now turn mods on and off selectively.
Added the option to release the 'Home' button.
New icon, slightly less ugly I hope.
Click to expand...
Click to collapse
Information
Why disable a safety feature?
The HTC Car App introduced those blocking 'features' for an obvious reason: to discourage people from fumbling around with their phones while driving.
That's a good and important cause, but unfortunately it's not a very smart method of doing it - which is why this module was created. Consider the following scenario: You're in your default navigation app with the music player (which is controllable by the car app) running in the background. You want to skip the currently playing track. If everything's at stock, the new restrictions make it an annoyingly long process: You have to click the home button, enter the music control applet, skip the track as you normally would, then click the home button again, find the navigation app's icon and re-launch it. Without those restrictions all you do is pull down the statusbar, click the 'skip' button on the music player's active notification tile, and pull it back up.
HTC's restrictions - which are supposed to increase safety and attention while driving actually make it longer and more attention-consuming to perform such tasks.
This module allows you to overcome those restrictions, mostly, but I must still say - and I can not overstate this enough:
DRIVE SAFELY!
DON'T OPERATE YOUR DEVICE WHILE DRIVING !
Play music, navigate, make and take calls - but do so safely without fumbling around.
If anything doesn't work with less then three touches of the screen, or if it requires you to look at your device for more than a split-second glance - either forget about it or pull over! It's not worth it!
Works as advertised. Upgraded from Sense 5.5 just so I could enable this mod and get to my notifications. Thanks!
Very cool. I use the HTC car app quite a bit and always hated that I had to close it to access anything else. What other tweaks are possible? It would be nice to be able to switch the default music app to Google Music. Disabling wifi on launch would also be slick.
BTW, this works fine on the M7 with Sense 6.
linuxsense said:
Very cool. I use the HTC car app quite a bit and always hated that I had to close it to access anything else. What other tweaks are possible? It would be nice to be able to switch the default music app to Google Music. Disabling wifi on launch would also be slick.
BTW, this works fine on the M7 with Sense 6.
Click to expand...
Click to collapse
Currently I'm mostly battling with basic things like making the 'recent apps' button work and making the settings toggleable without restarting. Once I get the basics working, I'll start seeing what else I can tinker with. Switching the default music app is not going to be easy because it's deeply integrated within the app, but I'll see what I can do.
As for the wifi, that shouldn't be too difficult.
Glad to hear it's working on other devices as well.
Please add support for all apps in car mode! Currently you can add only a few apps .. For example you can't add Torque
Looks like the 1.1 version changes caused it to stop working with the M7 :crying:
ETA: Looks like it functions properly if "take over home button" is disabled. With that unchecked you can access the pulldown menu as well as reach the desktop or recent apps using the home button.
linuxsense said:
Looks like the 1.1 version changes caused it to stop working with the M7 :crying:
ETA: Looks like it functions properly if "take over home button" is disabled. With that unchecked you can access the pulldown menu as well as reach the desktop or recent apps using the home button.
Click to expand...
Click to collapse
It might be something else, I noticed that the settings won't take until you run the settings interface at least once.
Please try to re-enable the setting and see if anything changes.
Thanks for the report!
Ambious said:
It might be something else, I noticed that the settings won't take until you run the settings interface at least once.
Please try to re-enable the setting and see if anything changes.
Thanks for the report!
Click to expand...
Click to collapse
I am pretty sure that I ran settings app prior to trying it out, not completely sure though. I just toggled the home screen option and get the same results. It only works if it is not selected.
linuxsense said:
I am pretty sure that I ran settings app prior to trying it out, not completely sure though. I just toggled the home screen option and get the same results. It only works if it is not selected.
Click to expand...
Click to collapse
Hmm. I'm not getting that on the M8, but I'll look into it.
Unfortunately I don't have an M7 to test on.
Could you for the sake of testing go to the settings interface - uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!
Ambious said:
uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!
Click to expand...
Click to collapse
Its work :good::good::good: thanks
ahlot18 said:
Its work :good::good::good: thanks
Click to expand...
Click to collapse
Thanks for the info, I think I know what's causing it:
The mods don't take if the car app is running in the background because it hooks into methods as they load.
There's a command to kill it if it's running in the background and settings have been changed, but it might not have taken - or rather, it also won't be run if settings are at their default state, so if you install the mod, then run the car app, then load the module interface and change nothing - it still won't be set.
Next version will handle this more properly, I hope (currently writing it).
Reyzis said:
Please add support for all apps in car mode! Currently you can add only a few apps .. For example you can't add Torque
Click to expand...
Click to collapse
I can add Torque to Car...?
agentdr8 said:
I can add Torque to Car...?
Click to expand...
Click to collapse
Torque free or the paid App? I have torque free and can't add it to car mode ... :/
Reyzis said:
Torque free or the paid App? I have torque free and can't add it to car mode ... :/
Click to expand...
Click to collapse
Torque paid. Maybe free is different, but from what I can tell, HTC Car doesn't blacklist any apps from being added to one of the screens.
I agree, there doesn't seem to be a limit on which apps you can add and which you can't.
Your issue must be related to the app itself. Since I'm unfamiliar with Torque, I really can't tell.
Are there any other apps, as far as you can tell, that you can't add?
Ambious said:
Hmm. I'm not getting that on the M8, but I'll look into it.
Unfortunately I don't have an M7 to test on.
Could you for the sake of testing go to the settings interface - uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!
Click to expand...
Click to collapse
If I do that when I run the HTC car app the home button will open recent apps if double tapped but otherwise it just returns to car mode when home is pressed. If I disable it pressing home takes me to the desktop and double tapping it takes me to recent apps. I am running NuSenseSIX based off the m8-base fwiw. If you have any tweaks you would like tested let me know, I can provide logcats and such.
Dialer not working
Thank you for this awesome mod. I'm not sure if it's the ROM I'm running, but I can't seem to launch the dialer using this module. All other buttons work normally, as well as the added functions of this module.
I'm running the Venom ROM on the M8.
Does anyone else have this problem?
dafob said:
Thank you for this awesome mod. I'm not sure if it's the ROM I'm running, but I can't seem to launch the dialer using this module. All other buttons work normally, as well as the added functions of this module.
I'm running the Venom ROM on the M8.
Does anyone else have this problem?
Click to expand...
Click to collapse
Good catch. Just shows how much I actually use my 'phone' for calls...had not even tried it yet :laugh:
I have the same issue on an M7, the 'Dialer' button in the car mode app doesn't do anything.
{
"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"
}
To God be the glory, my Slim7 Nougat project finally works on the Note Edge!
This is a very slimmed down version of Android Nougat, almost a "vanilla" experience with a few tasteful perks! By design, this ROM comes without root for those who wish to have a "pure" version without the entanglements that come with root, but it can also be easily rooted by using chainfire's SuperSU (see below for instructions and downloads). In it's default form, it is perfect for those banking apps, workplaces, and games that require you to have a phone without root. No need for tricks or hacks, all while having the latest and greatest Android on your Samsung Galaxy Note Edge.
If you do decide to use root, then you will be pleasently surprised to know that Substratum and layering works with this ROM. While not perfect, for the most part it functions well in my initial testing. However, if you find problems arise after installing a theme, please remove the theme to make sure it is not a substratum related issue.
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
This SlimRoms Nougat ROM was built for the TBLTEXX using modified LineageOS TBLTEXX trees. I have only tried this on a TBLTETMO device, using the datazip files, but you are welcome to try it on anything AT YOUR OWN RISK. The updater script would need to be edited for something other than TBLTE, TBLTEDT, TBLTEXX, TBLTETMO, TBLTECAN. Chime in if it worked on your device.
A huge thanks to the SlimRoms Project team!
Disclaimer: SlimRoms is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
Click to expand...
Click to collapse
A huge thanks to the SlimRoms team!
Another huge thanks goes to mickey387 for pioneering Nougat on the Note Edge!
Downloads:
Rom Download link:
http://www.mediafire.com/file/68325...-7.1.1.build.0.7-UNOFFICIAL-20170223-0955.zip
SuperSU download: (There may be other versions, 2.79 is the only version I personally tested.)
http://www.supersu.com/download
Gapps link:
http://opengapps.org/
-Which I personally only tested Nano. Be sure to choose "Arm" and "7.1".
If you want the AKLU kernel - Better performance and battery life:
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
Be sure to only choose the SLIM 7 version.
TBLTECAN and TBLTETMO users may use the Data Zip files here:
https://forum.xda-developers.com/no...ment/ril-data-fixes-6-0-1-bootloader-t3546110
However, there is a TBLTETMO/TBLTECAN version of this rom in the T-Mobile thread, but I did test that this worked.
This Rom has been stable for me, however, Nougat is new, so be prepared for some little hic-ups here and there. Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
!!!FIRST BOOT TAKES LONGER THAN 5 EARTH MINUTES TO COMPLETE!!!
!!!IF YOU FLASH SUPERSU, IT WILL REBOOT SEVERAL TIMES DURING INSTALL, THAT IS OKAY!!!
Installation instructions ( TO BE NON-ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and if desired, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
--> OPTIONAL - After first boot, then go back to recovery and install the AKLU kernel. (Note that without root, you cannot change the settings of the kernel, and it is a bit agressive in the default state.... I don't recommend this for non-rooted phones.)
--> OPTIONAL - TBLTETMO/TBLTECAN users can flash the data zip files after the first sucessful boot.
Installation instructions ( TO BE ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and SuperSU, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps -- Optional.
-Let the system boot up.
-Go back to TWRP.
-Install AKLU kernel. - Optional
-Reboot to system.
-Go back to TWRP.
-Install SuperSU.
-Let the system boot up. Note that it may reboot a couple times during the boot animation, that is okay.
--> OPTIONAL - TBLTETMO/TBLTECAN users can flash the data zip files after the first sucessful boot.
-Enjoy!
Code:
What works:
So far everything that I have tried works, such as
- Camera for video and pictures (use orange camera app, not traditional blue camera app.)
- Phone calls/receiving
- Data 2g/3g/LTE
- Bluetooth
- WiFi
- PTP/MTP
- GPS
- WiFi hotspot
- Multi-Window
- Fingerprint sensor* See notes.
etc....
What doesn't:
- Notification LED only shows RED and YELLOW. To show YELLOW, choose CYAN as the notification color, and it will show up YELLOW. All other color choices appear RED.
- The automatic time zone function forgets where you are alot. Use the manual time zone instead.
- Choosing to reboot the phone sometimes takes a loooong time. It may be better to Power off and then start the phone, which is faster for some reason.
- Built in blue camera app sometimes gets "stuck" or freezes or crashes, I tested several other camera apps, and all worked fine, including the orange camera app and opencamera from the fdroid repository.
- There is no "edge" feature at this time.
- Let me know in the forums if you find other issues.
Main Features:
- Merged with android-7.1.1_r13
- SlimDim, now with 100% more dimming
- SlimAction, Splits screen action (long press app in slim recent)
- SlimRecents, an alternative recents
- Notification log (long press statusbar header)
- Kill app from notification (long pres app notification)
- Substratum support (if rooted)
- OmniSwitcher built in so the kill function works with or without root.
- Advanced reboot (found under security settings).
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
ROM OS Version: 7.1.1 Nougat
ROM Kernel: Linux 3.10.40
Based On: AOSP and LineageOS.
My device trees: https://github.com/alaskalinuxuser/
Created 2017-02-23
Last Updated 2017-02-24
Change log:
Code:
20170223
-Fixed home button screen wake.
-Fixed WiFi hotspot.
-Added texting app.
-Added OmniSwitcher as optional switcher/tasker (makes a good "edge bar" since you can pin apps).
-Initial release!
Notes about the rom:
Fingerprint sensor:
I have successfuly used the fingerprint sensor, but it is a bit sketchy. To make it work:
- Go to register your fingerprint under security settings.
- I registered all 5 of my fingertips all at once, by clicking add another, and only 2 of them "stuck" when I clicked done. I redid it registering one finger over and over again several times, and it eventually registered and stuck.
- If after clicking done, the fingerprint settings says x-number of fingerprints registered, then those fingerprints are working. Once registered, then you can use it in apps, and for the lockscreen, which did work about 1/2 of the time for me.
- If the lockscreen does not show the "fingerprint" icon, reboot to make it appear.
Open Source apps:
There are quite a few really good open source apps included in this build, such as:
Browser app
Amaze file manager app
SatStat GPS app
Camera app (orange one)
All of these great apps and more can be found at https://f-droid.org/repository/browse/. You can also download other great apps there like music players, games, and everything else you might need. The Fdroid app allows you to maintain up to date version control and simple downloading and installation of these apps and is a lightweight alternative to the Google Play Store. that is certainly worth taking a look.
Hello, this ROM is also compatible with all versione / model of Note Edge?
T-Mobile, Can (W8), Sprint, Verizon, USC (R4) etc... ?
Thank you very much for the support!
pickandrew said:
Hello, this ROM is also compatible with all versione / model of Note Edge?
T-Mobile, Can (W8), Sprint, Verizon, USC (R4) etc... ?
Thank you very much for the support!
Click to expand...
Click to collapse
Good question. In a word, no. However, another user in the data zip thread (referenced in op) successfully used the data zip to flash an international ROM to his us cellular phone. You can read more about it there.
Wow hats off my man !
A very dedicated developer you are mate . And you just cooked us up one of my favourite roms !!
Thanks a lot Al
Ambient Display Issue
I love this rom, yet more great work from AKLU, but a big problem I have noticed with the rom is that Ambient Display stays on, even when disabled in settings. It drains battery pretty bad and causes my leg to press screen in pocket. Thanks for your hard work!
metalrules321 said:
Wow hats off my man !
A very dedicated developer you are mate . And you just cooked us up one of my favourite roms !!
Thanks a lot Al
Click to expand...
Click to collapse
Thanks for the kind words!
DaKillaz98 said:
I love this rom, yet more great work from AKLU, but a big problem I have noticed with the rom is that Ambient Display stays on, even when disabled in settings. It drains battery pretty bad and causes my leg to press screen in pocket. Thanks for your hard work!
Click to expand...
Click to collapse
Thanks for the kind words!
As for the ambient display, it is in the settings menu twice, once under "display" and once under "gestures" do you have both off? Does it still happen if both are off? Thanks!
Actually, I think I fixed it. The gestures and display menu settings copy each other, if I turn off in one, it turns off in other and vice versa. But I found that if you turn it off and on twice, the setting seems to stick and it turns off. If you only turn it off once from it being on after first boot, the setting doesn't stick until you cycle it one more time. The ROM runs amazing though, and isn't nearly as power hungry as TouchWiz; Qualcomm quick charge actually charges quick now! Another bug I have found however is that stuff like gyroscope seems to freeze up along with accelerometer. Google Cardboard for example immediately stops responding to the sensors. And there are times that the device will stop auto rotating, a fix to that is to open YouTube app on a video and it fixes. This is still a fast and amazing ROM though, I just wanted to let you know about these bugs too, so they can be looked at. I appreciate your work a lot. You and Mickey387 are pretty much the only people keeping this dev scene alive. If you need anything like logs or to test something, I would be glad to help!
DaKillaz98 said:
Actually, I think I fixed it. The gestures and display menu settings copy each other, if I turn off in one, it turns off in other and vice versa. But I found that if you turn it off and on twice, the setting seems to stick and it turns off. If you only turn it off once from it being on after first boot, the setting doesn't stick until you cycle it one more time. The ROM runs amazing though, and isn't nearly as power hungry as TouchWiz; Qualcomm quick charge actually charges quick now! Another bug I have found however is that stuff like gyroscope seems to freeze up along with accelerometer. Google Cardboard for example immediately stops responding to the sensors. And there are times that the device will stop auto rotating, a fix to that is to open YouTube app on a video and it fixes. This is still a fast and amazing ROM though, I just wanted to let you know about these bugs too, so they can be looked at. I appreciate your work a lot. You and Mickey387 are pretty much the only people keeping this dev scene alive. If you need anything like logs or to test something, I would be glad to help!
Click to expand...
Click to collapse
Thanks for the kind words! Yes, @Mickey387 is the man! I mostly just fine tune his really great work to use it on these other roms.
I am currently testing a new updated build of this rom, so that should be out soon. This is Slim 0.7, and I am testing Slim 0.13, so quite a few fixes, although not much more in the feature department, just keeping it slim. Interestingly, they did change the SlimLauncher to be more like the PixelLauncher, rather than the traditional TrebuchetLauncher style.
It also should fully support OMS, rather than legacy mode, but I am still testing that.
As for testing, yes, anytime that you have an error, please take a logcat, I will be able to help much better if I have logs to work with.... That being said, if you wait a few days for the new release, then test and log if the error persists, that would be great!
I use this great ROM till one week. I use it without the UKLA-kernel, with the hope to get better battery drain.
For me is one little problem. The inactivity display is a nice feature. But when I get a notification, the display is to dark for daily use. When I want to start the phone by active inactivity display, the display keeps dark. I have to press the power button twice to get full light. That's a long way.
Perhaps this is a normal nougut-feature?
---------- Post added at 07:25 AM ---------- Previous post was at 07:07 AM ----------
Part 2 - I have to change the train. [emoji3]
Because of my little problem above, I try to disable the inactivity display, but unfortunately the solution from DaKillaz98 doesn't work for me. [emoji17]
Well, I found out that the solution worked until I rebooted, now ambient display is stuck on. Knickelei, the ambient display staying dark is a bug with Android not restoring brightness values after the screen has been turned on. Another bug I found is that the camera display when taking a picture in Facebook Messenger is really warped and weird. I will provide logcats when I get them.
AlaskaLinuxUser said:
Thanks for the kind words! Yes, @Mickey387 is the man! I mostly just fine tune his really great work to use it on these other roms.
I am currently testing a new updated build of this rom, so that should be out soon. This is Slim 0.7, and I am testing Slim 0.13, so quite a few fixes, although not much more in the feature department, just keeping it slim. Interestingly, they did change the SlimLauncher to be more like the PixelLauncher, rather than the traditional TrebuchetLauncher style.
It also should fully support OMS, rather than legacy mode, but I am still testing that.
As for testing, yes, anytime that you have an error, please take a logcat, I will be able to help much better if I have logs to work with.... That being said, if you wait a few days for the new release, then test and log if the error persists, that would be great!
Click to expand...
Click to collapse
Currently having issues with 0.13, the sound quit working, so the upgrade/update is on hold while I investigate.
@AlaskaLinuxUser you said no, not all phones will work with this rom. but can you please point out what phones will work?
I have a N915F.
Thanx for the work !
benna said:
@AlaskaLinuxUser you said no, not all phones will work with this rom. but can you please point out what phones will work?
I have a N915F.
Thanx for the work !
Click to expand...
Click to collapse
This rom should work on your phone. As long as you are on the 6.0.1 modern and boot loader.
Also, you can use this rom:
https://forum.xda-developers.com/no...-nougat-built-sidebar-launcher-t3558296/page4
thanks for the port its working fine.
Does infrared working?
abbaselmas said:
thanks for the port its working fine.
Does infrared working?
Click to expand...
Click to collapse
Great question, I've never tried to use the infrared.... I'll have too find something to test it on.
AlaskaLinuxUser said:
Great question, I've never tried to use the infrared.... I'll have too find something to test it on.
Click to expand...
Click to collapse
Ok I have tested infrared and its not working.
Also I couldnt find a way to take a screen shot :/
abbaselmas said:
Ok I have tested infrared and its not working.
Also I couldnt find a way to take a screen shot :/
Click to expand...
Click to collapse
Thanks for the heads up! Also, press and hold down volume + power button to take a screen shot.
AlaskaLinuxUser said:
Thanks for the heads up! Also, press and hold down volume + power button to take a screen shot.
Click to expand...
Click to collapse
I thought that I almost try every combination :facepalm: thanks for the reply and SS combination :good:
will this work on N915V ?