Database Info

[TEST] HTC Messaging Fix (probably NOT!)

14/12: A few of us encounter the SMS sending problem again after applying the fix. So it looks like the latest messaging client found in ROM 1.61 doesn't fix the problem. Of course, I'm assuming that the problem lies on the messaging solution, rather than radio, as explained below.
Hi all,
It's probably a well known fact that HTC messaging has some serious bug, specifically on the reliability on SMS sending.
I've done a quick test, and noted that when the problem happens, usually the network is weak and the phone is undergoing through some network switching (e.g. from 3G to G in order to get better reception). This is consistent with the findings with some folks here.
However, I don't think this is the cause, I say it's a symptom, because network switching is common in any phone, and any reliable messaging app should be able to handle such scenario. On further testing, I noticed that when the problem happens, the messaging service that HTC developed to take over the entire messaging send/receive from Windows Mobile, would crash and won't be able to restart.
So this leads to my belief that the bug fix needs to be at the messaging service and/or the messaging client, rather than the radio.
Of course I could be wrong, but when I hear that HTC has released a new ROM 1.61 with new messaging client, I decided to give the new files a try.
Thanks to Steve0007, who had kindly forwarded me the files very quickly when I dropped him a request for the new files. So please try out this CAB I've put together, and let me know if you still get message stuck over at your end.
I'm crossing my finger!
Download link
{
"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"
}
MOD EDIT: tnyynt: Guess HTC head you! http://www.htc.com/europe/SupportViewNews.aspx?dl_id=812&news_id=407

Thanks zenkinz! You are my saviour! From Xperia to HTC Leo

theredundant said:
Thanks zenkinz! You are my saviour! From Xperia to HTC Leo
Click to expand...
Click to collapse
not so fast dude. We need to monitor for awhile to see if the new version developed by HTC is indeed solving the problem. The best way to test is to go underground or into lift and see if you can send messages or not

checking it right now

just tried to install( to device), looks like its done and then i get a
"installation was unsuccessful. the programe or setting cannot be installed because it does not have sufficicient system permissions"
help?

jaoropez said:
just tried to install( to device), looks like its done and then i get a
"installation was unsuccessful. the programe or setting cannot be installed because it does not have sufficicient system permissions"
help?
Click to expand...
Click to collapse
Maybe you should try this:
1. Turn the HTC Sence off
2. Reset
3. Install patch
4. reset
5. Turn the HTC Sense on.

jaoropez said:
just tried to install( to device), looks like its done and then i get a
"installation was unsuccessful. the programe or setting cannot be installed because it does not have sufficicient system permissions"
help?
Click to expand...
Click to collapse
see if you can install after applying the tweak "Policies/Allow unsigned apps" using BSB tweaks app.
Btw, I made a test just now. I changed my SMS preferred setting to 3G (not via Advanced network, but instead HKLM\Software\Jataya\Messaging\SMSPreferredNetwork) and put my phone in a metallic enclosure so that I've no network totally. Then I send out a message to myself and I don't get any delivery report nor the message itself.
After about 10s, I brought the phone out, and then in less than few sec, I got both delivery report and message. So it looks like it's working well, but all these count for nothing if somebody reports otherwise. So your feedback after installing the cab is very much appreciated here.

Just installed on 2 decides, will test for a few days and report my feedback

fix, no functional

Not directly related to this problem but always something regarding HTC Messaging, I've sent an email to HTC asking to fix the long waiting time it takes to load all of your SMS within a contact. It could possibly be one of the following fixes:
- stop updating the list, add all the sms to the control, then re-enable the control: should work reasonably well, since opening a menu while htc messaging is loading sms forces this behavior - Instead of waiting for a minute while loading 300+ sms, you only need to wait 1-2 sec. - Nice improvement, still not solves the problem
- just load 10-20 messages, then put a button to show more.. problem solved.
They replied me telling they've sent the request to the "relevant department".

Not working for me, sorry

oops wrong thread, sorry.

