I'm on CM 13 and android wear doesnt opens.
{
"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"
}
Please help
VeerAmrit said:
I'm on CM 13 and android wear doesnt opens.
Please help
Click to expand...
Click to collapse
I'm also experiencing the same thing now. Try downgrading the app perhaps?
Sent from my ONEPLUS A3000 using Tapatalk
VeerAmrit said:
I'm on CM 13 and android wear doesnt opens.
Please help
Click to expand...
Click to collapse
I had the same issue... googled it and others had issues with the newer watches after upgrading to Wear 2.0, which isn't my issue because the original 360 isn't getting 2.0. BUT, their solution fixed the problem.
https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=224093
I changed the build.prop from:
ro.build.type=userdebug
To:
ro.build.type=user
Worked like a charm!
I restored old backup of android wear using titanium backup. Others can try downgrading the app.
Changed build prop
Also changing build prop to user from userdebug worked for me as well. I had saw some reports that if build prop is already user it may be necessary to change to userdebug instead. Also don't forget to save the changes and reboot for the fix.
Same fix worked for me. My phone was running a signed userdebug. I changed ro.build.type=userdebug to ro.build.type=user, rebooted, and now things are working perfectly for now. Hopefully they don't figure out that I'm running 6.0 when it should be on 5.0...
Why can't google just let us tweak our devices?
Related
Hi guys,
I'd really appreciate if anyone on stock 4.2 could check if they can load this website on their stock browser. I notice many of the news articles on this site cause my browser to close. It's the mani newspaper in Ireland, so it should be compliant. I'm wondering is it just my phone though? Maybe it needs a wipe? Any ideas? I've looked at the logcat files but cannot figure it out.
http://www.independent.ie/entertain...-most-famous-justice-judge-judy-29184842.html
Any feedback appreciated. Thanks
works fine for me, no crashing - went through few articles on the site - completely stock 4.2.2 on UK 3 Network and using stock browser
dello said:
works fine for me, no crashing - went through few articles on the site - completely stock 4.2.2 on UK 3 Network and using stock browser
Click to expand...
Click to collapse
Thanks for checking this! I appreciate it. This is exactly what I wanted to know. I guess something (an app maybe) on my phone is causing the crash. I'm stock on 4.2.2. Build JDQ39 on O2 Ireland.
:good:
mcgon1979 said:
Thanks for checking this! I appreciate it. This is exactly what I wanted to know. I guess something (an app maybe) on my phone is causing the crash. I'm stock on 4.2.2. Build JDQ39 on O2 Ireland.
:good:
Click to expand...
Click to collapse
Any developers decode what is going wrong?
{
"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"
}
Hello Everyone,
I just want to share what I made for my phone. This is for TW Android 4.3 only.
Change Log
Adnoird 4.4 Phone Dialer icon
Change Battery Icons (Android 4.4)
Change Multiple Windows to Transparent
At your own risk. I will not responsible for anything that may go wrong with your device.
{
"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"
}
Instruction:
1. Download File
2. Reboot into Recovery Mod.
3. Install.
4. Wipe Cache/Devike and Set permission.
4. Reboot your phone.
*This is for all of us. Any suggestions are greatly appreciated.
*Please don't report any issues. lolz
Enjoy
Click to expand...
Click to collapse
Thank you but im a little unsure of what it looks like after reading the changelog
Sent from my SGH-T999 using XDA Premium 4 mobile app
Excellent, my suggestion is that you change the dialer and contacts style kit kat
flashed this on a stock tw 4.3 rom and it gave a bootloop. I followed instructions word by word
Sorry guys, I have been very busy that I didn't have a chance to respond to you guys sooner.
I guess, most of you already had the answer.
@ vibrant themer can you do the contact icon like this one
http://forum.xda-developers.com/showthread.php?t=2601247
Sent from my SM-T310 using xda app-developers app
(SOLVED)
I recently updated my Google pixel XL to Android O but there is a problem, the chat heads on Facebook does not work and when I try to turn it on manually it just reffers me to the settings but the option is already on. Does anyone know a fix?
{
"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"
}
Update: The update fixed it, thanks guys!
skoglundsimon99 said:
I recently updated my Google pixel XL to Android O but there is a problem, the chat heads on Facebook does not work and when I try to turn it on manually it just reffers me to the settings but the option is already on. Does anyone know a fix?
Click to expand...
Click to collapse
It's probably an issue with Android O, after all it is in beta. Perhaps the facebook app hasn't updated there app to support Android O.
skoglundsimon99 said:
I recently updated my Google pixel XL to Android O but there is a problem, the chat heads on Facebook does not work and when I try to turn it on manually it just reffers me to the settings but the option is already on. Does anyone know a fix?


Click to expand...
Click to collapse
I have 0 issues with fb messenger on Android O. I use it all the time. If I experienced this, I would first uninstall fb messenger and reinstall, if that didn't work, I would uninstall fb and if that still didn't work I would either try to factory reset or reload android o
Why Samsung galaxy s4 can get lineage os 15 update but note 3 cant? Anyone can explain why?
jyjc0324 said:
Why Samsung galaxy s4 can get lineage os 15 update but note 3 cant? Anyone can explain why?
Click to expand...
Click to collapse
What do you base that on? Some of the sites that mention Lineage 15 if you google it? If the maintainer of the device decides to work on Lineage 15 it will come.
I found some sites claiming to know what devices that will get Lineage 15... They probably just guess and have the Lineage 15 stuff written as clickbait.
Sent from my XT1650-03 using Tapatalk
{
"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"
}
via @trader418 's twitter
so be patient it's coming soon
I'd love to see android 8 on n9005
wessam.sh said:
I'd love to see android 8 on n9005
Click to expand...
Click to collapse
One question when ?
So what?
Any news?
iperv said:
So what?
Any news?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=244501
So:
I'm running now Los 15.1 on my n9005.
It was not a straightforward install.
I had to upgrade bootloader/modem, carefully choose the correct gapps and root only worked with magisk.
It seems to be a really good and super usable rom, excellent usability.
Anyway, I had a classic 8.1 oreo Bluetooth issue - phone calls are noisy/unusable; audio/music/pairing is ok.
What's the right place to report bugs about this awesome rom?
Hello everyone. On YouTube I saw some videos where it was possible to activate the 120Hz frequency on the screen. I had already tried it when I had Android 11 mounted on the phone, but it didn't work. So, since I have now updated to Android 12, and to be honest, I don't like that much, I would like to go back to Android 10 to be able to take advantage of the 120Hz screen function. Is it possible to downgrade 2 operating systems?
Nope, not possible to get back to 10...
Maybe....maybe 11 if you're 'lucky'
However 120hz will never work on this phone... the mod your thinking of made the option show, but it didn't actually change the refresh rate.
The Note 10 and 10+ do not have a 120Hz capable display. Display refresh rate is a hardware capability; going back to 10 won't do anything.
Ok, thanks for the clear answers. Oh well, I'll try to go back to Android 11 anyway, because I just can't see 12, it gets on my nerves!
ExileTM said:
Ok, thanks for the clear answers. Oh well, I'll try to go back to Android 11 anyway, because I just can't see 12, it gets on my nerves!
Click to expand...
Click to collapse
Highest I'll go is Android 10.
The bootloader version dictates how far you can roll back.
In this case my bootloader version is 2 on this Android 9 variant.
{
"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"
}