yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] goducks3620:
I was running Resurrection Remix but was having problems with stability every few weeks prompting me to keep doing reinstalls. I've moved to LineageOS, flashed with Opengapps stock and Nougat-level emoji. Running the 1/2 build right now and having no problems. I'm also on Sprint.
[Moto X Q&A] chimpknowskungfu:
GPS and Google maps working for you?
[Moto X Q&A] goducks3620:
yes, just fine.
[Moto X Q&A] hbenz2008:
Aicp

Wireless
[Upgrading, Modifying and Unlocking] reist:
Hello all,

i have read a lot about rooting the Lenny phone.

THere is just 1 problem.

I havent found anything about rooting the Lenny 3.

Well... i found some things like kinoroot ant those programms, found some youtube movies wich i dont trust one bit...

Could anyone tell me what is the best way to root this phone?

Tested and all?

I like the phone but i need ROOT :)

Thanks in advance!
[Upgrading, Modifying and Unlocking] reist:
Anyone?
[Upgrading, Modifying and Unlocking] mdurrer:
Hi friend,

I'm in the same ditch as you are.

I don't trust those videos one bit.

I really love those Wiko Lenny 3 phones. They are cheap (40 dollars) and are really something nice. But I don't want to brick my phone just yet.

Is there a safe way to root these phones?

I'm actually surprised this hasn't come any further. The phone is pretty awesome for the price but the SIM lock is annoying as hell. Speaking about it, it actually has 2 SIM card slots which is pretty awesome.

I bought some nice games so far for my account and I love to use the device. But I wish I could root it and use the full potential of this device :(

Has anybody rooted this device successfully?

It's being sold in Switzerland in the post stores for CHF 40 / about 40 dollars with 2 years of SIM lock to Swisscom.

It's a great deal, but I wish I could **** up the SIM lock.

Any success stories and manuals would be highly appreciated!

Regards,

Pix
[Upgrading, Modifying and Unlocking] yudaniel:
https://www.getdroidtips.com/twrp-recovery-wiko-lenny-3/
[Upgrading, Modifying and Unlocking] Meaviell:
https://xdaforums.com/android/general/wiko-lenny-3-twrp-root-t3630629/post72879407#post72879407
[Nexus 5 Q&A, Help & Troubleshooting] ashirviskas:
I want to give my unused nexus 5 for a friend, but it's been almost a year since I visited these forums. I want to give him nougat if possible, but are those ROMs stable? Basically I need a stable ROM with good battery life and that's it. What would you recommend?
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
I recommend flashing the phone with the latest stock MM so it will receive security updates.

Stock will be the most stable.
[Nexus 5 Q&A, Help & Troubleshooting] ashirviskas:
Thanks. But he doesn't really need security updates. And when I was using it, I'm sure XtraStock and XtraSmooth were really stable, no reboots and no bad stuff happenning. Also, multi window support would be cool, so what is the most stable Nougat ROM?
[Nexus 5 Q&A, Help & Troubleshooting] parag60288:
Try PureWhite6.0.1 Rom, it is very stable as it is based on stock rom.

I am using it since long time.
[Nexus 5 Q&A, Help & Troubleshooting] username8611:
It's a Nexus, they're all stable. Some have some bugs, but I cannot consider any of these ROMs unstable, like so many of them were on my Galaxy S back in 2011. Me personally, I use Nitrogen 7.1.1, and not only is it stable, I can't even find any bugs in it.
[Nexus 5 Q&A, Help & Troubleshooting] aciupapa:
AOSP 7.1.1 by [MENTION=5480061]Santhosh M[/MENTION] is great. Also The Fakenexus 7.1.1 is going yo get update soon i think. it was my favourite rom, but i lacked updates for last month. Right [MENTION=6117313]ganachoco[/MENTION] ?
[Nexus 5 Q&A, Help & Troubleshooting] fly23:
Sure? I thought the N5 won't receive any security updates any more.
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
The n5 won't get nougat but I thought it would receive security patches for a little while longer.

Edit: Looks like the n5 was supposed to stop getting updates three years from the date of introduction or 18 months from when it stopped being sold. Maybe the security updates have stopped?
[Nexus 5 Q&A, Help & Troubleshooting] fly23:
They have.

I am also searching for a ROM for my N5. I dont want to flash again and again. Lets say I want to choose between AOSP 7.1.1 by [MENTION=1326125]santhoshm[/MENTION] and the LineageOS Rom. What are the differences? For Updates: I think the LinageOS will have an integrated Update Feature. And in the Rom by SanthoshM I will have to flash manually in TWRP each Update? And besides that, one is completely the Stock Rom and CM hat some extra features but looks ans feels nearly the same as stock. ...?
[Nexus 5 Q&A, Help & Troubleshooting] ashirviskas:
Thank you guys!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jplum22:
There doesn't seem to be much documentation on whether Xposed even works with Tate (but I imagine it would work fine.) The only threads about Xposed and KFHD that I can find have to do with the 2015 version.

Does Xposed work on TATE? Thanks.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] squ89r97:
I have a Tate, I've previously had xposed working but I don't think it's worth it.

