If you long press the widget, you should be able to drag its borders and make it larger![]()
I tried this and it didn't work. But a cache wipe from TWRP did the job for me. Thanks!
If you long press the widget, you should be able to drag its borders and make it larger![]()
Which TWRP did you had while running [ayke:20170226]? It seems to be important to have the latest TWRP from Ayke, as otherwise the sudo fails.
Although I don't see any connection to the SIM-card.
Although my sim-card is recognised, I do have trouble with reliability of network (O2). Forced it to Edge now. Not sure whether it tries to check for HSDPA if Edge is not good enough and vice versa.
But even this "forced to Edge"-signal seems to vary a lot, even while phone is just laying on the desk. This seems strange to me.
What can be the reason:
- bad hardware
- bad connector
- bad SIM-card (I cutted once the SIM-card, but as this is just digital I would expect either a go or nogo)
- problems in software
...This morning I downloaded the rom of [zytrix78:20170505], made a TWRP backup as a precaution, did a dirty flash and observed the boot process very excited! SUCCESSFUL!
Device is running smoothly, no extreme battery drain! No bigger problems found till now! BIG THANKS to all developers!
guys, i installed latest hennys version and i cant grant root access. any help?
guys, i installed latest hennys version and i cant grant root access. any help?
You have to flash the addon-su-arm.zip ( Should be on the OP, other wise found on lineage site in 5 mins).
guys, sorry but i need a guide how to find twrp 3.1 and how to install itFlash with the last TWRP --> 3.1 and grant root in the dev options.
guys, sorry but i need a guide how to find twrp 3.1 and how to install it
is 3.1 needed for last version of hennys?
the last one? the 2017-03-24? ok did it thanksssHere you'll find it. Take the last one.
https://aykevl.nl/android
I have compass problems for some month. It allways pointed to south east and did not move when the phone was turned.
Calibration with different apps did not help.
Today i just came back from jogging where i used my phone for tracking with gps.
When i arrived at home i sat down and played around with the phone and opend the compass app.
And it works!!
I am a littele afraid to restart it
I have no idea what's the problem. But for now.
Regards
Sascha
My compass needle is turning. But it doesn't show to north.
Even worse: If I rotate the phone, needle follows this movement, but slower than I turn the phone. So I can adjust it to any direction I want. Crazy!
I use SatStat to show me details, and it marks magnetic field sensor to be unreliable. (2nd tab, green reliable, violett not reliable).
Can you check this please ?
I have a Problem, my phone cant detect my SIM-Card.
...
Problem solved. I had an old version of TWRP installed.
Before calibration the sensor was unreliable too (violett).
It seems that the compass can only be calibrated with gps on and it takes some time.
I was walking in in the garden with gps on, moving the phone from time to time (the "8" you know).
After some minutes (5 to 10) the compass started to work and then the color of the reliability changed to orange in SatStat.
After a restart the calibration is lost again. I was able to reproduce this 3 times.
Later i rebootet the phone to "uncalibrate" the sensor.
Then i activated gps, started mapfactor navigator to keep the screen on and the gps connection online and placed the phone for 10 minutes at the window.
When i came back i made the calibration move ("the 8") and the compass worked. So it seems to be question of time with activated gps.
Is the snapchat problem already solved?
I tried several methods to cloak the root access for snapchat, but they did not work, can u pls fix the problem?
Before you start:Disclaimer:
- You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
- Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
- Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
- The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
- It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
- Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
- Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Changelog:
19/08/2017:
* SELinux policy update
* Update to newest LineageOS sources
02/06/2017:
* Firefox crash&reboot fixed (thanks to Spookcity)
* Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
* Ambient display option added (disabled by default)
28/05/2017:
* [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
* Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
* Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
* Updated kernel to 3.4.107
* Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
* Updated LineageOS sources
* FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
* Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
* Replaced the buggy Snap camera with the LineageOS default camera app
* Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
20/02/2017:
* Fixed Youtube scaling issue on window resizing
* Compass fixed (thanks to mirhciulica for figuring out what's wrong)
* cpufreq config added
* Charge mode fixed (starts when plugging USB into a powered-off phone)
* USB-Tethering and Wifi SoftAP (Hotspot) fixed
* Camera doesn't crash when switching between camera and video (but might still crash sometimes)
* Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
01/02/2017:
* conversion to LineageOS
* updated some libs with stock MM versions
* fixed robotic voice problem
* fixed silence on first call
07/11/2016:
* Initial test build
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
* Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
* Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
* Updated kernel to 3.4.107
* Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
* Updated LineageOS sources
* FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
* Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
* Replaced the buggy Snap camera with the LineageOS default camera app
* Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)