Develop Bugs

Glorious Praise For The HTC Flashlight App

Old news to most but I had to drop a post to give recognition. The HTC flashlight app saved my bacon last night, in the aftermath of the snow and ice storms that rolled through Ohio. It uses the LED instead of the screen. It gives various brightness levels. It is glorious and I thank you.
Notes for improvement: Ditch the cute flashlight icon and give me a variable brightness setting that uses as many brightness levels as you can pack into it. Allow dual or single LED use as desired or needed and allow infinite brightness within each LED.
It's not a flashlight app if it uses the damn screen and can't change brightness!!!

Nice to hear one actually uses the flash. LG doesn't offer anything like that. Well they've got a flashlight app, but it's just the screen. I had to use it last night working on our home PC. Worked ok, but not nearly as good as a camera flash one.

Agreed. Amongst all the hate HTC get, they sure know how to make a damn good Flashlight App. Been a life saver a few times for me too!

I am a drummer and can testify to the usefulness of the flashlight app on a dark stage when you have dropped the nut off the top of a cymbal stand!!!!

Unfortunately it does not work on the Mozart (says device not supported even though it is HTC) and they never bothered updating it.

hsclater said:
Unfortunately it does not work on the Mozart (says device not supported even though it is HTC) and they never bothered updating it.
Click to expand...
Click to collapse
There's noting to update. The Mozard has a Xenon flash - it can't be always-on. That's also the reason why there's no video light on the Mozart.

yeah, it's the exact same flashing light HTC Sense ROMs use (WinMo and Android), I've been using this flashlight app ever since the HD2 came out, and it works flawlessly in WP7 just as it does in other operating systems. I even have it set as a tile for easy access when I need it!

Froyo 2.2.2 UK Retail Issues