zenkinz said:
see if you can install after applying the tweak "Policies/Allow unsigned apps" using BSB tweaks app.
Btw, I made a test just now. I changed my SMS preferred setting to 3G (not via Advanced network, but instead HKLM\Software\Jataya\Messaging\SMSPreferredNetwork) and put my phone in a metallic enclosure so that I've no network totally. Then I send out a message to myself and I don't get any delivery report nor the message itself.
After about 10s, I brought the phone out, and then in less than few sec, I got both delivery report and message. So it looks like it's working well, but all these count for nothing if somebody reports otherwise. So your feedback after installing the cab is very much appreciated here.
Click to expand...
Click to collapse
Intallsed BSB tweaks, applied tweak, sucess! able to install.
do i need to change the SMS prefered setting to 3G?
I havent changed any SMS preferered setting ( still default, GSM prefered?)
anyways, was able to send 2 texts just now, both received by reciepient a second after send. So far so good
Sent 5 more, waiting for replies. nothing in my outbox
so far, so good

jaoropez said:
Intallsed BSB tweaks, applied tweak, sucess! able to install.
do i need to change the SMS prefered setting to 3G?
I havent changed any SMS preferered setting ( still default, GSM prefered?)
anyways, was able to send 2 texts just now, both received by reciepient a second after send. So far so good
Sent 5 more, waiting for replies. nothing in my outbox
so far, so good
Click to expand...
Click to collapse
no need, just stick to whatever setting you have. The whole idea is supposed to work regardless of whether you have chosen GSM or WCDMA as your preferred network. Hope it works

ijob said:
Not working for me, sorry
Click to expand...
Click to collapse
can you explain why it doesn't work? you still have stucked messages, or you can't install the fix?

Its working now, got replies from all people verifying receipt of SMS, but anything else i could to "strain" the phone into failing to send an SMS?

Okay,
I installed the cab no probs, then reset my sms options back to GSM prefered [default], soft reset, sent a message, that didnt arrive.
Turned the options back to GSM only, removed the cab, soft reset, sent a message and it was sent along with the one I tried to send after first installing the cab.
Hope this helps..

try killing jblend daemon and the corresponding sms inbox handler in the reg

at least i finally know i am not the only one suffering from this problem.... almost thought i got a faulty set. thanks for the patch bro!

after sending 7 sms, just tried sending an sms now ( 3 hours after initial sucess) and its stuck in my outbox...again!!!
success might juts have been luck, i havent send an sms in 1 week, and did 3 soft resets, 1 after installl bsb tweaks, one after installed SMS fix cab, and 1 more for good luck.

[BIG FAQ] Nexus S General [Start Here before Clicking New Thread!] ** OUTDATED **

EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.​
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
Because people seem to be incapable of using the wonderful "Search" function built into these forums, I'm putting together a list of questions that keep popping up in new threads every other day.
Q: How's the Battery Life?
Officially, the Nexus S is rated for 6hrs of talk time and 427 of standby time. How much battery life you get will entirely depend on what you use the device for and how much. On my first real non-vacation day, my Nexus S lasted a little over 16hrs on one charge through what I would consider heavy usage (flashing roms/backups, emails, texting, web browsing, long phone calls, etc). Your mileage may vary. Fellow poster @Luxferro managed to get 2days, 14hrs, and 13minutes out of his phone on a single battery charge. Discussed here: http://forum.xda-developers.com/showthread.php?t=875809
Q: Does your GPS work?
Most people have reported their GPS to be functioning just fine, though there have been quite a bit of variation on lock times.
Q: Will this work on AT&T?
Yes, but you will not get 3G service. This is due to the different frequencies that T-Mobile and AT&T's 3G runs on.
Q: But it says it supports GSM band 850mhz!
GSM is 2G. UMTS is 3G.
Q: But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...
Stop it. It is likely that Google will release a version of the Nexus S with support for AT&T's 3G some months down the road, just like they did with the Nexus One but for right now, if you want 3G service, T-Mobile is the only way to go.
Q: Is tethering free?
So after having the phone for a bit of time now and tethering unimpended, I'm going to have to agree with @nxt that T-Mobile is not charging for or redirecting for tethering on this device. At least, for now. However, like in the original version of this answer, T-Mobile did announce that they were going to be charging for tethering but I've tethered every day for various amounts of time (including torrenting nearly a gig to my netbook) without so much as a hiccup. Source: http://bit.ly/d1NS9o
Q: Will TZones/Web2go/grandfathered web program work on this phone?
No, or at least, it doesn't appear to anymore due to T-Mobile locking down the IMEIs. When the phone was first released, people were reporting that it worked fine, then after a few days it became sporadic, before finally not functioning at all. See the discussion here for more information: http://forum.xda-developers.com/showthread.php?t=864843
Q: I unplugged my phone, and my battery dropped from 100% to 95% immediately, or it won't/takes along time to charge past 99%, what gives?
This is by design. Your phone will slow down and eventually stop pulling charge at or slightly greater than ~95% regardless of what your battery indicator says. This is to extend the overall life of the battery, as constant 100% to 0% charge/discharge cycles will cause it to fail prematurely. If you're interested in really pushing it to 100%, you can use a technique that is called "bump charging" and is better detailed here: http://bit.ly/f6xiZ0
Q: When I reboot my phone while it's charging, the battery jumps from X% to Y%, what gives?
I'm honestly not sure what causes this, but sometimes Android/Gingerbread gets confused on how much exact charge is in your battery if you reboot it while it's charging. However, from personal observation, it's just a display issue. Android/GB will eventually start showing the correct percentages once the battery has "caught up" with what it thinks it is at. Also wiping the battery stats(root only) seems to help alleviate this issue. Either way, it's not a large concern.
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Follow the root guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Q: Linpack/Quadrant Scores?
Linpack doesn't play very nicely with the Galaxy S lineup generating very low numbers in comparison to HTC devices. This is because the processors that are powering these devices operate in different ways. Does this mean the Nexus S processors are slower? Not really, just different. As for Quadrant, it doesn't currently work very well with Gingerbread and needs to be updated. The scores folks have been seeing though put it in the 1600 range without a modified kernel.
Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices(minus the Epic 4G on Sprint) thus far, there is no LED indicator light. There are apps, such as NoLED, on the marketplace which work great on the Nexus S and provide more or less the same functionality. There's another app called BLN which will blink the capacitive touch keys to let you know you have a notification, but it requires a custom kernel to support it. Those two circles are the Proximity Sensor and Ambient Light sensor.
Q: I can't zoom in and out on the camera app!
Correct, the digital zoom feature seems to be missing.
Q: Can the Nexus S do 720p?
No, at least, not right now and not on the stock ROM. It is possible that eventually our wonderful developer community will come up with a software hack for custom ROMs to allow 720p video recording, but at a reduced framerate than if it had a true 720p chip similiar to what they did with the Nexus One. Until then, the answer is no.
Q: But that one guy in Italy says the Italian version can do 720p recording!
No, he says that it can do 720x480 which isn't the same thing. The 720p "name" comes from the last numbers in the resolution, so in this case, it would be 1280x720(which the other Galaxy S phones are rated to shoot at).
Q: How do I video chat?
Google, unfortunately, did not develop a native app to support video chat and so we must rely on some from the marketplace. Right now, as far as I'm aware, Tango is the only one that has been updated to support video chatting on the Nexus S.
Q: My toys are better than your toys! Hahahaha!
Stop it and grow up. Different strokes for different folks. People spend their money on what they want to spend it on regardless of your agreement on their choice. Not to mention that this kind of behavior goes against the spirit of this community.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Q: Clockworkmod says I'm not set up for OTAs! What gives?
That's not for official OTA updates from Google. Some custom ROM developers set up their roms to receive custom OTA updates or at least notifications of said update specifically for that ROM.
Q: Why have my Wifi/3G/Signal bars switched from green to white?
A green set of bars typically means that you are connected to and syncing with the Google Account servers. White means that this is not happening for whatever reason, usually something like a bad signal or low coverage area. Also the WiFi connection is set by default to turn itself off(aka sleep mode) when the screen is off, this can be adjusted under Settings > Wireless & Networks > Wi-Fi Settings > Menu Key > Advanced > Wi-Fi Sleep Policy. Don't panic, though, it's nothing too major.
(Suggested by mmas0n, thanks!)
Q: How do I restore the stock recovery?
Right now, it is NOT possible to flash the stock recovery over Clockwork Recovery at all. The only way to restore it is by NAND restoring the Stock 2.3.1 backup in the development section.
Q: Does the Nexus S have Gorilla Glass?
No, it does not. Take care of your device.
Q: The Nexus S only gets 3G? Omg, I only see a 3G icon!
The Nexus S gets UMTS and HSDPA, which are both technically 3G. Your phone idles on UMTS 3G, and when it starts downloading/uploading, it'll flip to HSDPA after a few moments. You can see this by typing *#*#4636#*#* into your Dialer, going to Phone Info, and looking at Network Type while downloading something. The ability to switch the icons on the notification bar is something that was added in custom ROMS, and is not supported by the stock ROM. Furthermore, the icon is not always an indicator of what kind of data connection you have. If I were so inclined(and I'm not) and/or had the technical skills(which I don't) to modify the framework, I could make it say OVER9000g when connected to anything. Rest assured, if you are on a network that uses the 3G bands the Nexus S supports, then you are recieving HSDPA regardless of what icon you see.
As suggested by Gogol(thanks!), now adding a...
Possible Known Issues(Reported by some users but not all):
Lag in the Web Browser
Back button is not responsive or doesn't light up
Pink / white / yellow tint on the screen
Weak WiFi signal
Weak cell signal (not necessarily specific to the Nexus S; T-Mobile's frequencies typically have bad building penetration)
Some apps running wild consuming battery
Missing apps in market (until Google updates to recognize 2.3.1 buildprint)
Accelerometer becomes "locked" after using Google Sky Maps requiring a reboot to free
Ringtones changing on their own following reboot/USB plugin (Push the .mp3 to /system/media/audio/ringtones to stop this *requires rooting*)
Stock launcher has home screen/scrolling lag issues (not present on market launchers like ADW/LauncherPro)
Home screen icons on stock launcher randomly disappear, disappear after move, or show up in folders they weren't moved to. (not present on market launchers like ADW/LauncherPro)
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.​

Sti-cky! Sti-cky! Sti-cky!
Thanks for taking the time to make this list. Should be the first thing newbies read when they join the forum

Stuck due to the usefulness of this thread

Great FAQ thread man. Thanks a lot.
And lol @
But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...

Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....

Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices thus far, there is no LED indicator light.
Click to expand...
Click to collapse
Actually not true, the Galaxy S Epic 4G does have a LED notification light.

Q: Is tethering free?
No, tethering is not free. T-Mobile charges for this service. That being said, people have and still do tether without paying for the service with little to no consequence. T-Mobile seems to track the User Agent of the browser you're using on their network, and it is possible to mimic the Android browser's user agent on a desktop PC and tether undetected. In the event that T-Mobile discovers you tethering, you will receive a text message and all internet traffic on their network that doesn't contain the Android UA string will be redirected to an official T-Mobile site encouraging you to sign up for their tethering service.
Click to expand...
Click to collapse
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.

jblparisi said:
Actually not true, the Galaxy S Epic 4G does have a LED notification light.
Click to expand...
Click to collapse
Thanks! This has been corrected.
nxt said:
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.
Click to expand...
Click to collapse
Negative. As of 11/03, T-Mobile has begun charging for this service.
Source: http://www.tmonews.com/2010/10/t-mobile-launching-14-99-tethering-plan-november-3rd/
Android 2.2 introduced the ability to hotspot tether regardless of a paid service on nearly any device(and before that, this was available through some market apps). I believe some have had this ability "disabled," in the sense that it doesn't show up in the Wireless & Networks menu(such as the G2, though this was corrected in an update) but through apps such as AnyCut you can still activate the service and tether.
So, once more, you CAN tether without paying for it, however, T-Mobile may start redirecting your web traffic that doesn't contain the Android UA string to their website. They've been super inconsistent in their enforcement (a good thing, if you ask me!).
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
gogol said:
Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....
Click to expand...
Click to collapse
Thats a great idea, I'll definitely start try to start collecting known issues.

Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence

Paparasee said:
Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence
Click to expand...
Click to collapse
Updated to include links to two threads in the development section which should get you on your way.
The first one will help you setup ADB and the relevant drivers needed to input commands to the phone from your PC. The second is the actual rooting method and custom recovery installation.

unremarked said:
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
Click to expand...
Click to collapse
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.

nxt said:
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.
Click to expand...
Click to collapse
I'm well aware of which forum I am in and which phone I have.
The option was removed in the G2 and added back in via OTA update, it was also there on the MT4G at launch. I'll admit even setting my device to to show as one of those still does not pull up that option under services. I'm willing to believe that perhaps T-Mobile announced their intention to charge for the service then decided not to.
However, just to point out, the Nexus S/Nexus One are not special phones(as far as T-Mobile are concerned) on T-Mobile's network and thus entitled to special privileges. They are subject to the same rules and regulations as any other phone. In any which case, I'm going to make an adjustment to that section to note the ambiguity.

Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?

PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
Not really. Every device has it's bugs and issues at release, the Nexus One included. Touch screen wigging out randomly, capacitive buttons misaligned, the relatively easy "death grip," and just generally (at least for me) weak 3G connection. My favorite was when the Nexus One wouldn't send or receive any text messages or phone calls.
We should also keep in mind that Gingerbread itself is brand new as well.

unremarked said:
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Click to expand...
Click to collapse
regarding this...
we might see some ports over in due time.
they guys over at SGS are already in the process of porting the SenseUI
once they are done with that feast, it'll be a lot more doable to bring it to Nexus S
http://forum.xda-developers.com/showthread.php?t=788866
and
{
"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"
}
http://forum.xda-developers.com/showthread.php?t=827745 Alpha ready for testing!

Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.

mmas0n said:
Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.
Click to expand...
Click to collapse
Done so! Thanks for the suggestion.

PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
its just the high expectations, the NS wasnt a game changer like the N1 was

After the update I can't download anything from the marketplace. Anybody else have this problem?

katana24 said:
After the update I can't download anything from the marketplace. Anybody else have this problem?
Click to expand...
Click to collapse
Can't say that I have. Are you talking about missing apps, or are you getting some kind of error message?

[APP][4+] SkipLock Beta - Skip the lock screen (Formerly Unlock With WiFi) 4/17

The app is now live on Google Play.
Thanks to all my beta testers for helping me iron out the wrinkles. I will still post beta versions here when I have new features that need testing.
{
"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"
}
Tired of entering your password all the time? SkipLock lets you skip past the lock screen when you're connected to a designated wifi or bluetooth device. When you're at home or in your car, your phone is safe and you don't need to be typing in that damn password all the time. When you're connected to your wifi network, or any bluetooth device, you can go straight to the home screen when you press the power button. You can even have it keep the phone unlocked while you're connected to a bluetooth keychain or headset. As soon as the phone gets out of range, it locks.
This is a public beta. SkipLock is a complete rewrite of Unlock With WiFi. Why rewrite it? This blog post explains the reasoning behind it.
Here are the new features in SkipLock:
Pattern and face unlock supported on rooted devices
Completely redesigned Android 4+ user interface
No background service = less memory usage and more reliable
No status bar icon required (but it’s still an option). Tray-only notifications also an option.
If you have notifications enabled, you can now tap the notification to instantly lock the device
Even more cool stuff coming later
Many of the existing features from Unlock With WiFi will also be in the new app. Some of them are:
Automatically turn off wifi when leaving home
Automatically turn on/off bluetooth
Automatically turn on/off sync
WidgetLocker integration
Lock delay has been removed because Android 4+ supports it natively now
If you have a bug to report, press Bug Report in the app's menu. This will send me some diagnostic information that will help me figure out what's wrong. This is the quickest way to get a response. You may post more general questions in this thread, and I will try to answer them, but bug reports sent directly to me take precedence.
SkipLock requires Android 4.0 or above. Root is required for patterns and face unlock. Only PINs and passwords are supported without root.

SkipLock FAQ
The FAQ is now being maintained on my website.

Crashes on startup on CM 10.2 M1 on HTC One

MajorGaz said:
Crashes on startup on CM 10.2 M1 on HTC One
Click to expand...
Click to collapse
sorry about that! it is the first release of the beta, so please bear with me. can you email me the log file? it's at /sdcard/SkipLock.log. send it to support at benhirashima dot you know what.

Crashes
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]

Bionic22 said:
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]
Click to expand...
Click to collapse
sorry, corrupted apk file! i just uploaded a new one that works.

