Hi,
1) Smart lock is being removed from the smart lock menu in settings. I've seen people note that removing smart lock from trusted agents, and adding it back fixes it. This works, but only temporarily.
2) Does anyone know the stock kernel? I was previously running a beta build, and curious to know if kernel is correct.
Android version
8.1.0
Baseband version
2.0.c4-M2.0.0
Kernel Version
4.4.120-perf+(gcc version 4.9 x 20150123 (prerelease) (GCC) )
[email protected] #1
Sun Mar 4 15:14:06 PST 2018
Build number
OPM1.180104.092
{
"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"
}
You are using the stock kernel. I know that some people have experienced the smart lock option disappearing from settings but that hasn't happened to me. You probably just need to factory reset your phone. Since it sounds like you have corrupted data restoring your phone from a Google cloud backup after a factory reset is a bad idea. The cloud backup can also restore your corrupt system data. You should choose the start fresh option and set up everything from scratch .
Related
I flashed a custom ROM on a c-spire Samsung Galaxy S4 SCH-R970X
The parameters look like this
Android Version - 4.4.2
Baseband Version - Unknown
Kernel Version
3.4.0-aokp-g13b9152
[email protected] #1
Thu Jan 9 08:27:31 CET 2014
AOKP version
aokp_jfltecsp_kitkat_nightly_2014-01-09
Build Date
Thu Jan 9 08:13:39 CET 2014
Build Number
aokp_jfltecsp-userdebug 4.4.2 KOT49H
eng.sethyx.20140109.081306 test-keys
SELinux Status
Enforcing
I want to remove the aokp kitkat rom but I dont know how. each time I try to flash the original rom using ODIN I always end up with a failure bootloop and I would then have to re-flash the recovery. I discovered some thing in the settings menu and I'm wondering whether or not it is the reason for my not being able to restore the original rom
{
"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"
}
mrsalvatore said:
I flashed a custom ROM on a c-spire Samsung Galaxy note 3
The parameters look like this
Android Version - 4.4.2
Baseband Version - Unknown
Kernel 3.4.395248627
Click to expand...
Click to collapse
PLEASE DELETE,
the best way is to root 14.4.B.0.37 install recovery but don't deodex then apply this update(14.4.B.0.56) via ota then deodex and do your thing. few things changed in /system
Use flashtool and flash via flashmode
Original 4.4.4 build number but notice the kernel date
Note: Root is kept, System Still Writable Etc Etc Etc
+ I've noticed instant screen wakeup and faster camera initialization
- after a day of use the camera isnt as fast but it hasnt lagged to the point where it freezes at a black screen
- upon further investigation, libs and firmware has been replaced also i believe , try to work things in, might just flash the whole system partition from recovery, should still have root at least i believe
#Edit
after reading around it looks like this is the 14.4.A.0.157 update but for the Z1S, they report the same fixes, still need to find out if system was changed
{
"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"
}
can anyone else confirm and anyone know if system files or framework was changed?
iffy about just changing the build number, doesn't feel clean xD
Hey guys
My Screenwrite from AirCommand doesn't work and won't even start.
After I select Screenwrite from the AirCommand nothing happens, AirCommand just goes away like it would normally do. My phone is not taking a screenshot to edit it afterwards. It works again after Rebooting and I'm not able to find the cause of the problem.
All the other AirCommand Functions like ActionMemo, Smart Select, Image Clip and Pen Window work perfectly fine.
The screenshot function with Home-Button + Power-Button works though.
I've frozen Music 1.0, S Finder and S Voice with Titanium Backup, but it still doesn't work after enabling them (Screenwrite works fine after reboot with these Apps frozen).
I already tried to search for solutions here and on the internet, but could only find few with the same problem without any solutions.
Running:
Note 3 SM-N9005
ROM: Echoe Rom v.23
Android Version 5.0
ROM Kernel: Linux 3.4.0
I'll attach a picture for you guys to make sure you'll know what I'm talking about
{
"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"
}
***EDIT: Ok, found the culprit. If you don't explicitly tell the Screenwrite app to discard the changes (for example pressing home button or so) it will stay in the background and won't recapture a screenshot for you. Didn't manage to kill the background process as of yet. But with this knowledge it's fine.
I came here to share with you this mod which, I believe, many seek.
I think it was created by the developer of this forum (http://goo.gl/n4kNIj). If possible, run there and thank.
Tested with Pure White Stock 5.1, all went well. I had problems with the mods of the Cataclysm 5.1 Stable.
If possible some good soul solve the problem with the Cataclysm, I appreciate a lot.
Flash with latest TWRP.
Use at your own risk, I am not taking any responsibility for their losses.
(Translated with Bing)
{
"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"
}
Remove
It worked...
But the text is a bit too large
So how I do I undo it ?
Try the attached patch.
Have you tested on which Rom? Knows how to solve the problem with the Cataclysm?
Will it work with Cata?
Cause problems in Cataclysm. Have not tried restoring with the patch, I performed a clean installation.
I'm hoping someone with a lot of goodwill can solve the problems with the Cataclysm.
Ur just sharing this, didn't actually make it right? If you actually made this mode, would you mind making another one for the latest Cataclysm April 14 build? Thanks in advance!
Does it work with Boostpop rom?
Hello everyone,
since this awesome Tablet isn't getting Updates anymore I tried to build my own Android Version (10) with help of the AOSP Documentary.
Everything works smooth and fine, but when I try to flash this freshly created build, I get an error:
"Device product is 'baytrail'.
Update requires 'goldfish_arm64'."
{
"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"
}
I tried resolving the problem by getting to know what exactly is goldfish in the first place. So I found, that the 'goldfish' is in the Android Kernel for 4.x versions. I simply just don't understand why the bootloader is attatched to a specific android version. Strange.
Additionally, Lenovo Support gives the whole Open Source .zip for both Lollipop and Kitkat versions, so I have full build .zips of the "old" versions.
Is maybe the boot.img file the problem? I extracted it from Lollipop.
Any help will be appreciated.
Same issue.
I think you need to edit the upadte-script.
Hello. Could you please share your previous build that worked? Will it work on the Tab 2 - 8 inches?