I will update this thread as I found issues.
1. Middle of downloads the phone turned off and refused to switch on. Taking the battery out enabled restarting the phone again.
2. Despite of master reset/factory reset the phone is really laggy. Freezing applications made Defy very responsive but under 2.2.2 it appears no difference at all. (Second factory reset seems brought back somme life to my phone now...)
3. Definitely something is causing an annoying delay at startup even though the phone appears to be ready to use.
4. I have noticed once after a restart the capacitive buttons didn't light up for 1-2 minutes even though I was using the phone. The LauncherPro is installed and I'm suspecting that is the culprit here.
5. Once a number is dialed the phone locks itself. This is rather inconvenience when you need immediately use the key pad to select options. (20 June 2011)
Guidelines - 20 June 2011
I decided to write a guideline for Defy users. The information provided here have already been mentioned by others but normally not in one place. Please follow the steps below every time you flash a new ROM.
1. Master Reset (Whether you like this step or not this is required to do. Imagine upgrading a windows machine, it would be simply a mess in most cases. Any pro users would tell you always to do a clearn install. The same principle with Android applies)
2. Discharge the battery (It seems flashing a ROM messes up the battery calibration. Drain the battery to the point it won't boot then recharge it from the wall socket)
3. Avoid Restoring Apps (Only if is a must. Since Android 2.2 is different to 2.1 many apps might not work very well with the same settings restored from 2.1. Some vendors also offer different version for Android 2.2 or higher. Installing from market is best practice)
4. Avoid using widgets (They are simply battery eaters. Avoid them if they don't provide useful functionality to you)
5. Don't trust all vendors (Many apps placed on Android Market is written by programmers with no experience at all. A badly written app not only drains more battery but also takes up more precious RAM than it should. The less RAM you have, the slower the phone performs)
6. Don't keep large number of emails in your inboxes (They simply take up more memory)
7. Charge your mobile from wall socket when you can. It really does make a difference and also a recommended method by Motorola.
8. Put the Mobile Network to 2G when you can. It does save considerable amount of battery.
9. Switch off the phone once per day for 30 seconds before switching it on again.

Any chance to get hands on SBF for this release

Download available : Here http://direct.motorola.com/hellomoto/support/update/#

CSharpHeaven said:
4. I have noticed once after a restart the capacitive buttons didn't light up for 1-2 minutes even though I was using the phone. The LauncherPro is installed and I'm suspecting that is the culprit here.
Click to expand...
Click to collapse
I notice on my handset (UK T-Mobile eclair) that the capacitive buttons sometimes dont light up when holding the phone landscape. I think there is a light sensor somewhere which detects the ambient light and adjusts the capacitive button lighting.

techguyone said:
Download available : Here http://direct.motorola.com/hellomoto/support/update/#
Click to expand...
Click to collapse
I am on cm7 not sure if the phone will be detected by the msu. Will try once getting back home.
Sent from my MB525 using XDA App

techguyone said:
Download available : Here http://direct.motorola.com/hellomoto/support/update/#
Click to expand...
Click to collapse
That will get you the motorola update software.
During the update the .sbf is downloaded. We need to get the sbf, however it is deleted once the update has finished. I think this happens when the motorola software asks to "reboot phone, connect usb and verify update".
Please, if anyone does the update make sure to find the .sbf file and copy it somewhere safe before the update is verified. Then post to xda of course
Olly

binodnepal said:
I am on cm7 not sure if the phone will be detected by the msu. Will try once getting back home.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
I'm not sure either, I reverted to 2.51 and did the update form that point.
Anyone installed CM over 3.4.2_177-3?
Olly

kashavsehra said:
I notice on my handset (UK T-Mobile eclair) that the capacitive buttons sometimes dont light up when holding the phone landscape. I think there is a light sensor somewhere which detects the ambient light and adjusts the capacitive button lighting.
Click to expand...
Click to collapse
Thanks for that. I can actually reconfirm the issue. Last night when I was setting my alarm, with no lights in the room, I noticed once again the capacitive buttons' led were off. I was helding the phone in portrait and I know for sure this problem wasn't there in 2.1 because I always set my alarm after I turn the lights off (Bedroom's). When I press the Home Key to come out of the Alarm app the capacitive buttons lit up again.

binodnepal said:
I am on cm7 not sure if the phone will be detected by the msu. Will try once getting back home.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
If the msu is compiled by Motorola then I'm sure you won't be able to upgrade. The .msu can contain many other smaller installers that can do all the checking, exactly the way the update program does. Your only solutuion is to revert back to Motorola's stock ROM and give it a try.

Two more very annoying Defy/Froyo issues:
1) You can't disable the lockscreen anymore, so prepare for a lot of annoying swiping. Yes, you can get rid of the slider with an app called "No Lock," but this will also disable your security lock (pin code or pattern) which leaves your phone wide open.
2) The new gallery has more eye candy but less functionality, and it got slower too. If you open the folder list you can't read long folder names anymore. Is there is a way to run the old 2.1 gallery on Froyo?

I found the gallery the worst bit. So poor, I can't believe they let it go out like that. Runs like a dog.
I feel embarrassed for Motorola. Or I would if they were not working hard every day making their great hardware under-perform!
Seriously what a phone once CM is on it!
Olly

Use quickpic off the market, best gallery around
Sent from my MB525 using XDA App

rogier666 said:
Two more very annoying Defy/Froyo issues:
1) You can't disable the lockscreen anymore, so prepare for a lot of annoying swiping. Yes, you can get rid of the slider with an app called "No Lock," but this will also disable your security lock (pin code or pattern) which leaves your phone wide open.
2) The new gallery has more eye candy but less functionality, and it got slower too. If you open the folder list you can't read long folder names anymore. Is there is a way to run the old 2.1 gallery on Froyo?
Click to expand...
Click to collapse
As far as I'm concerned Motorola has degraded the phone and I'm not too sure if that is legal or not. I'm referring to the apps Motorola developed such as the video player and the gallery that you pointed out, not the Android itself. The additional Task Manager that was shipped with 2.1 in US is a welcome.
I have found my defy is performing slower, unless those claim Defy performs better with Android 2.2 has some settings that I don't. I ended up installing SetVSel to speed thigns up. It seems to me I'm getting 1/4 less juice out of my battery. I can reconfirm it once I play music on it for a couple of hours.
Not wanting to sound negative all the time, here are some positive things I found so far. I'm very happy with this update because now I got all my emails working on my handset which was important to me which missed the feature for the past 6 months. The browser appears to work very smoothly in most cases. I haven't used the Tasks app yet but that is another welcome addition as I always have a need for such features on portable devices. Other positive things about Android is to thank google not Motorola anyway. The slightly improved dialer worth just mentioning about it.
If Motorola refuses to give us Gingerbread then I hope they provide an update to fix some minor issues that either annoying or impacting the user experience soon enough.

I gotta say I'm pretty surprised about all the issues people are facing with the Froyo update everywhere. I had the french update installed which was one of the first available in Europe before moving on to the leaked 2.3.3 and it was smoother than ever. No bug at all except for the space touch getting a bit crazy while typing a text a few times. I didn't have many applications installed. A few people mentioned the update's fine as long as you don't have much installed on the phone but it starts getting extremely laggy when you keep installing more and more applications. After a factory reset there shouldn't be any lags though !