I also don't think xposed works at all on 7.0 based roms yet.
[Other SmartWatches] Neuer_User:
Guys, I did a short analysis on the apps in firmwares 1.2.3 and 1.3.0n. The results were pretty surprising:

The Chinese one is more advanced adn much newer (as was already known)

The Watchfaces app contains the SAME drawings in both versions (except the English one having less watchfaces). That means: The Chinese version does have e.g. English weekdays available (stored at the same locations) as the English version has. It probably was just disabled in the code to use the right coding!

One gets the clear indication that they worked on a joint firmware and then at some 70% got the strategic directions to split the firmware.

I am currently doing some tests to modify the apps and load them on the Chinese version. Maybe a Chinese version with English translation is better than the official English version. :rolleyes:
[Other SmartWatches] sakilxda:
Yes, in this moment i think that the china version with hack is better that English version
[Other SmartWatches] shayne77:
Wonder if it's worth flashing Chinese ROM to English version and then changing to English?

or, would you expect English version will catch up soon?

I'm disappointed so far with this watch (or rather the very very simple support from the APP on your phone)

You can't even look at the step or sleep data on your phone?!?!?

Nothing wrong with the hardware but it seems they rushed out this awesome device not really thinking about the supplementary app to go with it.
[Other SmartWatches] Pi3rluigi:
To sync sleep and steps on phone, you need Chinese Amazfit and MiFit apps, login with same Xiaomi account

Inviato dal mio D6633 utilizzando Tapatalk
[Other SmartWatches] shayne77:
I saw that tutorial on YouTube but I couldn't get MiFit to show data (it seemed to read it, sync ok but not display anything?)
[Other SmartWatches] Neuer_User:
UPDATE:

I can grant the app the WRITE_SECURE_SETTINGS permission, and then it indeed works (command "pm grant <package name> android.permission.WRITE_SECURE_SETTINGS"). The question is now, why do I need to grant that manually, when this is in already in the AndroidManifest.xml???
[Other SmartWatches] sakilxda:
Is possible change millas to km??? Thanks for you work
[Other SmartWatches] Neuer_User:
With this approach, yes. I need to get this running first, though...
[Other SmartWatches] sakilxda:
Perfect, many people hope this
[Other SmartWatches] sakilxda:
And do you think is possible put the original Chinesse firmware?

Change the English to Chinese after of Chinese to english

Return to previus version again
[Other SmartWatches] Neuer_User:
I am currently working on a "non-intrusive" custom-rom. That is using the Chinese version on the watch, booting with a special (temporary) boot image and running translated (and modded, if needed) apps. So, a simple reboot, and you would have back the original Chinese version.

I think I can get this running. I exchanged one app with this method, so It could be done with all apps. But I am still having some problems to solve first. And I don't have much time (actually, currently, nearly no time at all :( ).
[Other SmartWatches] dehallusinate:
Really appreciate your work for our watch, I'm willing to help in translating this watch into some language, but I'm not a developer, and it would be nice if we can enable language setting in option for our future custom rom, so we can choose the language we want.

