yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Q&A, Help & Troubleshooting] Soufiansky:
You cant downgrade
[Galaxy S6 Q&A, Help & Troubleshooting] senolsenol1:
download mode working yateley gu46 6gg uk sm-g920f devaice please help me
[G3 Q&A, Help & Troubleshooting] smokarz:
Hi Guys,

I am looking to upgrade from my HTC One M7, and either the G3 ($250) or G4 ($400) seems like good upgrade options.

If I go with the G3 and saved about $150, what am I missing from the G4? Is the G4 worth the extra $150?

Thanks
[G3 Q&A, Help & Troubleshooting] copy2050:
i have this doubt too when i have to choose, and thinking on the price, the difference of performance and etc...and i think is better go to the G3...for many reasons:

1st: screen percentage to body ratio is better than the G4,

2nd: They perform similar, have the almost same specs, SD808 over SD801 dont worth the overpayd money.

3rd: Isnt curved, you dont feel much curve in G4 but G3 is flat...and is good to handle.

4th: They will have the Android Marshmallow like G4.

Is my opinion, i have the G3 since March and i love it, already play with G4 more than 10 times when i go to shopping center and i dont feel the same as i feel with my G3...go for it, worth a lot better the money you pay for the G3 over the G4.
[G3 Q&A, Help & Troubleshooting] Orcam:
I would also say go with the G3, people on the G4 forums will probably tell you otherwise, but for me its a no brainer.

The G3 has better battery than the G4.

The G4 has a better camera.

The G3 has similar performance.

There are alot of good Devs that like the G3 and for these reasons probably wont feel the need to throw it away for a G4 any time soon.

The G3 pretty much is a G4.

Its alot cheaper, save that $150 for postage, tempered glass, case and phone plan.

Lastly its not a bad phone at all. You will still get a nice shiny new phone with the box and all the bling with it. Oh and who really needs an amazing camera on a smart phone anyway, these days they take great photos if you use them properly and if you want better quality or have a problem with quality I would assume you would have a SLR for the sole purpose of taking photos.

Ps. The camera isn't by any means bad. Look at the photos thread in G3 general.
[G3 Q&A, Help & Troubleshooting] BurtGummer:
This is a toss up. The G4 has arguably the best camera available right now. Its display is slightly brighter than the G3's display and processor a bit faster. I have the G3 with the OEM Slim Guard case and there is no better phone-case combination out there. Battery life is wonderful with latest SkyDragon, display can still run with the best of them although auto brightness on this phone is useless, and camera while not in the conversation of best android camera is still a good snapper.
[Other SmartWatches] LaGra:
It's only an idea and I think it can be possible.

I'm using the APP AudioBT plus to send Google Maps navigation via Bluetooth to

my car radio. My car radio gets a call from AudioBT plus and gets out the Sound from

Google Maps.

Can this be used by a Smartwatch like U8 or other China Devices?

Could someone test this idea? Because I don't have a smartwatch. :D

Sorry for my really bad english.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
I upgraded from 5.1.1 to 6.0 by flashing the factory image without flashing userdata. Everything worked perfectly, but, as many people have noted, I get a "Your device is corrupt" message briefly on startup, before having the opportunity to enter my encryption code. Again, the phone functions just fine despite this.

I'm wondering what it is about my phone that causes this message to display. My bootloader is unlocked, though I don't think this alone should be a problem. I am completely stock, unrooted (though I was rooted on previous versions). As such, I don't think it can be a problem with the system or boot partitions, since, again, I have flashed and re-flashed these directly from the factory image. I don't see how it can be problem with userdata, since this isn't even decrypted when I get the "corrupt" message (i.e., I haven't entered the encryption code yet). Perhaps it's some problem with how userdata is encrypted?

Any logs that might give insight into where the fault is occurring?
[Nexus 6 Q&A, Help & Troubleshooting] cupfulloflol:
Verity is the cause. That post should answer your question.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
Thanks for the link. I'm still not sure this explains my situation. I get a red "corrupt" warning telling me my device is actually corrupt, which should mean that system files have been modified. However, my system is unmodified; I know this because I have flashed it directly (multiple times).
[Nexus 6 Q&A, Help & Troubleshooting] trent999:
Although it is extremely unlikely and might be a unique situation, Verity might have actually worked for what it was designed for, for once, and your system might actually be corrupted by either persistent malware or bad memory.