MrBelter said:
Use quickpic off the market, best gallery around
Click to expand...
Click to collapse
QuickPic would be the best gallery app if it would let us change the grid size (the thumbnail previews are too big now) and if it had "all photos" and "all videos" views. Unfortunately QuickPic only does folders.

lotfib said:
I gotta say I'm pretty surprised about all the issues people are facing with the Froyo update everywhere. I had the french update installed which was one of the first available in Europe before moving on to the leaked 2.3.3 and it was smoother than ever. No bug at all except for the space touch getting a bit crazy while typing a text a few times. I didn't have many applications installed. A few people mentioned the update's fine as long as you don't have much installed on the phone but it starts getting extremely laggy when you keep installing more and more applications. After a factory reset there shouldn't be any lags though !
Click to expand...
Click to collapse
Thank you for your post. In my experience there was a noticeable performance difference between 2.1 and 2.2.2 before a single application was installed. One theory to why some people are happy with the performance and others are not could be down to different components used in Defy. No one knows for sure if all Defy around the globe use exactly the same components or not. As you pointed out installing apps appears to effect the performance so we can conclude those that are not experiencing performance decrease are not power users.

rogier666 said:
QuickPic would be the best gallery app if it would let us change the grid size (the thumbnail previews are too big now) and if it had "all photos" and "all videos" views. Unfortunately QuickPic only does folders.
Click to expand...
Click to collapse
I am confused, all my photos and videos are in folders anyway and all the previews load like lightning so i fail to to see the problem, it is better than any default gallery whichever way you look at it.
Anyway only issue i can find with the retail 2.2 is how low highest screen brightness setting seems to be, the display is really hard to read outside now.

If you have a hundred pictures scattered over ten folders, would you want to tap into those folders one by one to browse all your photos?
Just like there's a unified inbox for mails from many accounts so you don't have to jump from one mailbox to the next, the stock gallery has a unified pictures view (all pictures in one grid) for all your folders.
If you want to swipe through lots of pictures from a bunch of different folders, having them all in one grid beats having to open all the different folders one by one.
If QuickPic would have the same unified picture view and custom picture grid sizes I would throw the stock gallery out. While QuickPic is working on it (are they?) I'll keep both apps.

The problem with the capacitive buttons that not lighting up is worse than I thought. It happens all the time, it doesn't light up and the only way to make it to work, when it gets really bad, by locking the phone (power switch) and unlocking it again.
The battery life noticeably shortened after the update. What I have done today was to completely discharge the battery to the point it doesn't turn on. Recharged it fully again without turning it on and from the wall socket. I'll report back if there was any improvements on Monday.
I also uninstalled VSel and set it to default CPU speed again. Despite of freezing so many apps and services the start up is really slow and I really feel the lag with the phone.

Another Defy/Froyo bug:
Dial *#*#4636#*#* to get into a service menu. From there battery_history/network_usage would tell you network traffic per app since last boot/unplugged/all time.
In Eclair all data was counted. In Froyo it usually doesn't count anything.

Light Flow Status [UPDATED 8/18]