big thanks Neuer!
[Other SmartWatches] Neuer_User:
So, I now got the the cause of the problem:

W/PackageManager( 432): System package com.huami.watch.sport signature changed; retaining data.
W/PackageManager( 432): Package com.huami.watch.sport desires unavailable shared library com.google.android.wearable; ignoring!
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)

So, that is why the application is force closing, ok. Now the question is, how to solve this. I would like to have an experienced ROM developer help me here. :confused:
[Other SmartWatches] Neuer_User:
OK, if someone is interested: I now understand why the permissions are not granted. It is the signature of the apk (which I needed to resign). For some permissions this signature must be identical with the signature of the platform. This key only Huami has.

So, what can be done? I am currently thinking of patching the PackageManager, so that it will not deny the permission. Not sure, if this is possible, but I will try.
[Other SmartWatches] Pi3rluigi:
I can't help you to develop, I have no knowledge, but I can be a tester when ready!

Inviato dal mio D6633 utilizzando Tapatalk
[Other SmartWatches] Neuer_User:
Thanks for the offer. Main work currently is getting the knowledge on howto deodex files, mod them, re-odex them. Then I can try to exchange the Package Manager on my watch. All of this is only temporary, so even if nothing will work afterwards, a simple reboot will fix it. :)
[Other SmartWatches] Neuer_User:
Some more info, on how my planned "non-intrusive" changes will work:

- The watch will need to be booted via a fastboot command. That loads a customized boot image. The boot image will mount all filesystems and then start the processes.

- However, after all filesystems have been mounted, it will mount the custom rom over the system partition. So, instead of using the system image, the watch will use the custom ROM.

- The custom ROM will reside as one single file on the /sdcard. So there are no modifications to the system partition (and neither to the boot partition).

- After a reboot, the normal boot image is booted again, which will also not mount the custom ROM.

- If you reboot via fastboot, the modded boot.img can be booted, which will mount the custom ROM again.

The nice thing with this is, that all modifications are temporary. If something is borked up, the device cannot boot or goes into a boot loop, it doesn't matter. You simply turn the watch off and on again, and everything is back to unmodified.

So far, this seems to be working. I now need to get a working custom ROM. That is, I need to understand how to modify the apps, so deodexing, decompiling, recompiling, signing, etc.

I will probably open an open source GitHub project, as soon as I have something usable. Then people can contribute translating and modding.
[Other SmartWatches] silver-alx:
Hi!

I've just translated chinese fw to russian and switched watch to kilometers everywhere and resolve some interface bugs. )) It was easy and i can give some advices if you need.
[Other SmartWatches] lordzahl:
If you could describe, how you did it, that would be very helpful. Maybe even upload your original and modified firmware, so we can take a look at the differences?

Thanks!
[Other SmartWatches] Neuer_User:
Hey, that is great. So, you are much further than I am currently. What fw are you using as a basis? The Chinese or the English version? Care to share your work?

My main goal is maintaining a custom rom, mainly with localizations, but also with small mods (such as km). As I stated above, I would (personally) prefer to boot this rom "non-intrusive", as I described.

Can we exchange our work or put it together?
[Other SmartWatches] Neuer_User:
To be honest, I have a pretty clear understanding, on how to do it. I already modified the Sports up to show some different text. But there are side effects (apk signing, frameworks etc), which I need to get used to.
[Other SmartWatches] silver-alx:
As I wrote - I use chinese fw. Took a base from my watch, deodexed whole ROM, decompiled some APKs, edited resources and smali-s, compiled and put it to device SD-card. After all I test it individually in a safe way. I stop android while staying in the adb shell, change one APK, start back android and whatch for errors and compiling process. If it is unsuccessful i revert APK back.

I can share my findings in any way. To resolve permission error you have to put wearsports.apk to the priv-app folder.
[Other SmartWatches] Neuer_User:
Thanks. A couple of questions:

