Related
Hi all,
I've been a long-time Cyanogenmod user, and been very happy overall. However, as they expand to so many devices, and time their final updates together, I no longer benefit from quick access to new versions of Android since I've only got Nexus devices (for example: https://plus.google.com/+CyanogenMod/posts/HpXkXU98R7q)
Realistically, I only use a few CyanogenMod features that go beyond a stock Nexus ROM:
Root
Numerical Battery
Clock Widget
Bluetooth Tethering
Expanded Desktop (Might not be required with KitKat)
Pie Controls (With Expanded Desktop, might not be required with KitKat, either)
Given that, and KitKat's full screen capabilities, it brings me down to Root, numerical battery and BT tethering, which are pretty easy to enable on a stock ROM. However, every time I OTA update, I loose it all. And to get root back, many times I have to re-unlock which causes a hard-reset, loosing all my data, too.
So, the question: Is there a ROM that's close to stock, with root, that either has or would be easy to add the above features? Or, is there an easy way to create my own. I'm also looking for something that could be repeated across multiple Nexus devices (4/5/7/10).
Thanks,
Ben
Although I don't use it, so I'm no expert, I think the Xposed Framework would do the things you want.
Sent from my Nexus 4
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.
@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.
Very scarce info everywhere, but quite a few people already use this $80 super-powerful watch including me (which is basically a micro-smartphone).
Many video reviews already.
I personally think that such powerful watch (much more powerful than my cheap 2016 tablet on previous Mediatek chip with less RAM) is a such small smartphone with illusion like it’s watch made by very modified version of Circle launcher with edited Android 6. I don’t see any limitations on this watch to run full stock Android OS here from the M6737M series smartphones, if ported. Even now all full-featured apps from Google store made for smartphones are perfectly runs here, including very big navigation apps and even the full “battery saver” function present from smartphones (first one which I see on Android watch ever). The only limitation which I noticed is very small display (specific apps cannot fit) and badly edited Android OS (like completely deleted status bar from OS, any 3rd-party status bar apps are installing fine but crashing on settings). Most 3rd-party launchers from Google store and open sources are installing here (only with few exceptions) - the most stable one I’ve found is open source “Essential Launcher” ver. 1.3.
My feeling from “lift wrist turn on” function with “swipe pages” makes almost iPhone X experience here, no any buttons needed, very stable power on only by view and swiping windows (including closing them by swiping to the right) makes very good feedback to the user.
Everything spoiled only by edited OS - awful work with fonts, too many illogical Menu lists, deleted functions like not present “Storage” in OS settings(only shortcut to file explorer) - the USB storage media not adding because of edits on OS level, considering normal micro-USB & even if you turn on “usb media” in developer settings.
Very few watch-faces with no way to install any others, it’s obviously fake feature to make you feel and use them as watch.
So, what I think many would be glad to see here - the root is the most important goal for now(developer menu allows bootloader unlock-not sure if it’s true because USB media settings there not works), maybe putting the normal Android is the next goal.
The root is very needed to firewall for very shady apps here, it’s very powerful device so it have full smartphone spyware, like notorious MTK Logger & Thermal Manager, which can work at sleep mode (it is almost suspicious that they broke USB media function so user can’t bypass network connection for installs). Root needed to work with display resolution and etc.
Edit: the processor by Aida app recognized as MT6737M but on Aliexpress you can find watch easily by search term processor "MTK6737M" (only like 7 sellers total).
I have the H5 as well, and you're correct! The main draw back is the stripped down OS, for example the call forwarding features are missing..
Ordered one of these a few weeks ago, should be getting delivery soon. Interesting to see how it performs, my last android watches have been mt6572 & mt6580, both of these I ported full Android versions to, I may give it a go at porting a full Android version to this in the future
Check this also:
https://forum.xda-developers.com/sm...dorid-6-0-finow-q1-pro-smartwatch-4g-t3745271
Well I got mine today, seems good so far. As for alternative launchers tried a few that work OK, if you want to change the clockskins for now I have found that Universal Launcher New Gen works just fine (you add clockskin folder +clockskins)
https://play.google.com/store/apps/details?id=com.ricktop.ClockSkinCoco
I use mine at least 2 weeks maybe. Without root (which I plan to do but don't have time right now) I do not connect them to any Internet, so I'm using them as just watch (it's my first smartwatch). Files I'm sending through bluetooth from my Android phone, quite neat that you can install apps from bluetooth menu right away.
About battery - very good, if you don't connect them to networks at all, with battery Saver on & "wrist move activation" off they can work whole week on 1 charge (this includes some extensive using in 2 days on winter street with GPS apps, camera-video, constant time checking and etc.). They CAN HOLD MORE days, after the full charge, watch calculated the battery to the 15 days of work - which is believable, as I see now if you will check only time manually they can easily save 1 charge to 12-13 days. I use charger with them only once at week, it's quite shocking to read Apple Watch forums where people making that every 2-3 days.
They're quite powerful - making the zip archive internally from 250Mb photos/videos takes something like 2 minutes.
Because the step-counter here work always (even if you take them to the other room) - this device is just made for the SmartNavi (open source navigation app which use mainly step-counter with rare or no GPS connection for battery saving).
Can't wait for a custom recovery to be made for it, so I can root it. Tried all the rooting apps out on the web and none work so far.
Well I have managed to get Root access, using Magisk, and flashing patched boot image, struggling to create a TWRP recovery. Hoping someone out there can come up with a custom recovery.
Managed to port TWRP to it, but it is in miniature! going to have a play around with it to see if I can make it usable. Anyone with suggestions be grateful - well gave up on trying to amend TWRP resolution, and installed flashify - just flashed an AOSP ROM to the H5, happy days!
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Wizard2004 said:
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Click to expand...
Click to collapse
I will put something together at the weekend, by then I should have something usable, don't want people breaking their new toys!
stevea76 said:
I will put something together at the weekend, by then I should have something usable, don't want people breaking their new toys!
Click to expand...
Click to collapse
It would be interesting to find if there's any "recovery mode" on stock ROM image at all, considering that there's only 1 button. On similar watches from Samsung and etc they have quite awkward way to enter recovery - like some swipe to the left in time of logo showing and etc. I tried to repeat any swiping during boot - nothing...
Also, by the usual use of watch (almost a month now) I can say that in my case of use the battery holding 1 full charge for 7 days, so a week, the same amount calculated by OS also. That's the battery regime or mode which is now constant in my case (it can be different in situation of other people).
The battery here can be saved even more for a week - I managed to notice that "sleep stat" function are working here at all times and cannot be turned off like step counter in this Android OS, at the night time it randomly turning on the pulse checker light even if you not wearing them, which using the battery (not a big deal, but using some).
Wizard2004 said:
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Click to expand...
Click to collapse
Here is the link to the AOSP ROM I ported to the H5.
I must express it is a long winded way to flash it as I am not technically minded, just playing at it, and only do this if you have the stock ROM downloaded as a backup to revert back to and don't mind the possibility of wrecking your toy!, the only reason for me doing it this way is that the recovery TWRP I ported is functional, but not set for the screen size for the H5 so unless you have bionic eyes it is nearly impossible to use, hence the reason for my 'workaround' (note: If anyone can make the TWRP scaled for the watch, just flash the ROM in the usual way)
Here is a 'sort of' guide and link to files.
https://www.androidfilehost.com/?w=files&flid=252561
1. Flash
Microwear_Magisk_Patched_Boot_IMG using splash tool, reboot device.
2. Install Magisk Manager from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page4
Open Magisk manager and go to settings, set default action to 'Grant'
You now have root.
3. Flash
Microwear_H5_Recovery_TWRP using spflashtool.
4. Install
Flashify (for root users) from the Playstore.
5. Download directly to the watch (or to Computer and transfer to the watch) Microwear_H5_AOSP ROM AND the GAPPS of your choice (Open Gapps arm64 nano was my choice)
6. Use Flashify to install zip(s) making sure you click TWRP as recovery option and also tick the wipe cache, data etc (add the Gapps as well if you want Google)
Click Reboot on flashify.
Hopefully the watch boots to recovery and installs the ROM and gapps!
First boot sticks on boot animation, so if not starting after 3 or 4 minutes power off the watch and reboot, after another 5 to 10 minutes you should see 'android is starting'
Nav Bar is by default on permanently, to make this and notification bar 'hide' (fully Immersive) I used this method.
1. install on pc ADB (Guide below)
2. Enable developer options and USB debugging on watch.
3. connect watch (switched on)
4. Open ADB on pc.
5. Type: adb devices (click enter)
(should see you device is connected)
6. Then type: adb shell - (click enter)
7. Then type this line:
settings put global policy_control immersive.full=*
Now the navigation bar will pop up when you pull down or up slightly on the screen and will auto hide after a couple of seconds.
As for sensors I don't think any are working.
I have included 3 launchers on this ROM, so make your choice!
Please, please, please DO NOT ATTEMPT THIS if you don't know how to revert back to stock rom. I bear no responsibility for broken toys!
Guys, who already have a scatter file for this watch, i really want to make a backup of current ROM before checking for any new updates (which is quite good version from January and there's nowhere on Internet any firmware files for this watch, so saving and sharing ROM is important). If i manage to download ROM i will post it on Google drive.
I wanted to force watch go into it's own recovery but my ADB installation don't see this watch connected - there's a primitive subsystem on watch beside Android OS, it can be seen when you turn Android OS "power off" and connect USB for charging - it will show the battery, i'm puzzled how to enter into any settings of that subsystem.
The stock firmware is on the Microwear Website.
http://m.microweartech.com/en/MicrowearFirmware.html
stevea76 said:
The stock firmware is on the Microwear Website.
http://m.microweartech.com/en/MicrowearFirmware.html
Click to expand...
Click to collapse
Yeah, i noticed only now, strangely but i remember that a month ago there was nothing about H5 model on their site when i searched…maybe because they just released it.
Also the firmware have the same scatter file - the first one which i found myself for some cheap smartphone on 6737 chip, as i remember i found it on reddit.
As i seen no updates of firmware for now.
crustier said:
Yeah, i noticed only now, strangely but i remember that a month ago there was nothing about H5 model on their site when i searched…maybe because they just released it.
Also the firmware have the same scatter file - the first one which i found myself for some cheap smartphone on 6737 chip, as i remember i found it on reddit.
As i seen no updates of firmware for now.
Click to expand...
Click to collapse
No updates as yet. I have ported an AOSP version, pretty much stock Android to the H5, it is basic, but I like the 'stock experience' on a square watch. Not got the sensors set up, but not really bothered about how many steps I have done on any given day or my heart rate for that matter.
Also if you want fancy clockskins then Eric's launcher works just fine on it.
stevea76 said:
No updates as yet. I have ported an AOSP version, pretty much stock Android to the H5, it is basic, but I like the 'stock experience' on a square watch. Not got the sensors set up, but not really bothered about how many steps I have done on any given day or my heart rate for that matter.
Also if you want fancy clockskins then Eric's launcher works just fine on it.
Click to expand...
Click to collapse
As i understand correctly - here they simulated or just copied clock skins from Apple watch?
Where to find Eric launcher?
For everyone else i will write again link to the firmware from Microwear site here – https://drive.google.com/drive/folders/1WaktAl-cjCTE1l0jffA7BnevzESdlCwc?usp=sharing
because chinese support is very short in time and can vanish with website very easily (for example to find an older firmwares to my Onyx Boox ereader i used "webarchive" service, thanks gods we have it - only from this saved archived copies of pages i found the sharing links to the older firmwares, still i cannot find the first version of RemixOS release for KitKat-if anyone have the alpha - please message me)
Eric's launcher is here:
https://play.google.com/store/apps/details?id=com.ricktop.ClockSkinCoco
All about the clockskins mainly for round Full Android watches here:
https://plus.google.com/communities/109827242607524552712
For square Full Android Watches here:
https://plus.google.com/communities/118413074291213420811
A useful forum for Full Android watches (round) with guides how to install custom watch faces:
http://roundandroidwatches.proboards.com
Hey guys,
up till today I'm still using a Samsung Galaxy Note 3 with Android 4.3.
It is modded to the max to exactly meet my needs and "paranoia":
- Custom Rom TouchWiz based rom
- Custom Kernel with some special script based tweaks (for example: MAC randomization everytime I turn Wifi on - handy for time limited free access points and to prevent beeing tracked etc.)
- Full Disk Encryption with a password different than my unlock pin (so when the device is off it requires a long password, but when on only a shorter pin)
- Xposed with the "old" Xprivacy Pro, Greenify and lots of other useful modules (like device shutdown after x failed amounts of unlock password etc)
- Lightning Launcher (allows "pinned" widgets that do not scroll - like the clock always beeing shown on top of all my homescreens) and custom widgets made with UCCW
- Button mods (double tap menu button turns on/off auto rotation, long menu switches last two apps, long back kills foreground app etc.) and homebutton mod to turn on flashlight when held while device is locked (to turn it on blindly / without looking)
- Sidebar Launcher Appsi for all my apps (and using xprivacy to prevent certain apps from showing up in the list at all)
... etc etc.
It took me a long time to set up everything and whenever I bought a new phone I sold it soon after because they never could be modded that hard like my old note 3 could be. (not to mention the built in batteries - I HATE that so much about all new devices).
Long story short: The Mi A1 could maaaaybe finally be the device to replace my Note 3 - but for that I need to be able to really mod it hard again hehe.
What really is important to me is beeing able to use xposed and xprivacy (unfortunately the xprivacy lua is not that good as the old one as far as it reads in the description), controlling the device encryption with my own 20+ Character Passphrase while still having a shorter pin when the device is booted up (and it beeing "full device encryption" not just file based if that still exists?). Removing all google apps except the playstore (and the account manager - dont even want the google play services crap) and preferably beeing able to install modded playstore which does not autoupdate itself etc.
-----
Do you guys think this is possible at all? And if so - should I stay with a 7.1.2 based rom or go for oreo? I mainly care about modability as I explained..
Hope someone is in the same boat or at least knows enough about this phone and the roms/kernels/availabe and working xposed mods to help me out.
There's pretty much no development for Nougat so it would be better if you were to get on oreo
Modabillity is pretty great with this phone so far
Look around on xda and see if you like it
berezker said:
There's pretty much no development for Nougat so it would be better if you were to get on oreo
Modabillity is pretty great with this phone so far
Look around on xda and see if you like it
Click to expand...
Click to collapse
but does xposed and stuff like modded playstore etc exist/work for oreo? and do you maybe know if its possible to have a different boot password than just the unlock pin when device is powered on?
and how about rootcloak and stuff like that? On my old note i can pretty much fake everything to apps and prevent root to be detected or feed them with fake data through xprivacy - but does this all still work to the same extend on the newer android versions? This safetynet bull**** has been around since when again? Can that still be fooled?
zroice said:
but does xposed and stuff like modded playstore etc exist/work for oreo? and do you maybe know if its possible to have a different boot password than just the unlock pin when device is powered on?
and how about rootcloak and stuff like that? On my old note i can pretty much fake everything to apps and prevent root to be detected or feed them with fake data through xprivacy - but does this all still work to the same extend on the newer android versions? This safetynet bull**** has been around since when again? Can that still be fooled?
Click to expand...
Click to collapse
I'm not really sure about modded play store and boot password stuff but what I do know is that you can use Magisk (Similar to SuperSu + Extra useful mods) to hide root from certain apps that you choose
Xposed does work perfectly fine but it depends on the modules and whether they work on oreo. If not, magisk modules are also pretty good
If you happen to own a phone that you can flash Oreo on, (see, Lineage 15), then you can pretty much know and discover everything about Oreo and how modding works on it
I recently had a crash using Android Q Beta 4, Magisk and Elemental 4.01
Since the crash the phone acts somehow weird. After checking on developer options I noticed that it says "developer options are not available for this user" so it seems like its a privilege issue. I can't switch to another user, it is set to 'owner'.
Many other things won't work either. There are no notifications anymore, the quicksettings are not extendable or mobile data is set off even though it's connected. Recent apps doesn't work either. Is this a known, possible result after a crash? I can't find anything about this but it feels like it could be easy to fix.
//Edit: Found the solution to simply run the setup wizard once again. Everything is fixed after this.
philsner said:
I recently had a crash using Android Q Beta 4, Magisk and Elemental 4.01
Since the crash the phone acts somehow weird. After checking on developer options I noticed that it says "developer options are not available for this user" so it seems like its a privilege issue. I can't switch to another user, it is set to 'owner'.
Many other things won't work either. There are no notifications anymore, the quicksettings are not extendable or mobile data is set off even though it's connected. Recent apps doesn't work either. Is this a known, possible result after a crash? I can't find anything about this but it feels like it could be easy to fix.
//Edit: Found the solution to simply run the setup wizard once again. Everything is fixed after this.
Click to expand...
Click to collapse
Q beta4 is worse that beta 3 from my usage.