Ben74 said:
sorry, corrupted apk file! i just uploaded a new one that works.
Click to expand...
Click to collapse
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.

D3_ said:
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.
Click to expand...
Click to collapse
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.

Ben74 said:
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.
Click to expand...
Click to collapse
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.

D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
hmm, that's interesting. maybe i'll look into it when i get a chance.

Installs now.
Will give it a whack when i get home

It works!
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.

Bionic22 said:
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.
Click to expand...
Click to collapse
great! thanks for the feedback. try to test it with bluetooth too, if you can.

Also work on my SGS3 Omega v51 4.3
sent from my amazing SGS3 via Tapatalk

Is this time limited?

I don't know how you did it, but this works on stock rooted HTC One with pattern lock! Your previous app and some other apps do not, but this one works perfectly! When does this beta expire?
Take my money!
Side note: does not work on nexus7 with CM 10.2 (4.3) pattern always shows even when skiplock notification says its unlocked. Going to submit report from app
Thanks for this! I have missed this function since using HTC One. And will use this on my Nexus 5 when it arrives too

D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
Yes, the S3 supports nfc from the lockscreen on some ROMs

My Feedback
Thank you for this great little software. You can also achieve this with software like lama or tasker. But I dont need such big toolkits. So your app fits perfectly on my device.
Here are my thoughts:
* starting an app when a network is in reach - great for car-users to start their favorite mp3-player etc.
* simple geofencing to re enable wifi/bluetooth
* turning on/off different system profiles (so you dont have to take care of all settings...it´s all build into the os)
Keep on coding!