I would warranty return the phone, if possible.
[Nexus 6 Q&A, Help & Troubleshooting] droidstyle:
Wipe data factory reset from stock recovery.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
Thanks. I'm not looking really looking for a radical solution (wiping phone, returning it); I'm looking for an explanation (which might guide me to a less radical solution). Again, I wonder whether Verity makes a log somewhere. As I mentioned, my phone is working perfectly.

Hard to imagine it's persistent malware, since I've flashed every partition other than userdata (which is still encrypted when I get the "corrupt" message). Moreover, I'm by no means the first person to report this behavior.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
[Nexus 6 Q&A, Help & Troubleshooting] Tower1972:
I didn't notice mine until I installed a custom recovery. Hrm..maybe I just didn't pay attention lol
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
i didnt get it either. but i flashed a custom kernel as well, which gets rid of that message.
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
I'm unlocked, stock and get no such message(s). Expecting it when I install a recovery though
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
So I can't figure out what the true story is. Some people say that it happens to everybody with an unlocked bootloader, but, according to what you say, this isn't the case. I am stock in every way - recovery, bootloader, boot image, system image - and yet I get this warning. It's not a big deal, but it eats at me and makes me wonder whether there really is something corrupt about some aspect of my system.
[Nexus 6 Q&A, Help & Troubleshooting] dasDestruktion:
:confused:

It has to be changes to recovery. I'm running stock 6.0 with an unlocked bootloader and root and I have no such message on startup. Rooted and unlocked through Wugfresh NexusTool and temporary modified recovery option (non-persistent).
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
No, if you're rooted, it's a different story. The modified boot image installed when you root disables verity checking.
[Nexus 6 Q&A, Help & Troubleshooting] xtien:
I got the message after rooting my phone with CFRoot. Have done that before, always worked. But now the phone stops working after that boot message, I have reinstalled the stock image.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
I can confirm that this is not true. I ultimately factory-reset my phone from Recovery (it was acting strangely in other ways - Contacts crashing, for instance). My bootloader remains unlocked, but I no longer get the "Corrupt" message on startup.
[Nexus 6 Q&A, Help & Troubleshooting] MysticKing32:
I'm unlocked on marshmallow also and have never had that message
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
Take a look at here, it was my experience and solution.

https://productforums.google.com/forum/m/#!topic/nexus/sTu8Bdc1GLA;context-place=topicsearchin/nexus/category$3Adevice-security
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
A simple factory reset in Recovery was all I needed. But I was hoping for a solution that didn't involve wiping my phone, ... and some insight into why so many of us are getting this message with stock systems.
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
Glad you could fix yours with a simple factory reset. Mine was in a much worse situation where i immediately got the corrupted message once i entered gmail account into phone. Google reps couldnt find the answer to the issue but advised me to downgrade to previous os and take OTA to marshmallow, that definitly fixed the issue for me.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
Device verification on Android and Nexus can be a bit of an interesting subject.

In theory, dm-verity on a Nexus will ONLY validate the system image, and nothing else.

This is the key description that Google made regarding verified boot;

http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html

The key takeaways from that are;

1) an enforcing secure boot chain will involve validating each of the bootloader/boot partitions from the previous level, up to and including the boot.img.

2) The boot image contains the linux kernel and the verity_key file.

3) The verity_key file is the public key used to validate the contents of the metadata partition, which stores the hash tree for the system partition and is used to validate the contents of the system partition *on the fly*.

4) When dm-verity detects a change, it causes an I/O error.

5) On Nexus devices, the validation of the boot partition can be disabled.

The part that is interesting, is figure 2.

The part where it verifies metadata signature files --> no, causes it to reboot in logging mode and gives you the big ugly warning page.

Note that an unlocked Nexus 6 does NOT implement the yellow or orange warning states in its default configuration - see the description of "Class A". I'm not entirely sure if they can be enabled or not, but I've heard chatter of something to the effect of fastboot oem verify, which might enable validation of the boot partition.

So what happens during a dm-verity?

Well, when init tries to mount the system partition using dm-verity, it fails signature check. When it fails signature check, it sets a boot flag that it failed signature check, and *reboots*. The bootloader picks up this boot flag, and loads the error. If dm-verity PASSES signature check, it just continued boot as normal -- no rebooting.

So the approach for getting rid of that error message is actually this; if you tell init not to apply dm-verity, then the signature check is never even applied, so it continues boot as normal.