Since the threads have been split AGAIN thought I would pop in here and post a thread for those of you that were following the progress on getting "Light Flow" to work on the US GSIII (or in our case the T-Mo GSIII)
The last notes on the developers blog are
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
25 July 2012 - it looks like it should arrive with me Friday or Saturday this week
(He's been waiting for a US GSIII, ATT in this case, to figure out whats messed up)
29 July 2012 - I've now got the AT&T S3 and I'm making good progress for users with root access
30 July 2012 - Just to add a little to yesterdays comment. With root access I'm controlling the led in the correct color. You don't get the always on green led and you can set different flash speeds. At the moment the issues are around the UI part of the app hanging in a few places for up to 30 seconds and also everything gets reset at reboot time until I go back into the app and reset some new settings again. I'm not too worried about either as the main thing is that the led control itself is working. I'm pretty sure root will be required for any solution though (unless Samsung fix the actual driver to accept the alpha channels - which is where the problem stems from). I did find rooting to be a pretty simple process and it only took around 10 minutes.
31 July 2012 - The boot issues have now been resolved (and may also fix startup errors that others were having with other phones).
I've read the few comments regarding root down below . I will continue to look for a solution that doesn't require Samsung but as they are transposing their data incorrectly it may be totally impossible to control directly via android without root. When not rooted we can only send data through the android API so unless shoe-horning some data into the led parts of the API manage to pass through the correct values I'll be pretty much stuck unless Samsung fix things. Trust me, I want it to work for non-rooted users too. My own Galaxy nexus (which is my main phone) isn't even rooted!
1 August 2012 - App sent to beta testers.
2 August 2012 - Some problems noticed when running with the charger not being plugged in causing the led flashing to freeze for long periods of time (even if controlled outside of the app). Therefore it looks like only solid (non flashing) will be available, but using another method there's some control of flashing the same colors that Samsung do when they control the phone, so red, blue and pulsing blue - like on boot.
3 August 2012 - Beta seems to be working well so far
4 August 2012 - Working on a couple of bootup bugs for root version of app. Created sample app and letter to send to samsung regarding Talkback issue and incorrect color mapping on non-rooted phones.
5 August 2012 - still working on the bootup issues, making some progress but lots of changes to make everything boot smoothly. I know a lot of people are keen to beta test, but for the time being I'm being kept busy enough with the current beta testers and I'm therefore not pushing the app out to a wider audience until these issues are sorted otherwise it'll only slow me down trying to reply to everyone. Thanks
6 August 2012 - new beta out to testers to see if the bootup issues are resolved. They seem to be for me from the testing I've done so far.
7 August 2012 - boot issues seem to be resolved. Added in root control for international version of S3 (GT-I9300) so users can have the led on when the screen is on. Adding in some new app support while beta testing continues.
8 August 2012 - fix for GT-I9300 settings in root mode. Updated translations files for new languages added. Testing on non S3 phones. Added support for another 24 apps. Started to prepare build for next release to play store (this usually takes about 1-2 days depending on if any issues are identified in the "lite" version of the app as development is all done on the full version)
9 August 2012 - it's here. Version 3.0.5 of the app has just been uploaded to the market. It may take a few hours to show but you should start to see it soon. Note that it's still only adding functionality for rooted users for the time being.
10 August 2012 - ok, I think I've managed to get control of the LED for non rooted phones! It's a solid light, but it looks like the solid green light can be got rid of and then with some re-mapping of the incorrect color maps I may be able to get a real color list. I've had my phone running for about 9 hours now trying different combinations automatically at about 100 per second to come up with one that matches the command issued from the root version. It's also given me some insight into how the led color has been mapped incorrectly by Samsung. It'll be a solid LED as the flashing has similar problems to root, but if I work out a way for root to make it flash I should be able to do similar for non-rooted phones.
11 August 2012 - I've managed to get the app working on non rooted phones. There's no solid green light when you've no notifications and when you select a color from the color list it shows the correct color. I've a bit more testing to do, but things are looking good.
At the moment the differences between the rooted and non-rooted version are:
Rooted version: the led stays on when the screen is on, not rooted it goes off (which is standard android default functionality)
The blue pulse and 2 flash colors are not available as there's no way to access this control file
If you use the "custom led color" option, those colors will be messed up as there's no way I'll be able to write that to issue the correct colors as the color matrix is too messed up, but the main default 18 colors all show up fine and you can still "play" with custom colors, just don't expect to get the color you chose!
12 August 2012 - Not much to report today, non rooted test still going well and I've been benchmarking the battery usage ready for trying to add in the flashing code (plus trying to work out in my head the best way to tackle flashing). Sounds simple, but it's quite tricky.
13 August 2012 - started work on the flashing code. I've got the led flashing, but there's still quite a lot to do to get it working, stopping and starting through the different color cycles.
14 August 2012 - making good progress on the flashing. Yesterday the flash color was incorrect (that's now fixed) plus now I'm managing to mix different flash rates with solid leds for different notifications (e.g. charging solid, gmail flashing etc) and actually make the flashing services stop when they need to. A few occurances where the state gets mixed up, so the solid will be off instead of on when it is its turn to show, but improving.
15 August 2012 - got flashing for root mode working, changed the flash rates to be better for less battery drain, added notification regarding more battery drain for flashing speeds. Default app to "Always on" for notifcations on USA S3's. USA S3 detected on startup of the new version and automatically set to the correct mode to work (unless you are already running in root mode). Now I just need to look into the "sleep mode" settings as they are getting ignored for s3's. Hope to have a beta very soon - but please don't send me lots of requests yet!
16 August 2012 - though I'd come across a show stopper for non-rooted users as the default blue flashing led that Samsung provide for missed events was overriding our notification (which is different to other apps raising notifications that I'd already tested). This meant things like gmail and missed calls were killing the app's control and Samsung's default behavior took over (another non-standard way to do things - thanks Samsung). Finally after a lot of scratching my head and having a play around I found a way to kill their blue light by cancelling it shortly after it's been raised. It's a real hack, but seems to work. For those familiar with android it's using a bit of "reflection" to access bits of android not normally accessible. Phew, after a day of worry, I think things are back on track!
17 August 2012 - I've been building yesterdays hack into the app and making sure it doesn't affect the user if the screen is on when a notification comes in. Due to the inconsistent timing of the blue led starting to flash after a notification it's been quite tricky, but seems to be working quite well now.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For those of you who don't know, the color mapping is different for some reason between our GSIII and the International version which is why the colors are off if you are currently using light flow and also why the green light stays on when there is no notification
Its all being looked into by the developer, you can follow along at his blog here

nonmindo said:
Since the threads have been split AGAIN thought I would pop in here and post a thread for those of you that were following the progress on getting "Light Flow" to work on the US GSIII (or in our case the T-Mo GSIII)
The last notes on the developers blog are
25 July 2012 - it looks like it should arrive with me Friday or Saturday this week
(He's been waiting for a US GSIII, ATT in this case, to figure out whats messed up)
29 July 2012 - I've now got the AT&T S3 and I'm making good progress for users with root access
For those of you who don't know, the color mapping is different for some reason between our GSIII and the International version which is why the colors are off if you are currently using light flow and also why the green light stays on when there is no notification
Its all being looked into by the developer, you can follow along at his blog here
Click to expand...
Click to collapse
Pretty buggy for me, waiting for it to work better. Just using standard leds for now and noled app overnight so I don't have to disable the leds but s till notifications without bright blinking blue.

bump for updates

If only I can set led colors for separate Contacts text like go SMS let's me do. This is the only reason I want led control.
Sent from my SGH-T999 using xda app-developers app

Even with 3.0.5 I'm still getting the green light staying on. If I disable the led for phone then none of the notifications work. Any body still having these problems after the update?

elracing21 said:
If only I can set led colors for separate Contacts text like go SMS let's me do. This is the only reason I want led control.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about free, but the paid app can do exactly that. Once in the app and in the notifications section, touch the contact + icon on the top right. You can choose colors for mms, SMS and missed call for that contact.
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
sarmadical said:
Even with 3.0.5 I'm still getting the green light staying on. If I disable the led for phone then none of the notifications work. Any body still having these problems after the update?
Click to expand...
Click to collapse
Are you rooted and do you have root mode enabled in the app? I'm rooted running a stock deodexed rom and the app is working perfectly for me. All colors are working and the app showed me the proper notifications about 100 times today.

The app is still buggy. When I have set a few notifications and some go off at the same time or I do t check my phone and they stack the colors don't flash Constantly or it freaks out and just shuts off. When I turn my screen of the red led flashes for no reason. I had to uninstall ill try it again I am a few weeks after the dev works out the kinks.
Sent from my SGH-T999 using xda app-developers app

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
[/COLOR]
Are you rooted and do you have root mode enabled in the app? I'm rooted running a stock deodexed rom and the app is working perfectly for me. All colors are working and the app showed me the proper notifications about 100 times today.[/QUOTE]
Yup. I'm rooted, and provided root access to the app. I still get the colour bug. Not sure what's up.

i updated the app, but still get the talkback bug everytime i open a folder or do other movements... still no go for me.

Try disabling Samsung tts in the manage apps section.
Sent from my SGH-T999 using xda premium

xanderdad said:
Try disabling Samsung tts in the manage apps section.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks, it worked.

bugs...
SAMSUNG GALAXY S III T999 Blue 16GB
ROM--FreeGS3 GSM R6
THEME-- ICS Blue MOD Theme V3/ Blue clock with Battery fix
KERNEL-- SGS3-ATT-TMO-kernel-tw-010u_r2 (overclocked to 1836MHz)LOVE IT!!!
RECOVERY--T999 CWM Touch/ExtSdcard read/write
MODEM--TMOGalaxyS3UVLG1Modem
Had to uninstall... Kept causing my auto-brightness to stay dim when coming out of sleep state.

bump for updated info

[APP]Lg touch LED notifications

Hey guys i found this app using which we can use our touch buttons as LED notifications
It's available for free from Google play store
Description from play store:
Touch LED Notifications
This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service.
Supported devices:
* LG Optimus 2X/T-Mobile G2X/Star (P990/P999/SU660)
* LG Optimus Black (P970)
* LG Optimus 3D (P920)
* LG Nitro (P930)
* LG Optimus ME (P350)
* LG Marquee (LS855)
* LG Prada 3.0 (P940)
Other phones might also work if they're similar to one of the supported devices. Even though a device is listed above your rate of success may vary depending on ROM and/or if you require root. It may also not work perfectly due to various limitations of the phone.
If you get a message about rooting, you have to root your device to get LED notifications to work. This is not something I've chosen to do, it is because the devices does not have the correct permissions and root is needed to correct them. If you wish to root your device you're doing so at your own risk.
Translations of the app is very welcome. If you wish to translate please drop me an e-mail and I will give you the link to the strings.xml-file.
Gmail 2.3.5+ no longer works with the built-in Gmail-check. To get it to work again Gmail has to be disabled in Notifications and then added as a monitored activity (Notifications -> Monitored activites -> Gmail).
* It's recommended to open the app once after update to initialize new features and updates.
* If the latest version doesn't work then previous versions can be downloaded here: http://martinborjesson.com/android/
A note about Accessibility:
The app uses Accessibility to listen to notifications from other apps. When activating this feature a warning will be displayed, this warning is part of the Android-system and is displayed for every app that uses Accessibility. The warning can safely be ignored as the app only uses the notification-part and since the app does not require an Internet-connection no data can be sent away somewhere.
Some tips on how to increase the battery life when using the app:
Every time the LEDs has to change or when the vibrator or sound is started the device has to wake up for a short moment. More wake-ups results in decreased battery life. So to improve this set the Touch LED mode to Constant and optionally use a lower Touch LED brightness, for example 15-25%, and do not use vibration or sounds. Devices that can handle one LED at a time will only use one to increase battery life.
Thanks to
Paul at MoDaCo for sharing how to change the brightness on the touch LED buttons !
[email protected] for helping me with the LG Optimus Black implementation !
Everyone who helped me out with the app during its development !
Disclaimer: It is not known if using this app have any negative effect on the touch LEDs in the long term, so use at your own risk. By installing this you agree that I take no responsibility if anything happens to your device while using this app.
DOWNLOAD

Nice one Anurag, thanks!

rly nice 1, works great on my P350

there is updated version of this app in optimus black forum

gud 1.. thanks..

[US BETA 3][ZSL5] Official Android 10/UI 2 BETA for the US unlocked Note 10+ (N975U)

READ THE OP FIRST BEFORE POSTING!!
This thread is for discussing bugs, issues, work around, and suggestions for the beta for the US models. Please no discussion of the international models. There's already a thread for that, and I don't want to confuse bugs/fixes for the wrong model.
If you have the international model (N975F), please see @henklbr 's thread here:
https://forum.xda-developers.com/ga...laxy-note10-sm-n975f-official-oneui2-t3987433
Stay on topic. This thread is to discuss issues with the beta, not how to get it. There's already a couple threads for that as well. The basic step is to sign up for the beta in the Members App, or download the OTA from firmware.science. For further assistance, please see @tlbland0426 's thread at:
https://forum.xda-developers.com/ga...available-note-10-unlocked-sm-n975u1-t4002783
When posting your issues, please state what software version you're on (current one is 2ZSL5), and if you did a dirty flash, restored data, or did a complete clean install.
I know this isn't an official channel to report to Samsung, but bugs discussed here can be forwarded to Samsung in the beta app.
Please read the OP and the entire thread before posting.

Been running the beta (ZSK3) for less than 24 hours. I did officially register, and started to download the OTA through device settings, but it requires WiFi. I was at a hotel and the WiFi there was achingly slow, so I went to firmware.science so I could just download the OTA with LTE, then manually flashed it through recovery.
I performed a clean install. Factory data reset, flash OTA, then another factory data reset. Then I set it up from scratch. I didn't restore anything.
Here is my experience so far:
Pros:
1. Dark Mode - I love the native system-wide dark mode.
2. Space below keyboard - I use gestures and GBoard, and I like how now even third party keyboards are pushed up a bit, and you have the keyboard switcher and close keyboard buttons.*
3. Charge Status Toggle - Ability to turn off the charge status. (Thank you Samsung!)
4. Fingerprint Icon Toggle - Ability to turn the fingerprint reader icon on or off.*
5. Improved Biometrics - Fingerprint reader seems to work MUCH better now. Even with the last few updates on Pie, my FP reader was almost worthless. Now it's nearly flawless.
Cons/bugs:
1. Brightness Slider - No longer able to display brightness control on top in the notification shade. I use the brightness slider a lot, and it's frustrating having to fully expand the notification shade when I want to adjust it.
2. Gestures - The new gestures aren't very intuitive. I prefer the gestures from Pie. I know I can still use those, but I'm really trying to get used to this style, since it's what Google will push everyone toward anyway. This system of gestures is Google fault not Samsung's.
3. Home screen Jank - I occasionally get issues with the home screen freezing. Seems to be when I'm having issues with the gestures, particularly getting Google Assistant to activate via swipe.
4. Syncing issues - There's several Samsung apps/services that will not sync. Samsung Pass, Samsung Internet. Samsung Contacts, and a few others. Under Samsung account settings, when trying to sync them, they say "syncing" then change to "Couldn't sync." This occurs in WiFi and cellular.
5. Disney+ - Not compatible from the Play Store. I was able to install it, log in, and watch movies with a work around, so I know it works. Not sure if this is Disney's problem, or Samsung's. I know it works on other devices running Android 10, so who knows.
6. Netflix - this could've been my issue. I was in the Netflix beta program, and Netflix installed, but kept telling me to update, then telling me it wasn't compatible. I had to leave the beta, and sideload an older version from apkmirror. Working fine now.
7. WiFi issues - It connects to WiFi just fine, but some apps wouldn't load or allow me to sign in while on WiFi. See below.
8.. VUDU - It would initially force close. I deleted and sideloaded an older version that would freeze on the load screen. Updated that version through the Play Store and it wouldn't force close, but would freeze. I was on WiFi and when I turned it off VUDU loaded. (WiFi was pulling 250 Mbps down, so it wasn't the issue).
9. Hulu - When I tried to log in, it kept saying couldn't reach server. Again, was on WiFi in a restaurant pulling 250 Mbps down. But once I shut off WiFi, it signed right in.
10. Full Immersive Mode - This option is still missing in Samsung Internet and most video apps. It works just fine in YouTube and Disney+. We should have the option of using full Immersive Mode at least in the internet browser. As far as movies, make the rounded corners on the black bar less rounded.

Disney+ app workaround. See below.
CREDIT TO @tlbland0426 !!!
tlbland0426 said:
Yeah, it's not available in the Play Store on the beta. But I have found a workaround and got it installed and working.
Download all 4 files from here:
https://drive.google.com/open?id=1-QC8B-Cic3gU00CF3u1pYvP-zWZ663nG
Install the SAI.apk
After that has been installed open that app and then select Install APKs
Select the 3 other apk files that you downloaded then click Select (3) and it will install the working Disney+ app
Click to expand...
Click to collapse

" 1. Brightness Slider - No longer able to display brightness control on top in the notification shade. I use the brightness slider a lot, and it's frustrating having to fully expand the notification shade when I want to adjust it."
You actually can put it back on top, you just need to set this.
Just press the 3 dots when pulling the dropdown menu, then select the quick layout panel
No issues with Disney+ and Netflix either

Brotuck said:
" 1. Brightness Slider - No longer able to display brightness control on top in the notification shade. I use the brightness slider a lot, and it's frustrating having to fully expand the notification shade when I want to adjust it."
You actually can put it back on top, you just need to set this.
Just press the 3 dots when pulling the dropdown menu, then select the quick layout panel
No issues with Disney+ and Netflix either
Click to expand...
Click to collapse
Thank you!!! Not sure why they hid that option.
So you were able to download and install Disney+ from the Play Store while on the beta?

Mr. Orange 645 said:
Thank you!!! Not sure why they hid that option.
So you were able to download and install Disney+ from the Play Store while on the beta?
Click to expand...
Click to collapse
Yes no issues with that, but i cannot remember if i installed the apps before i upgraded...

One of the only real issues I'm having is with the new gestures, mainly the recent apps gesture. When using it straight from the home screen it works like 50/50 for me and sometimes causes OneUI Home to crash but using it when you have an app open it seems to work much better.
Edit: (2ZSK3 obviously). I got the OTA through the beta registration and had some issues because I had #hex installed so I did a factory reset. I did however restore everything from Samsung Cloud afterwards.

Brotuck said:
Yes no issues with that, but i cannot remember if i installed the apps before i upgraded...
Click to expand...
Click to collapse
It still shows as incompatible in the Play Store for me. Go to the Play Store and look for Disney+. Below the unsintall/open buttons, tell me if you see a message in red lettering that the app is now incompatible with your device.
tlbland0426 said:
One of the only real issues I'm having is with the new gestures, mainly the recent apps gesture. When using it straight from the home screen it works like 50/50 for me and sometimes causes OneUI Home to crash but using it when you have an app open it seems to work much better.
Edit: (2ZSK3 obviously). I got the OTA through the beta registration and had some issues because I had #hex installed so I did a factory reset. I did however restore everything from Samsung Cloud afterwards.
Click to expand...
Click to collapse
Yes, the recents gesture from home screen is very wonky. I had some home crashes too when I first installed and set everything up, and I actually wound up doing another factory reset to get rid of them.

disregard

znel52 said:
disregard
Click to expand...
Click to collapse
I have been running the U1 firmware on my Verizon Note 10+ since the day it launched. It retains wifi calling, volte calling, and visual voicemail. The only thing missing that I've found so far is native video calling in the phone app but that wasn't a big deal to me as I never use it anyways.

Do you mind sharing how you were able to get Disney+ installed and working?

Romans8vs1 said:
Do you mind sharing how you were able to get Disney+ installed and working?
Click to expand...
Click to collapse
Look at post #3 on this thread...

tlbland0426 said:
Look at post #3 on this thread...
Click to expand...
Click to collapse
How'd I miss that! Thank you!

Also found doing factory reset after installing this that whatsapp would no longer verify my number.

So today I sent several feedback reports to Samsung through the OneUI beta app. Please keep the feedback coming. In my experience with past betas, Samsung really does listen to our feedback when it's directed through the proper channels.

Besides the new animations I don't see anything really worth writing home about. It's beta so there's quite a bit of bugs. Android auto on my android 10.25 screen exhibit a buzz and audio moving from car to phone sporadically. The new gesture navigation is not as easy to use. I much prefer using Pie control (which is not 100% compatible now) for launching home, recent, and back. One handed operation to swipe diagonally up to shrink the screen. Diagonally down to bring top of the screen down. I've also seen more battery drain and on screen fingerprint isn't as accurate anymore. Beta 2 is supposed those 2 things. The one UI lock up is also being addressed.
I'm hoping beta 2 will soon be releases for US unlocked. Otherwise, I think I will switch back but dreading that as it will factory reset my device.

aznmode said:
Besides the new animations I don't see anything really worth writing home about. It's beta so there's quite a bit of bugs. Android auto on my android 10.25 screen exhibit a buzz and audio moving from car to phone sporadically. The new gesture navigation is not as easy to use. I much prefer using Pie control (which is not 100% compatible now) for launching home, recent, and back. One handed operation to swipe diagonally up to shrink the screen. Diagonally down to bring top of the screen down. I've also seen more battery drain and on screen fingerprint isn't as accurate anymore. Beta 2 is supposed those 2 things. The one UI lock up is also being addressed.
I'm hoping beta 2 will soon be releases for US unlocked. Otherwise, I think I will switch back but dreading that as it will factory reset my device.
Click to expand...
Click to collapse
Beta 2 was released this morning finally. I agree this is one of the buggiest betas I've tried in the last few years. I'm the opposite of you with the fingerprint reader though. It was almost useless on Android 9. On this beta it's much faster and more accurate. Works nearly 100% of the time for me. Although it seems more sensitive to the screen being dirty.

Beta 2 has been released
I awoke to a notification that beta 2 was released. Below is the changeling from Samsung.
[ Beta Software Update )
:l S/W Version
- ZSKH
:l Bug Fix
- The screen flickers
- When returning from some app to the home screen the
background can appear to be blurred
- The status bar disappears when turning the screen off,
/vhile some app is opened
- When taking a screenshot, and opening Recent window
after that, the screenshot of recent window is captured
- Keybaord is cut at the bottom
- Keyboard can't be resized
- Two contacts app display after update
- Application that has been removed from the folder and
laced on Home Screen disappears
- After update, app shape changed to Android app shape
- AOD doesn't appear while charging
- A Noise can be heard when connecting a Bluetooth device
- Improved gestures interactions, some problems have been
axed.
:l Known Issues
- No scrolling in widget state.
- The Fingerprint icon stays on the screen after unlocking the
device.
: Disappears when unlocking with fingerprint icon displayed
)n lock screen

I took the OTA this morning and it seems to be running ok so far. The screen flickering was something I saw alot on beta 1 and that seems to be corrected. My battery life was pretty good on beta 1 also so I will have to see how this performs. Thought it was interesting it has the December security patch already.
Sent from my SM-N975U1 using Tapatalk

Mr. Orange 645 said:
Beta 2 was released this morning finally. I agree this is one of the buggiest betas I've tried in the last few years. I'm the opposite of you with the fingerprint reader though. It was almost useless on Android 9. On this beta it's much faster and more accurate. Works nearly 100% of the time for me. Although it seems more sensitive to the screen being dirty.
Click to expand...
Click to collapse
My lack of patience and frustration with beta 1 got to me and downgraded to 9 over the weekend. However I did not deregistered for the beta just in case I want to try future betas. The one most frustrating for me was audio output going from car to phone and vice versa when using android auto. I did report it so maybe it will get addressed in beta 3.
---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------
Romans8vs1 said:
Do you mind sharing how you were able to get Disney+ installed and working?
Click to expand...
Click to collapse
You can also restore apps in Smart Switch if you had backed it up on Pie.