- you say moving the app to the priv-app folder is enough to overcome the permission problem (ProtectionLevel = 2; different signature on the app)? Or did you recompile (and resign) did you also some framework.apk?

- How do you plan for future updates? Any OTA will probably fail, if you change one app on the system.

I plan to keep the Chinese version unchanged, and mount the modified ROM on top of the original fw. I also like to have some automated tools that can take a new fw , apply any of the changes we want to have and recompile it. So, actually, I am considering:

completely deodexing the ROM

adding the language res files and any other changes

recompiling the apps

preparing the ROM image

loading the rom image to sdcard and boot it over the system.img.
[Other SmartWatches] silver-alx:
Thanks. A couple of questions:

- you say moving the app to the priv-app folder is enough to overcome the permission problem (ProtectionLevel = 2; different signature on the app)? Or did you recompile (and resign) did you also some framework.apk?

== year, it's enough to place app to priv-app. I didn't touch framework jars and framework-res.apk, just recompile wearsports.apk and resign it.

- How do you plan for future updates? Any OTA will probably fail, if you change one app on the system.

==nice question )) I'll plan to make some automation tools to translate new roms and upload they to users

I plan to keep the Chinese version unchanged, and mount the modified ROM on top of the original fw. I also like to have some automated tools that can take a new fw , apply any of the changes we want to have and recompile it. So, actually, I am considering:

completely deodexing the ROM

adding the language res files and any other changes

recompiling the apps

preparing the ROM image

loading the rom image to sdcard and boot it over the system.img.

==nice plan but there will be a lot of work... I'd be difficult to make multilanguage rom because chinese brothers hardcoded a lot of links to "en" and "zh" resources
[Other SmartWatches] Neuer_User:
Yes, will be difficult. Not sure, if I manage.

Btw, my watch was flashed to english 1.3.0n, but now runs (temporary) chinese version 1.2.3 (without flashing). :D

The 1.2.3 rom image is on the sdcard and gets mounted over the (english) system. Seems to be working nicely. Just loosing some 600MB of space on /data. Is very nice for testing: No risk of bricking the watch.
[Other SmartWatches] Neuer_User:
How do you "stop android"? I only know, if I kill zygote I get a system restart, but not how to "stop" it and start it again later.
[Other SmartWatches] silver-alx:
You can write shell "stop" and "start" commands ))) It's very useful

---------- Post added at 12:46 AM ---------- Previous post was at 12:44 AM ----------

It's great! Do you mount file or separate partition?
[Other SmartWatches] Neuer_User:
I edited the init.rc in the boot image and added the following line in the "on boot" trigger:

exec /system/bin/sh /data/media/0/mount_custom_rom.sh

I can then temporarily boot this boot.img via fastboot ("fastboot boot my-modded-boot.img"). That will boot the system and also run the script I can place on the sdcard. This script currently contains:

#!/system/bin/sh

/system/bin/mknod /dev/loop0 b 7 1
/system/bin/busybox losetup /dev/loop0 /data/media/0/system-test.img
/system/bin/mount -o ro -t ext4 /dev/loop0 /system

Which mounts my custom rom image (which is currently just the 1.2.3 fw) over the system partition.

If the watch is rebootet, it will boot via the boot image on the internal flash (without calling my script), and everything is back to normal. :)

It's not a 100% perfect yet, as the mount of the custom rom seems to happen a bit late. The system has already read the "build.prop" from the internal system partition. I need to find out, when and how build.prop get read and try to place my mount script just before that action.
[Other SmartWatches] Neuer_User:
OK, assembled my first "custom ROM". Based on CN-1.2.3, I simply added the English translations from the PACE for a single app (StopWatch/AlarmClock). It's working nicely :) It probably helped that this app was already in priv-app folder.

I only copied over the "values" folder, renaming it to "values-en". I didn't copy "layout" over. But maybe I should, as the English text is a bit bigger and should thus use a reduced font size (is the "layout" folder the right one for this?).
[Other SmartWatches] silver-alx:
AlarmClock is a safe app )) Try to translate wearsettings.