working great on note 2 4.3 keep it up bro!

thanks for the feedback, guys. good to hear it's working! for those who asked, yes it's time limited. the current version will expire at the end of november, but if i feel that more testing is necessary, i will update the app and extend the time limit.

Viber battery drain after A13 upgrade

Hi there,
I need some help or advice. I have upgrade to A13 some days ago and apart from the crazy battery drain with "Phone Idle" and "Mobile Networks" I am facing a weird Viber drain which never occured before :
Shows and 20-30% battery consumation with 15-25 hours "alive" and only 2-3 minutes in background.
Ofcourse this is nonsense the real usage is the 2-3 minutes and not the 15-25 hours
I have wiped cache , and done a uninstall re-install but nothing happens.
Viber is the no.1 battery consumer in the app list.
Any advice,guys?
I am already very disappointed with the A13 drain with "Phone Idle" and now this Viber issue comes up Heeeeelp !

Why are you reporting a viber bug here?

ibanezman192 said:
Why are you reporting a viber bug here?
Click to expand...
Click to collapse
He's reporting it here because its a13 problem on our device not vibers.i have p6p and i have the same bug. does anybody have a solution?

This does not have anything to do with the P6.
It is an app issue and needs to be reported to the developer of the app.

Exactly. It's a well known problem with the latest version of Viber across many devices. So stop spamming irrelevant stuff to Pixel 6, or else.