What isn't clear, is how it could be even remotely possible for a corrupt boot or cache partition to trigger a bootloader error. The only thing I can imagine, is maybe there is some additional check that isn't documented, or a bug in the bootloader that gets triggered when some boot flag is set wrong.
[Nexus 6 Q&A, Help & Troubleshooting] jj14:
Hmm - on my N6 (unlocked bootloader, but stock, unrooted - with Marshmallow), I don't see that message. From power off, I first see the "Google" text, with unlocked padlock at the bottom (indicating unlocked bootloader), I get the place to enter my passcode, and it then boots up - no "device is corrupt" message anywhere. There must be something else going on with op's phone
[Xperia Z2 Themes and Apps] katanabangbang:
Hi, This is my first attempt at making a theme...

Everything is pretty standard , I only changed the navigation buttons to PlayStation style buttons and changed the app drawer icon to the PlayStation logo.

Let me know if you want anything changed and I'll see what I can do :D

Link to theme apk: http://d-h.st/LaIE

Screenshots:

[IMG="screenshot"]http://http://xdaforums.com/album.php?albumid=11645&pictureid=50961[/IMG]

[IMG="screenshot"]http://xdaforums.com/album.php?albumid=11645&pictureid=50962[/IMG]

Peace!
[Xperia Z2 Themes and Apps] rychlin:
Looks like you've tried to copy Azmil's Playstation theme...

Odesláno z mého D6503 pomocí Tapatalk
[Xperia Z2 Themes and Apps] katanabangbang:
My navigation buttons are larger, the colors are different and the orientation of my back button is different...
[Xperia Z2 Themes and Apps] Alaa | Google Android:
The screenshot is empty !
[Xperia Z2 Themes and Apps] litlnicky:
big thanks , love the bigger icons , anychance you could please change the blue headers ? theyre everywhere maybe to orange , found in stock theme loll
[Xperia Z2 Themes and Apps] Gaugamela:
Great work!!

This is almost what I wanted in a Playstation theme.

Can I just ask if you have the possibility of making a variation of the theme?

I would love to see a version of this theme in the following way:

1 - Make the navigation buttons the same size as the stock Lollipop buttons,

2 - Make the accent on the status bar black or at least a very dark grey,

3 - make color variation of the toggle buttons with the color of each of the navigation buttons.

I really like your interpretation of a Playstation theme more than Azmil because in his theme the triangle button isn't in the orientation of the Lolipop back button and because the color theme of his theme is just horrendous.
[A3000 Original Android Development] gwhite5:
Summary

This is an attempt to get the Lenovo S6000H running CM12.1, which uses almost the same components as the Lenovo A3000H, but with a 10.1" 1280x800 screen. It could eventually be ported back in to the A3000H source, due to their similarities.

Status

Currently, I'm attempting to produce working ClockworkMod recoveries before I start work on the system.

XDA:DevDB Information

CyanogenMod 12.1 for the Lenovo S6000H, ROM for the Lenovo A3000

Contributors

gwhite5

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Testing

Created 2015-10-24

Last Updated 2015-11-12
[A3000 Original Android Development] Adam Hui:
Hi,

Good news for a great hope !!

Congratulations, i think all A3H users will supporting you !!

TIA

*] front LED holographic keyboard >> another dream in android
[A3000 Original Android Development] naeroki_bi:
So u made it for a6000 or a3000?
[A3000 Original Android Development] gwhite5:
S6000H; it's a similar architecture to the A3000H. I said that there was a potential of it being ported back to the A3000H. I believe that there are several changes needed to make a working recovery build in both device trees.
[A3000 Original Android Development] BobbyCurry:
Good news!!!

I am interested in contributing to our A3000H but I don't know how to get started. Could you share some links of guidance for rookie dev?

I've just finished setting up the environment for building CM12.1, but later I messed it up with local_manifest.xml from another amazing contributor JustArchi in the thread of Galaxy S3, turning out with error. (Actually I didn't have time to fix it these days.)
[A3000 Original Android Development] naeroki_bi:
Hope u will ported back A300H
[A3000 Original Android Development] gwhite5:
Have you tried reading the CyanogenMod wiki pages on the matter?
[A3000 Original Android Development] Red-code:
goog news lollipop is out for mt6589 devices like mmx canvas a116
[A3000 Original Android Development] Fisher.FreeMan:
this thread is for ETA not more and [MENTION=5771814]gwhite5[/MENTION] is not a developer:p
[A3000 Original Android Development] Gborg3:
Any luck on getting a functional build running? Any knowledge of anything more up to date than the stock 4.2 from Lenovo?
[A3000 Original Android Development] razzz23:
any progress?
[A3000 Original Android Development] coderex96:
Some news about this ROM or other ROMS on this tablet?
[Samsung Gear Fit] etatus:
I had installed version 1.117 from Galaxy Apps repository and it worked perfectly (except S Health sync) on my GT-I9000 with CM11 and build.prop modified with S4 data. But now a notification shows up telling I need to update to 1.127, but this new version doesn't work, probably due to Touchwiz dependencies (an error related to CSCFeatures class is shown in logcat). My Gear Fit firmware version is R350XXU0BOA2