I made a whole rom with russian in every screen and it was very nice until i try to do a hard reset. Now i've got many errors with signing.
[Other SmartWatches] Neuer_User:
Yes, AlarmClock seems to be easy. Now added "layout-en", so the text in the buttons got smaller.

I added "values-en" to WearSettings, but that doesn't even start now (press on the button "More Settings" and nothing happens). Not sure if I made a mistake. Will redoe this and see.

Your signing errors are coming from the PackageManager?
[Other SmartWatches] silver-alx:
Of cource! The main problem is system shared user cert. And you don't see settings because of this cert error.

You can try "logcat | grep WearSett"
[Other SmartWatches] Neuer_User:
So, the only solution then is to completely decompile and deodex all apps and the framework, then recompile them and sign all with your own key. Then this should work, I guess?
[Other SmartWatches] silver-alx:
I've just tryed it without success. Android didn't boot comletely because of caching previous certs and data. We have to make hard reset after resign but it's very dangerous ))

We need a kernel with auto fallback to recovery. I'll try to do it.
[Other SmartWatches] Neuer_User:
Easier: Take my method. If it won't boot, simply turn off and on again.
[Other SmartWatches] silver-alx:
How to do a hard reset with your method?
[Other SmartWatches] Neuer_User:
Haven't done it yet, but if I would need to, I would do it very similar. Instead of entering

fastboot boot my-modded-boot.img

I would try

fastboot -w boot my-modded-boot.img

which should delete cache and userdata.

If you want, I can send you my boot image.
[Other SmartWatches] silver-alx:
Deletes cache, userdata and your system image... How to boot system from image with empty data?
[Other SmartWatches] Neuer_User:
Sure, it deletes the full data partition? I thought it only deletes something like /data/data or so.

Well, in case it deletes all (which I am really surprised of), I would probably adjust my script on the sdcard to delete what needs to be deleted.
[Other SmartWatches] silver-alx:
Ok, i did it. ))) I made a kernel with a little bit simpler syntax that mounts system image in a right moment with proper build.prop. Everything is working fine except rebooting between systems because of android compiling every time.

But i spent many hours trying to do the same trick with data partition without success... The kernel remounts my image in the middle of the booting process.

Upd: I did it!!!! We've got isolated virtual machine ))
[Other SmartWatches] kkti:
Hi all. I'm playing with translation of CN version as well. I started on version 1.2.4f and my translation works well.

But unfortunately I was not able install new OTA update 1.2.5a. There was error when installation progress bar was shown on display.

So I installed Neuer version 1.2.3 from package convert_to_chn.zip. Than OTA goes directly to 1.2.5a.

Now I cannot install lower version than 1.2.5a. I have tried both 1.2.4f and 1.2.3. After installation failed to start Launcher and Watchface app.

Now I have English translation for Steps, HR monitor and Sleep monitor for version 1.2.5a. But I don't know if this modification can work with future OTA updates.

Maybe there is some rights problem. I upload modified apk and set rights 655. Maybe it is something else, maybe last OTA was specific update which check all apps? Really don't know.

Any suggestions?
[Other SmartWatches] Neuer_User:
As I mentioned before, ANY modification of the system image will probably make OTAs impossible. The updater script is checking for consistency of all files it will touch (maybe even more). If any file has been modified, the updater stops.

That's one reason why I work on the "non-intrusive" version.
[Other SmartWatches] Neuer_User:
Yeah, it's indeed like a virtual machine :D But don't forget, they use the same /data partition, of course.

Where did you put the mount command in the init.rc, so that you get the right build.prop? That would be nice to know.

I am currently still trying to learn how to modify apks in the way I want. I think I just discovered, that for (installed) system apps, I can copy over the old signatures even when I change the resources. So, I currently have my original WearSports app running with a small change in the strings.xml, and I do not get any permissions errors that I got before.

Next step will not be to test this with adding a whole "values-en" folder. If that works, I will try to produce a first english translated Chinese firmware.