ibanezman192 said:
Exactly. It's a well known problem with the latest version of Viber across many devices. So stop spamming irrelevant stuff to Pixel 6, or else.
Click to expand...
Click to collapse
How come it only showed up after A13 uprade? On A12 Viber was normal, with A13 its a mess with massive drain
You cant be serious this is not A13 related.....

blaze73 said:
How come it only showed up after A13 uprade? On A12 Viber was normal, with A13 its a mess with massive drain
You cant be serious this is not A13 related.....
Click to expand...
Click to collapse
Because Viber app is maybe not updated to support A13.
Several apps need an update to work under A13.
In my case, DJI Mimo needed an update to v1.7.26, after that it started correctly.
Cheers
Tom

tom1807 said:
Because Viber app is maybe not updated to support A13.
Several apps need an update to work under A13.
In my case, DJI Mimo needed an update to v1.7.26, after that it started correctly.
Cheers
Tom
Click to expand...
Click to collapse
I see this is a bummer. However I feel that this is more like a Google issue not Viber's fault but we will see. My battery life
is tragic, worst ever in my 10+ years smart phone usage...

Looks like your feeling is not shared with the moderators, it was moved to general.
Beside that, maybe check Google whether others reported the same problem and maybe offer workarounds.
Cheers

tom1807 said:
Looks like your feeling is not shared with the moderators, it was moved to general.
Beside that, maybe check Google whether others reported the same problem and maybe offer workarounds.
Cheers
Click to expand...
Click to collapse
I tried to check but could not find any workaround so far and this is very annoying that it is the main consumer. (APP)
Top drainer it is, next to "Phone Idle" I have been trying to find a workaround but none so far or I have been bad with searching...