Can anyone patch this last version (1.127.0827) for non samsung mobiles (touchwiz free)? :confused: Hopefully this new version could work with new S Health (now available in Google Play).

Ok, below it is available to download my first attempt to do this.

You can download the official apk from Samsung repository:

http://dvnhhc4qeiohk.cloudfront.net/221015/GearFitManager_OA2_1.127.0827_USER.apk

Got from JSON response:

http://wearable.samsungapps.com/update/check?mcc=222&mnc=01&fitCsc=ITV&mgrCsc=NEE&fitDeviceId=SM-R350&mgrDeviceId=SM-G900F&fitVersion=simonepsp&mgrVersion=1210&fitDevUniqueId=TEST&mgrDevUniqueId=000000000000000&langCode=it&localeCode=it-IT&firmwareFileName=UPDATEMODE_R350XXU0BOA2_R350XXU0BOA2.tar&minSdk=17&targetSdk=19

** New Features **

Better stability with S Health (Heart rate, Cycling, Podometer,etc...)

Modified some settings in blocking mode

Thanks! :)
[Samsung Gear Fit] Aussie4005:
Just a heads up this version doesnt work for me with S4 Active and Gear Fit. Gear Fit just constantly tries to reconnect/disconnect from phone and triggered my gear fit to crash. I had to then use Odin to reinstall the R350XXU0BOA2 OS back onto the gear fit, then uninstall gear fit manager and go back to GearFitManager_NE5_1.70.0617_USER to get it to work again.
[Samsung Gear Fit] etatus:
Can you sync with new S Health using GearFitManager_NE5_1.70.0617_USER version?
[Samsung Gear Fit] Aussie4005:
I tried it and unfortunately didnt work. Had to roll back S Health to the original version to get it to work. Hopefully Samsung provides a patch to fix this bug in their Gear Fit Manager, really annoying...
[Samsung Gear Fit] etatus:
So, just to have all the info about your working environment, what version of S Health are you using with Gear Fit Manager 1.70 to sync?

Thanks!
[Samsung Gear Fit] etatus:
Gear Fit Manager 1.127 apk modified for non samsung (touchwiz free)

Ok, I've managed to modify the original apk in order to remove CSCFeatures dependencies and now it works on my Galaxy S with CM11 (S5 build.prop). However the syncing problem with latest S Health is still present... :(

I attach the new apk in case you want you try it.
[Samsung Gear Fit] AlexHFOkumura:
But APP connect works?

Enviado de meu SM-G900M usando Tapatalk
[Samsung Gear Fit] gabi.:
Not working on Z3, maybe I should change build.prop?
[Samsung Gear Fit] etatus:
Notifications, phone calls, messages... seems to work, but App connect fails. I will check that.

I am currently using this /system/build.prop:

...
ro.product.brand=samsungs
ro.product.name=SM-G900F
ro.product.manufacturer=samsungs
ro.build.product=hlteskt
ro.product.model=SM-G900F
ro.product.device=SM-G900F
...
[Samsung Gear Fit] ilatimer1:
Hey everyone, I have a Nexus 6 running Marshmallow and got a Gear Fit for my birthday. I was wondering if I could get some advice on getting this working? From what I understand I need to install the GearFitManager_OA2_1.127.0827_USER_eTaTuS.apk on my phone, but do I need to edit the buildprop? Is there anything else I need to do? I appreciate any help you can give.
[Samsung Gear Fit] SteveRiley:
This version (1.127.0827) certainly seems not to like my T-Mobile Note 4 running 5.0.1 (PopRocks V15XxXR build). My brand new Gear Fit simply won't pair with it at all. When I try to pair the Fit to the phone, it fails. Error message on the phone says "Incorrect PIN or password." Which is weird, because the PIN shown on both devices is the same.