blaze73 said:
I tried to check but could not find any workaround so far and this is very annoying that it is the main consumer. (APP)
Top drainer it is, next to "Phone Idle" I have been trying to find a workaround but none so far or I have been bad with searching...
Click to expand...
Click to collapse
Look into this topic, the section "RECOMMENDED AFTER UPDATE". The first 3 items could help, but you should be familiar with "platform-sdk-tools" and ADB commands (also how to open a command prompt in Windows).
Cheers
Tom

tom1807 said:
Look into this topic, the section "RECOMMENDED AFTER UPDATE". The first 3 items could help, but you should be familiar with "platform-sdk-tools" and ADB commands (also how to open a command prompt in Windows).
Cheers
Tom
Click to expand...
Click to collapse
I did some of the settings and no, I am not familar with "platform-sdk-tools" and ADB commands.
I am a regular user not a tweaker. Unfortunately nothing has changed. Phone ide is 35% in 8 hours in flight mode
and Viber is still top consumer APP Insane ! I am really fed up with this A13. Battery cant even last 24 hours
using flight mode for the night. : (
{
"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"
}

Maybe you should explain what you did?
Cheers

tom1807 said:
Maybe you should explain what you did?
Cheers
Click to expand...
Click to collapse
The recommended "DISABLE" bits and parts. Did not really help. Still heavy battery drain and Viber is no.1 consumer APP-wise otherwise its "Phone Idle" 30-35%

No, I specifically said the 3 commands written in "RECOMMENDED AFTER UPDATE". The others may help, but not for ur problem.
One command specifically deals wit re-compiling all the apps which could help with overheating and battery drain.
The other one deals with battery drain.
"Disable" bit and parts could cripple your phone if you don't know what they exactly do.
And don't focus on how much 30-35% for Phone idle writes.
If your phone used for example 10% battery, the 30% of these 10% were drained, but not 30% of the battery.
Cheers

tom1807 said:
No, I specifically said the 3 commands written in "RECOMMENDED AFTER UPDATE". The others may help, but not for ur problem.
One command specifically deals wit re-compiling all the apps which could help with overheating and battery drain.
The other one deals with battery drain.
"Disable" bit and parts could cripple your phone if you don't know what they exactly do.
And don't focus on how much 30-35% for Phone idle writes.
If your phone used for example 10% battery, the 30% of these 10% were drained, but not 30% of the battery.
Cheers
Click to expand...
Click to collapse
Alright. Can you tell me what to do and how to do with these 3 commands? I will perform but I would need some step-by-step help if possible

Enable USB debugging on your mobile. Download the platform-sdk-tools and unzip to a directory.
Connect your mobile to a PC, and open a command prompt.
Type adb devices, authorize the connection on the mobile and then type the commands.
All this can be easily found, here on XDA and internet.
Cheers

tom1807 said:
Enable USB debugging on your mobile. Download the platform-sdk-tools and unzip to a directory.
Connect your mobile to a PC, and open a command prompt.
Type adb devices, authorize the connection on the mobile and then type the commands.
All this can be easily found, here on XDA and internet.
Cheers
Click to expand...
Click to collapse
Great. Many thanks, man. I will wait for the september patch if nothing happens I will do these steps.
Viber is still no.1. consumer staying on top with 25% consumation with bogus data
Phone Idle is 35% with 18-20hours standby which is insane. This A13 update was a catastrophe in terms of battery life

Google won't fix Viber. That's a Viber problem.
So far Viber is developed up to API 30, Android 13 is API 33.
Cheers

tom1807 said:
Google won't fix Viber. That's a Viber problem.
So far Viber is developed up to API 30, Android 13 is API 33.
Cheers
Click to expand...
Click to collapse
Good to know that. (API 33) I have sent a report , trouble ticket to Viber support.
Hope it will be dealt with.

Question Cracking/squealing between phone call

Hi.
Today I ported all my things from P5 to P7Pro and I noticed a very annoying thing.
In every call, after a minute or two there beggins cracking/squealing, like it's a bad connection.
I updated the phone to the latest Android version (screen in att). I tried restarting, with another SIM but the same ...
No problem at all on my P5.
Anyone else facing that?
I'm really disappointed that this disables the basic use of the phone and I don't even know how to start reporting a bug considering I'm using the phone in an unsupported country. :/
{
"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"
}
Thanks for your help.

Strange one, not something I have nor read anyone else having. I'd suggest you have a faulty handset if you have tried another sim from another sim in it (presumably from another provider).

Beefheart said:
Strange one, not something I have nor read anyone else having. I'd suggest you have a faulty handset if you have tried another sim from another sim in it (presumably from another provider).
Click to expand...
Click to collapse
Yes, another SIM from another provider.
Yes, strange one. I did not found anything similar anywhere ...

akulp said:
Yes, another SIM from another provider.
Yes, strange one. I did not found anything similar anywhere ...
Click to expand...
Click to collapse
Do you have clear calling enabled? Not sure if it would make a difference, but I did see one or two people report that their connection was worse with it, although for most I think it's better. Not sure they reported crackling/squealing though.

Lughnasadh said:
Do you have clear calling enabled? Not sure if it would make a difference, but I did see one or two people report that their connection was worse with it, although for most I think it's better. Not sure they reported crackling/squealing though.
Click to expand...
Click to collapse
I read about CC, but in my version there is no such option for now. Waiting for upgrade ...

Hello I have the same issue with Italian PosteMobile.
Where are you from?
It starts after 5 or 6 minutes in call.
Same phone but with other operator I have no problems.
Is your operator a virtual one? Full MNVO?

giobik said:
Hello I have the same issue with Italian PosteMobile.
Where are you from?
It starts after 5 or 6 minutes in call.
Same phone but with other operator I have no problems.
Is your operator a virtual one? Full MNVO?
Click to expand...
Click to collapse
Hi!
Not so great for you and me, but great that I'm not the only one.
I'm from Slovenia.
Hm, strange, so something with operators u think? I'm on Telekom Slovenia, so biggest national operator ...

Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!

giobik said:
Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!
Click to expand...
Click to collapse
Great, thank you!

giobik said:
Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!
Click to expand...
Click to collapse
Hm, today I had zero issues up to now.
Yesterday in the evening I took out my primary SIM card, cleaned SIM slot with air pressure ...
I keep fingers crossed!

Same issue here but I only get it after exactly 20 minutes of calling. I'm using kpn Netherlands with a esim . I migrated from pixel 5 also with esim on same provider. I must note that after I disabled 2g calling from the settings that not all calls have the issue anymore.

Same problem here in Portugal after 15m in a call.

I must say that now after testing a couple of days with the 2g slider turned off, 90+% of the calls go without big audio issues. Only sometimes 1-5 seconds long distortion of some kind is left

Hello, problem still present after many updates and now on last beta.
Probably most of you solved it by switching to another operator, but I can't.
I opened an issue in Android Bug Report and discovered through logcat that there are some duplicate received frames.
If you suffer from the same issue I kindly ask you to post in this official issue link to let Android developers know that I'm not the only one with this problem!
Google Issue Tracker
issuetracker.google.com
Take a look to my answer number 6 to see the logcat :
On a Windows PowerShell:
adb logcat | find "F1:ERR"
Google Issue Tracker
issuetracker.google.com
If the problem remains unsolved I will sell my Pixel 7Pro, I can't work with this issue (and cannot change operator as it is the professional on that gave me my employer).
Thank you!

Same problem here

Hello, as of today nothing changed, just updated on beta 13 (T2B2.221216.008)
Annoying...

Same problem here!
After about 8 minutes of calling with Postemobile operator (Italy), the call starts croaking! More and more often I receive text messages from people who have looked for me, despite the fact that the phone was always under excellent signal. Postemobile still has VoLTE not enabled on Pixel7.

sbellisario said:
Same problem here!
After about 8 minutes of calling with Postemobile operator (Italy), the call starts croaking! More and more often I receive text messages from people who have looked for me, despite the fact that the phone was always under excellent signal. Postemobile still has VoLTE not enabled on Pixel7.
Click to expand...
Click to collapse
Please, write a comment in this Bug Issue Tracker to let know Google we have this horrible problem.
Also click the +1 on top to increment the counter!
Google Issue Tracker
issuetracker.google.com

giobik said:
Please, write a comment in this Bug Issue Tracker to let know Google we have this horrible problem.
Also click the +1 on top to increment the counter!
Google Issue Tracker
issuetracker.google.com
Click to expand...
Click to collapse
done