Does this simply not work at all on rooted phones? Or should I start trying various versions, downgrading until I stumble on one that works?
[Samsung Gear Fit] SteveRiley:
False alarm! Total user error here. When the Fit would prompt for connection, I was pressing the back arrow button rather than the orange check mark. Once I figured out my stupid mistake, the Fit connected immediately and is now operating as expected. Grrrrr I feel like a moron :p
[Samsung Gear Fit] jsvick20:
Google nexus 6

I also have a nexus 6 running Android 6.0 and every version of gear fit mgr I've installed force closes immediately. Any help would be appreciated greatly
[Samsung Gear Fit] Düdeldü:
master hint, use a samsung phone, i had no success with my nexus.

Now I´m back on my S4 (Imperium LL ROM v11.0 - Android 5.0.1 ) and I downloaded the version from the first post and it worked like a charm. Connection works, notification pops up, great!
[Samsung Gear Fit] mihneavlad:
Build.prop for Galaxy S

Hello, after many unsuccessful attempts I managed to load Android 4.4.4 Cyanogenmode 11 in my Galaxy S i9000. The final goal is to connect Gear Fit to this phone. I downloaded different versions of Gear fit Manager, but all of them fail to connect to Gear Fit. As I understand reading your post, is that I have to change also something in the file build.prop Unfortunately I cannot find any useful information. Can you please explain me what to do, send me the file or give me some advice? Thank you
[Samsung Gear Fit] etatus:
Take a look at: http://xdaforums.com/gear-fit/gener...it-manager-t3232338/post63545352#post63545352

You will need root privileges to edit /system/build.prop with your favourite editor (e.g. ES Explorer)
[Samsung Gear Fit] mihneavlad:
Still not working

Thank you for your answer.

I installed that update with number ...27... for Gear Fit Manager. I also modified a few lines in build.prop with the exact words like in your example. Even if the lines in my file weren't in the same order like in your file, I identified them and changed everything to match your file.

After this the behavior changed when connecting the Gear Fit. the program in the phone does not give errors anymore, but it cannot connect to Gear Fit. After waiting for about 2 minutes, Gear Fit tells me it cannot connect, even if the program in the phone still searches.

Any suggestions for me?

Thank you.
[Samsung Gear Fit] SalJR:
(just sharing)

Hi,

After several attempts, i could find an version of GF which is working on my LG G4.

Just followed this thread:

http://xdaforums.com/gear-fit/general/gear-fit-manager-htc-m8-5-0-1-lollipop-t3086187

Cheers ;)
[Samsung Gear Fit] mihneavlad:
Now what about S_Health?

Thank you, finally Gear Fit is connected to the phone, using the Gear Fit Manager you recommended. I remains the final step, but the most important, transferring the data to a fitness program. Any suggestions for a S-Health variant to work on a rooted phone with cyanogenmode?
[Samsung Gear Fit] SalJR:
Well, i don't use SHealth, but if i had to, i would go for Open Fit app. Ir works smooth.

You can find it here:

https://play.google.com/store/apps/details?id=com.solderbyte.openfit

;)
[Samsung Gear Fit] mihneavlad:
One more step

Thank you, I installed Open Fit and connected it to Gear fit. I understand that Open fit works with Google Fit, which is the program that treacks your activity. Now I cannot sync Open Fit to Google Fit. Any suggestions?

After a few more attempts, I solved all the connection problems. Thank you everybody.
[Samsung Gear Fit] lucky116474:
I can't get mine to work... Could you please tell me which firmware and Manager are you using? Thanks in advance
[Samsung Gear Fit] buddy66:
Force Close after pairing, any help ?

SOLVED: AdAway interfered with Gear Fit Manager
[Android Apps and Games] nisangames:
Guys, build my first endless runner game with two players to control at same time. You are very much welcome to try it out!!

Twin brothers on their adventure through the ocean kingdom. This twin brothers are sea surfers. Make them surf as long as they can and catch all the sea stars on their way. Unlike any other endless runner game,

SEA SURFERS

has two player (our twin heroes). You need to concentrate on both of them. If one brother dies, the other will jump into the sea. There are three lanes for you to surf. Left brother will start on the left lane and right brother on the right lane. There is also a middle lane. You can change the lanes while surfing, but don't try to bring both the brothers to the middle lane; then they will collide. Also beware of stone and broken bridges.

HAPPY SURFING!!!

Please look for "Sea Surfers" in Google Play Store.