PebbleOS Firmware Release Note - Pebble

Lastest version : Pebble Changelog
Pebble Firmware 2.4 (Release Notes)
Fix a potential crash when using scroll layers or animations
Added support for realloc
Added a gbitmap_create_blank function to create empty bitmaps of a fixed size
Added number_window_get_window()
Fixed a crash with atan2_lookup when high input values were used
Fixed a bug where TupletInteger could not be used with unsigned integers
Fixed several bluetooth reliability issues
Fixed a case where the "Setup notifications" banner would erroneously show in the iOS Pebble app
Fixed a bug with the music app where media playing faster than real time could not be paused
Fixed a bug where the notifications view could show a rapidly increasing counter for number of notifications when first displayed
Fixed a bug where switching watchfaces could cause the same watchface to be relaunched
Pebble Firmware 2.3 (Release Notes)
Improved Bluetooth LE connectivity.
Added the ability to skip to the next notification with a double-click of the Down or Up buttons.
Bug fixes and stability improvements.
v.1.14.1 - Date: 11 Dec 2013
What's New
New "Do Not Disturb" feature: schedule the times you do not want to be disturbed by notifications.
Updated "Alarms" app: create multiple alarms, toggle alarms on/off and edit them.
New "Snooze Alarm" feature, customizable via the Alarms app.
Finer control over what notifications are displayed: Notifications On, Phone Calls Only or Notifications Off.
Notification settings are now accessible more quickly through a dedicated menu in the Settings app.
iOS 7 notifications now arrive more quickly on Pebble.
Bug Fixes
Fixes an issue where the Pebble may enter "recovery mode" immediately after updating to 1.13 software.
Fixes an issue affecting some iOS customers where the Bluetooth connection would be dropped after a few seconds.
Fixes a problem where phone calls would not get displayed any more after having received a missed call.
Fixes issues where Bluetooth transport would become unreliable (particularly during a firmware update).
Sometimes the Pebble would keep on vibrating after dismissing a phone call. This has been resolved.
After exiting Airplane Mode, the Pebble will now immediately attempt to reconnect to iOS devices, instead of waiting a minute first.
Click to expand...
Click to collapse
v.1.13.0 - Date: 11 Nov 2013
What's New
Adds support for Apple Notification Center Service (ANCS) notifications for iOS 7 users with iPhone 4S, iPad 3, iPad mini or iPod Touch 5 or greater (requires Pebble iOS app 1.3 or greater). See help.getpebble.com for more information on setting up iOS7 notifications. * The Pebble now can show >80 unread notifications, up from 8 previously. Bug Fixes ----------
Issues when receiving a phone call around not showing caller-ID, dismissing a call when pressing the back button, or continuing to vibrate, have been fixed.
New iOS users no longer need to manage access to their address book in order to see Caller ID on their Pebble.
Sometimes settings would be lost when the Pebble was rebooted. This issue is fixed.
Click to expand...
Click to collapse
v.1.12.1 - Date:16 July 2013
What's New
Bug Fixes
Fixed a problem that caused the phone app to disconnect immediately after a firmware update.
Click to expand...
Click to collapse
v.1.12 - Date:2 July 2013
What's New
The backlight now turns on momentarily when a charger is connected.
Lots of goodies for watchapp developers that will be unlocked when the new version of PebbleKit is released.
Bug Fixes
Fixed subject/sender cutoff in notifications with long subjects/senders.
Fixed motion backlight from sporadically not working.
Fixed factory reset to disable the QC app and perform the reset.
Fixed long click release after changing the action bar icon.
Fixed textlayergetmaxused_size to always return the right size.
Fixed graphics draw pixel, circle, round rect to draw inside the layer.
Fixed graphics draw rect, round rect to use the stroke color.
Fixed graphics GCompOpAnd bitmap compositing mode to not have artifacts.
Fixed graphics gpath filled to not have cuts.
Click to expand...
Click to collapse
v.1.11.1 - Date:1 June 2013
this minor update fixes bugs with Sports watchapps like Runkeeper and FreeCaddie.
Click to expand...
Click to collapse
v.1.11.0 - Date: 30 May 2013
What's New
Improved Notification UI
Allows multiple notifications to be viewed if they arrive within a short time frame
Improved Set Time UI
Added the option of showing your current speed (as oppossed to your pace) in the RunKeeper application.
Swapped next and previous track buttons in the music application.
Added the Simplicity watchface.
Removed the Fuzzy Time watchface (it is available through the watchapp library).
Bug Fixes
Fixed a few issues where the bluetooth module would consume too much power.
Fixed an issue where rounded rects drawn with graphics_fill_rect did not handle being clipped properly.
Sped up text rendering when some of the text layer is clipped off the screen.
Fixed a bug where the vibrating motor would get stuck on.
Fixed a crash when changing windows, most commonly seen in the set time and set alarm UIs.
Fixed an issue where SMS messages on iOS would be incorrectly shown as an email with a very long subject line.
Click to expand...
Click to collapse
Usefull links
Watch apps :
http://www.mypebblefaces.com/?date=desc
http://allpebble.com/index.asp
Source :
http://developer.getpebble.com/getting-started/index.html Preview of next firmware and next smartphone apps
https://forums.getpebble.com/discussions

It's (almost) Software Time!
Hi Pebblers!
It’s no secret that we’ve been hard at work developing better software for Pebble and this Wednesday, November 6th, we’ll be making a very important announcement.
You’re invited to join our livestream event at 10AM PST to hear what awesome new things we’ve been working on to make Pebble a more robust and feature-rich platform. To tune in, visit https://www.getpebble.com on Wednesday morning after 9AM PST to obtain a link for the livestream. After the live broadcast hosted by Eric and our very own Thomas, we will be leading a Reddit AMA discussion at noon (12PM PST) to answer any lingering questions you may have.
Still haven’t had a chance to try out the SDK? Download the SDK, check out the documentation, and get hacking!
Click to expand...
Click to collapse
Source : http://www.kickstarter.com/projects...per-watch-for-iphone-and-android/posts/651308

Any updates on V2?

slowfuse said:
Any updates on V2?
Click to expand...
Click to collapse
What update? V2 is officially out!

alex_herrero said:
What update? V2 is officially out!
Click to expand...
Click to collapse
...but there's no mention of it in this thread as of yet.
Sent from my Nexus 4 using Tapatalk

Don't really care if listed as "out" or not. I am running it.
The previous (now deleted) posts listed the change log for v1 revisions. That would be useful/interesting.

V2.0.2 firmware updated on my Pebble.
Sent from my Nexus 7 using Tapatalk

Version 2.1 updated on my pebble

2.2 is here. Music volume control + apps reordering.

Firmware 2.4 is here

2.4.1 has just been released
Sent from my C6903 using XDA Free mobile app

2.5 has just been released

DonDragonka said:
2.5 has just been released
Click to expand...
Click to collapse
Is 2.5 mostly just emoticons and compass or are there bug fixes and/or optimizations as well?
Sent from my SGH-I747M using XDA Free mobile app

There are definitely optimizations, like this: "Fixed a bug that would cause animations between windows to be slow.", but the best new feature (dismissing notifications) is sadly iOS8 only as of now. They promised to bring it to Android in the future.
Although not a feature or fix, but I love the new Domo watchface, the animations are funny and so smooth...

The Full 2.5 Changelog
Major Changes
FW 2.5 includes an optimized version of snprintf (and related functions like APP_LOG, etc) that does not support some length format specifiers previously supported (%hh, %ll, %j, %z, %t). The list of supported specifiers has been updated in the snprintf documentation. For those of you that use these previously-supported specifiers, please do not hesitate to contact us at [email protected] and we’d be happy to assist you with updating your code.
Added compass support.
Enforced versionLabel formatting in appinfo.json in preparation for app auto updates.
Added support for Pebble app relaunch on iOS when a Pebble watch is in proximity.
Added notification dismissal support on iOS8.
Added emoji support to Pebble notifications and system fonts.
Detailed List of Changes:
Changes for Firmware:
Added functions heap_bytes_free and heap_bytes_used to view current heap memory usage.
Added support for uuid_equal and uuid_to_string.
Added function accel_raw_data_service_subscribe to get accelerometer data with a single timestamp for all samples (significantly reduces memory usage for apps that do not depend on timestamps).
Added compass support.
Added emoji support to Pebble notifications and system fonts GOTHIC_24_BOLD, GOTHIC_18 and GOTHIC_18_BOLD.
Fixed a bug that would cause a crash if a screen shot was taken while one was already in progress.
Fixed an issue where Pebble APIs would use non-reentrant versions of standard C functions causing unexpected changes to return values.
Fixed a bug with accel_service that could result in memory being freed twice.
Fixed a bug where Golf API would show stale information on disconnect.
Fixed a bug that prevented calling menu_layer_set_selected_index before menu_layer_set_callbacks.
Fixed a bug which would sometimes cause the command line logging tool to crash when a watchapp crashed.
Fixed a bug that would cause the sample rate of the accelerometer to be reset when subscribing.
Added support for Pebble app relaunch on iOS when a Pebble watch is in proximity.
Added support for notification dismissal on iOS8.
Fixed numerous bluetooth reliability & connection issues.
Fixed a reset and other various bugs related to Data Logging.
Fixed a bug that allowed backing out of FW update screen.
Fixed a bug that would cause animations between windows to be slow.
Fixed a bug where the Date UI would allow selection of invalid dates.
Fixed a bug which would prevent the down button from scrolling through notification history.
Fixed a bug with AVRCP that could lead to a crash.
Set backlight to stay on during alarm ringing.
Changed the default backlight setting to AUTO.
Fixed a bug which would allow developers to ask for more than 25 accel samples per update.
Added check for NULL parameter in gpath_draw_filled.

The middle Button can not anymore be use to dissmiss Notifications. Have to use the single back Button. This was not in the previous fw.
Skickat från min GT-I9505 via Tapatalk

@ormetkruper: That's because that will dismiss the notification. This feature is already implemented with iOS8, we just have to wait till they make it work on Android too.

anyone on 2.6 for now ? Any feedback would be appreciated

My screen starting to tear now.not sure if it is because of this update.
Sent from my Nexus 7 using Tapatalk

2.6 is a very good update, I enjoy misfit app and compas gadget no problems at all using pebblebit firmware 2.6 try it yourself.
Sent from my Nexus 5 using XDA Free mobile app

Related

New Version Of Locale

You'll be happy to hear that we've just released Locale 0.3 beta this week. To install the update, simply:
1. Open the Android Market
2. Search for Locale
3. Tap on Locale
4. Tap on Install
The update resolves the PM-AM time boundary problem you ran into, as well as these other changes:
New Features
- Time Condition now supports day of week
- Network Setting now supports GPS
- Battery Condition now supports plugged-in and unplugged
- Contact Condition now supports accelerated scrolling
- Calendar Condition displays which calendar each event comes from
- Location Condition supports easier renaming and deletion of locations
- More thorough in-application help
Bug Fixes and Enhancements
- Better location detection
- Calendar Condition and Time Condition now detect changes immediately (previously it could take up to 10 minutes)
- Fixed a bug with Time Conditions spanning across the PM-AM boundary
- Fixed a bug where large locations couldn't be edited. Zoom controls now display even if a location fills the screen
- Notifications dismiss when leaving a situation
cool.
love the apps, keep them coming.
....cannot wait for cooking to start, but I think im not the only one...lol
just wondering.."Network Setting now supports GPS" means its posible to use locale features using gps only, without 3g location gethering?
Can anybode send me a link to the .apk oh this app for use on my HTC Tattoo, please?
THANK YOU
This is in the wrong forum; reported.

[APP]Touch InCall Screen Tweak v1.2.0 - Updated 3 Sep 09 - Battery Drain Fix

Welcome to the Touch InCall Screen Tweak thread. This app is a collaboration between 600GOL (of changeScreen fame) and Steve Pritchard (of the lesser StartTomTom fame).
Release notes are in the second post.
What does it do?
The purpose of the application is to switch on your screen during a call if you don't have it against your ear. This is useful if you need to enter digits for voicemail or telephone banking, etc. The screen will be switched off if the phone is against your ear (since v1.0.10 this will include as you a making a call, as well as during the call). From v1.0.11 if you put the phone face down, it will switch off the screen, and turn on the Speakerphone (from v1.0.19 this is now an option).
How does it work?
The application, once installed, doesn't actually run until you make or receive a call, so it won't impact normal performance of the phone. When you are in a call, the application runs, and monitors the orientation of the phone, and will switch the screen on if the phone has been in your hand for around half a second or so. If you put the screen against your ear, the screen will go off again. You can repeat this cycle as many times as you like.
So it doesn't use the light sensor then?
From v1.0.6 it DOES use the light sense to detect if it is against your ear. This is really a double check to back up the orientation. It doesn't use it to determine if it's away from your ear because the sensor doesn't seem to work when the screen is off, so it's of no use for switching the screen back on.
Will it work with my Phone?
This app is only compatible with Windows Mobile based HTC phones. It is developed and tested on a HTC Touch Pro, but should function on Touch Diamond and Touch HD models, although it looks as though non-TP models don't use their light sensors during a call, so Diamond and HD owners might want to disable the use of the sensor using the config app. It is not compatible with Android based phones, e.g. HTC Hero, or with Samsung phones, including the Omnia i900.
You can install the application from the attached cab file. You need to soft reset after installation for the application to work.
The second post in this thread will contain release information. Please resist the urge to tell everybody that you are downloading and trying the software by posting to this thread. By all means let us know if it works for you, along with what ROM you are using, and obviously let us know if you have any problems.
Cheers,
600GOL and Steve.
If you would like to consider making a donation, it is by no means necessary, but it is appreciated.
Many thanks to Hilaireg who has taken the time to provide a user manual, and Kitchen packages for TICST.
The files available for download:
- TICST Manual v1.1.3.pdf.zip - User Manual
- Touch_InCall_Screen_Tweak v1.2.0.CAB - Regular installation CAB
- Touch_InCall_Screen_Tweak v1.2.0 with UC.CAB - CAB for inclusion in UC startup installations
- Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Visual Kitchen OEM Package
- PACKAGE_Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Legacy Kitchen OEM Package
[size=+1]Release Notes[/size]
The logging option is provided for people who find they have problems with odd behaviour. The log file will be written to the Touch_InCall_Screen_Tweak.txt in the root of your device. It will get pretty big, pretty quick so if you make/receive lots of calls the best idea might be to switch it on for a short while, use the phone, make a copy of the log file to upload to this thread, and then switch it off if you are filling up your storage space.
3 Sep 2009 - v1.2.0 - Bugfix Update
- This version addresses a bug that has been around for a while, but has been difficult to track down. It appears that an early beta introduced an excessive battery drain for some users, and this has now been tracked down, and addressed.
6 Aug 2009 - v1.1.3 - Update
It's been a while, but this minor update has the following changes:
- Fixes a bug with the "switch off after Bluetooth" call function.
- Fixes a bug which caused the left soft key to be pressed at the end of a call.
- The "switch off for Bluetooth", and "switch off after Bluetooth" facilities (which switch the screen off during, and after a bluetooth headset based call respectively) are now applicable to wired headset calls too.
31 May 2009 - v1.1.2 - Update
This version includes an option to turn off the AutoDeviceLock during a call, as described in this post, for better compatibility with SPB Mobile Shell 3.
21 May 2009 - v1.1.1 - Update
This version fixes a bug with the "Ignore first screen off" function. This bug is most noticeable in the situation where the phone canvas/utility/whatever turns the screen off before TICST gets the chance to. This version has been tested with PhonEx from IconSoft, and works as long as you switch ON the screen off during conversation facility.
17 May 2009 - v1.1.0 - Update
This version provides a number of new features:
- It will allow the switching between APM and non-APM (Advanced Power Management) mode via the config application. Non-APM will give the better experience, but you may find that your battery runs down quicker in this mode. If the option is greyed out, then you are already running in Non-APM mode, and you can't change it.
- An option to prevent the auto-unlock has been added
- The option to switch the screen off after a Bluetooth call has been added.
- The "Show phone at screen on" option has been changed slightly in that it will attempt to activate the existing instance of cprog.exe, rather than spawning a new one. This will hopefully help some people who were having problems with different dialers - most people won't notice any difference.
- Minor logic alteration to try and prevent too much "flashing" of the screen in some circumstances.
16 Apr 2009 - v1.0.20 - Update
This version provides a couple of new features:
- If the screen is locked with the WM Lock when the app switches the screen on, it will attempt to automatically unlock it.
- The app goes into an override mode if the speakerphone is switched on manually, or if the call type is a video call. NB. This is not the same override mode as if the screen is switched on/off manually, and the override timeout isn't applicable.
8 Apr 2009 - v1.0.19 - Update
This version provides a number of new features:
- More configuration for the use of the Speakerphone. You can define whether putting the phone face down should switch it on, and what action, if any, the phone should take with the Speakerphone when you have it in your hand, i.e. switch it on, off, or take no action.
- The ability to show the phone canvas has an extra option of auto-pressing the left soft key, which should put it into dialpad mode.
- You can define a timeout, in minutes, for the override mode. This option hasn't been tested thoroughly, so feedback would be useful.
7 Apr 2009 - v1.0.18 - Update
This version adds the facility to force the phone canvas to be displayed when the screen switches on. This could be useful if you find that when the screen switches on, you are back at your Today screen.
6 Apr 2009 - v1.0.17 - Includes UC Friendly installer
This version adds the facility to always switch off the screen when you are taking a call via bluetooth.
There is also a UC Friendly installer which doesn't run the config app, or give the option to soft reset after installation. However, please be aware that you will still need to soft reset after the app is installed in order for TICST to function correctly.
2 Apr 2009 - v1.0.16 - AppToDate release
There is no change to the application itself, but the installation now supports AppToDate. Also, the config utility will now try and detect the phone type, and select suitable defaults with regard to ignoring the light sensor, and the first screen-off.
2 Apr 2009 - v1.0.15 (beta) - Consolidated Release
Another Minor release - this version handles sensors that give readings greater than expect more sympathetically. In the past, if a sensor produced a reading higher than expected, it could be misread. This has been corrected. The "Always On" feature has been added. This will keep your screen on all the time, regardless of orientation.
24 Mar 2009 - v1.0.14 (beta) - Consolidated Release
Minor release - this version fixes a bug which stopped the speakerphone from being switched back on. Polling frequency has been increased from 4 to 5 times per second.
21 Mar 2009 - v1.0.13 (beta) - Consolidated Release
Minor release - this version loosens the definition of "face down" for switching the speakerphone on. People having problems getting the speakerphone to come on, should try this version.
21 Mar 2009 - v1.0.12 (beta) - Consolidated Release
This release adds the option to switch the speakerphone off once you put the phone into the "in your hand" position, i.e. when the screen comes back on again. The option is "Switch speakerphone off" in the config utility.
Bug Fix - This version should no longer switch the screen off if making a data connection.
20 Mar 2009 - v1.0.11 (beta) - Consolidated Release
This release adds functionality to switch the screen off, and speakerphone on if you put the phone face down on a flat surface.
[Earlier version release notes have been removed due to post size]
Wow, thanks for the APP! Will have to try this one
Works Great!
Installed on Sprint TouchPro Stock ROM, works great.
maybe in future releases you can make a toggle switch or a small program to enable or disable it
thanks
I'll test when I get home from work.
Thanks
Installing right now.
Hi -- works great so far! Thanks for this, I know people have been asking for this for some time. I found it works best if you sort of "flick" the phone when you bring it down from your ear to turn the screen back on. It turns on very quickly and responds quite well. So far, in just a few minutes of testing, I really like it. Great job and thank you !!
installed..testing..
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Not working for me. Screen still turns off immediately using NATF's 4.2
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
Did you soft reset?
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
same here. screen stays off. i shake the **** out of the phone..nothing
aonavy said:
same here. screen stays off. i shake the **** out of the phone..nothing
Click to expand...
Click to collapse
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
bugsykoosh: I would guess he is using energyrom 2.0
aonavy said:
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
Click to expand...
Click to collapse
Edit: Just for the record I am using the same rom on my fuze and my screen still turns off during a call. I installed the cab to the main memory and rebooted when it wanted me to.
Goatmaster said:
bugsykoosh: I would guess he is using energyrom 2.0
Click to expand...
Click to collapse
aahhh- reading...interesting
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
It works! Just wasn't angling the phone right....It's still not perfect but it works
If I move the phone away from my head, it will flash on/off real quick sometimes, Also their is a bit of lag between the on/off function as well.
bugsykoosh said:
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Click to expand...
Click to collapse
I love your site! Excellent gossip site for us Fuzers!
bugsykoosh said:
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
Click to expand...
Click to collapse
its in my sig.
D3TH METAL said:
I love your site! Excellent gossip site for us Fuzers!
Click to expand...
Click to collapse
Thanks - it's like an AA meeting but instead you just get to come in and keep drinking

[User thread] MIUI v5 general discussion

The purpose of this thread is for discussion about best use of MIUI in general.
Which may or may not be related to MIUIv5 by rugglez.
It is recommended to try his rom first to see if you like it:
http://forum.xda-developers.com/showthread.php?t=2219511
For bugs about 3.5.3.
Issue: When you press and hold the home button, the multi task will flash up and then exist.
Solution: Setting-> button -> desktop key -> choose none.
I have already flash back to beta 2, but this should be the way to solve the issue.
For tips about 3.5.3.
- on the music icon, press and hold, then swipe up. You will see a pop-up music control
- there is a battery saving mode in setting >battery. I think this have something to do with tune down cpu freqz to from 1.2 to 1Gz.
Is there any battery drain or any other major downsites of this Rom?
Sent from my A2109A using Tapatalk HD
flopower1996 said:
Is there any battery drain or any other major downsites of this Rom?
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
1. Uses material stolen from pengus77 without permission
2. Battery drain is higher than any other rom for the o2x
3. Our phone's low amount of available ram in android 4.0+ can't handle resource hungry miui any more. May be smooth at first but apps take a lot of time to open, compared to other roms, and multitasking can't be handled well(mostly due to low ram, again)
Those are the problems in descending order of importance, (and coupled with my lack of time) why you aren't seeing newer versions being released by me
MIUI ROM 3.5.10 is released. Changelog
[Messaging]
Fix - In some cases when network becomes unavailable, it still sends as network message instead of a normal text
[Lock screen , status bar, notification bar]
Optimization - Improved the touch slide fluency of lockscreen
[Desktop]
Optimization - "Global search" thumbnail style in editing mode
[Camera]
Fix - When entering camera from contacts, front camera mirror image function does not work
Fix - When enabling camera from other programs, the preview and image of moving objects is inconsistent
[Gallery]
Optimization - Gallery blacklist
Fix - Unsorted picture can still be moved to the photo album
Fix - In some cases, thumbnails cannot be displayed
[Music]
Fix - Online music fails to load from cache or flash back in some cases
Fix - Clicking on desktop widget cannot enter music player
[Sound Recorder]
New - “Recording silent mode” switch
[Calendar]
Fix - In some cases the calendar view switch may cause selected date to change
[Notes]
Optimization - Notes reminds will display notification in status bar area
Fix - In some cases the notes renaming notes folder will lead to flash back
New - Slide down on Notes icon to create a new note
[Alarm clock]
New - When setting an alarm, remaining time before alarm is displayed
Optimization - System default alarm ring interface displays weather
Optimization - Adjust the alarm interface for Samsung I9100
[Xiaomi account]
Fix - In some cases Cloud service activation is unsuccessful
source
3.5.17 is now available from MIUI site.

[ROM][JB][4.2.2] Vanilla RootBox m7 Sprint *unofficial* [07.21.13]

{
"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"
}
Description
Vanilla RootBox is built straight from RootBox sources & Google Sources
and always carries a very light installation with no extra/useless apps.
This means, you can enjoy a pure Android experience combined with PA/AOKP/CM features and some cherry-picks.
Keep in mind Jelly Bean is only at the beginning stage of development and there will be minor bugs.
If you're wondering how this ROM differs from any other AOKP roms out there
Try it yourself and choose the one that meets your requirements
Recommended Install
Wipe Data/Factory Reset (This does not affect your Internal/External storage)
Wipe Dalvik Cache
Flash RootBox
Flash JB GAPPS
Wipe Dalvik Cache
Reboot
Credit/Thanks
Bajee
IOMonster *TheCubed*
The CyanogenMod Project
AOKP
Teamhacksung
Paranoid Android
DaXmax
Rodries
Pier
BigDenn
JankA4U - graphics / bootanimation
PonyExpress
Everyone else I forgot to mention
Open Source
Romanbb said:
All the heavy lifting is done over at https://github.com/htc-msm8960 - thank those guys,
they are working incredibly hard to bring AOSP to this device. I think the list of developers goes something like this:
h8rift, intervigil, toastcfh, deck, Flinny, Flemmard, Codeworkx, birdman. That means that any bugs that exist in other
AOSP builds will probablacy exist in these builds.
Click to expand...
Click to collapse
Downloads
| --> July.21-2013
- md5: 8b9ebf91330da07d58077b2fce95139c
Gapps
| --> Banks Gapps - HERE
| --> Recommended Gapps are banks minimal or multiDPI - then update whatever necessary on store. thanks
| --> gapps-4.2.2-jb-6.30.2013-signed.zip
Disclaimer / Warning!: I'm not responsible for any reason should you bork your phone
Donations
If you want to donate, feel free to do so otherwise don't forget to hit thanks and show your appreciation for all the hard work that goes into this.
RootBox Sources
My Github Sources
ScreenShots --- CLICK HERE - thanks Pony Express
Extras
Alternate Launcher - Xperia Launcher 2
Bug List
Let Me know thanks!
Rules
Coming Soon!
ChangeLogs
May.2013
May.21.2013 - Initial m7ul Release
May.23.2013
sync'd with sources
sync'd with cm's m7 sources
kernel testing
added faux sound - thanks faux - to be verified
more to come as progress picks up.. and i'll have a more detailed changelog..
May.24.2013
Add transparency settings for lockscreen
This will enable the user to set the transparency level
for the lockscreen.
FW: Ribbon v1.0 overhaul
Thickness Increase max && decrease min
Configurable long swipe and long press swipe areas
consolidate and cache views for smoother animations
User adjustable animantion duration
Add dismiss options for swipe ribbon
- Always dismiss on click
- never dismiss on click
- Don't dismiss for navbar action
fix app window crash if user has fast fingers and to much time
on their hands...
Swipe ribbon drag handles now get their own location, height,
width, and opacity.
Hide apps from app window
Hooks to dismiss app window if softkeys or navbar buttons pressed
Fix app window to pull all components also IE camera and messenger.
Rub some unicorn polish on the on touch glow. The giant boxes were
a bit ridiculous.
If ribbon is empty but toogles are not, just show toggles no flipper.
add adb wireless to toggle map
Phase 1 of the Animation chooser. Simple helpers to let users
choose the animation for the swipe ribbon and app window.
ill be adding some fancier animations for now just some of
the stock AOSP one.
Add lots o animation options. Also preload animations instead
of creating them at run time, should smooth things out a bit.
Keyboard IME hide, Vertical spacing App window, Cache resources.
Fix IME hide when navbar hidden.
Longpress on app window now takes you to app info.
Per-app PIE color
Since we're using Per-app color now, let's use it for PIE as well.
Fix layout of MultiWaveView and GlowPadView.
If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
the right
Fix that by not using width in the calculation, as the inset size
already takes it into consideration.
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
Fix message composing in DarkUI with emojis enabled
fix xxhdpi inverted launcher icon for Mms (HTC ONE)
Mms: set notification number attribute for messages
This will enable also the notification count overlay properly
sorry didn't get much time to work on kernel
May.28.2013 - initial Sprint Release
RB Settings: Update icon for keyboard enter
AudioService: Remove STREAM_NOTIFICATION from ringer mode streams
EthernetDataTracker: Set network available on connected
This change fixes state mismatch found in the bugs below,
and makes the code look consistent with disconnect().
In startMonitoring(), reconnect() is called before mNMService.registerObserver().
Then dhcpThread.run() could finish without getting interfaceLinkStateChanged() callback.
In such a case, mNetworkInfo has connected but not-available state - which is contradictory.
FW: Fix Menu Overflow Disable Option
The three button Menu Overflow would display no matter what setting was seleted within ROMControl, this commit makes a slight change to correctly return a result that reflects the users selection through ROMControl.
I had to enable then disable the option for it to function correctly (no reboot required)
Remove opaque check in preparing dirty region
Since preserve swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage being present from the previous process in the color buffer.
SystemUI: show blue dc-hspap icon when connected to Google services
TelephonyManager: hide NETWORK_TYPE_DCHSPAP
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
SystemUI: fix vertical date not showed while on Pie
SystemUI: show date on 2 lines in status bar
This allows showing of the full day of the week, and removes
the blank space above the date (which always felt strange to
me when clicking it to access the calendar).
It also fixes a spacing issue on smaller screen devices that
causes the quick settings button to be partially chopped off
when the AM/PM clock settings are enabled.
Fixed an accidentally dot showed in some languages (for ex. US english)
Bluetooth: Fix MAP accept threads sometimes spinning endlessly.
Randomly (under no obvious precondition), the MAP access threads spinned
endlessly after enabling BT, because mServerSocket.accept() always threw
IOExceptions, probably because the actual socket was already closed.
This change makes sure to exit the thread when that happens to not waste
CPU cycles and battery power.
This tracks similar changes done to the BluetoothPbapService and makes
sure to follow the (working) PBAP flow.
Fix a number of issues with T9 dialer.
- Fix an ArrayIndexOutOfBoundsException (like reported in
[1]) which happened when highlighting the last digits of a number and
the number had additional characters after those digits.
- Fix another potential ArrayIndexOutOfBoundsException due to the
highlighting code relying on normalNumber being a subset of number,
which wasn't the case due to number being additionally sent through a
formatter. Fix that by running the formatter before normalizing.
- Fix number highlighting not working if the number match occured at the
end of the number.
- Fix number type label & formatting not being updated on locale
changes.
- Fix T9 search not being triggered when pressing the dial button to
recall the last dialed number.
Remove DEBUG to avoid to run checking at every turn
Needn't to run storage checking in DEBUG mode at every turn,
it will make "DELETE OLD MSGS" always be checked in Mms Settings
Enhance the Easy Selector
- Follow GoogleUI Guidelines
- Fullscreen selector
- Added groups support
Mms: Go TRDS 2.0
use propper configuration values now
MMS app: fix crash when MMSC setting is NULL
An APN with a null MMSC column prevented the MMS app
to find the next APN in query.
Camera: Add TrueView
This commits adds the ability to show the complete image sensor frame
rather than the cropped preview used by aosp to fill the entire
screen.
Fix audio in Hangouts
* Add higher sample rates and stereo input device
May.29.2013
Fix wrong log information in DevicePolicyManagerService
When user reset password their password,
if password doesn't match target quality of device,
DPM print a log why can't reset password.
however log message isn't correct information.
in log context, it have to exist current quality
and target quality. this patch can help print correct log
Avoid IllegalArgumentException in Preference.java compareTo()
In some situations the collection.sort() algoritm fails in compareTo()
with a: java.lang.IllegalArgumentException: Comparison method violates
its general contract!, due to a more strict validation of the compare
contract.
Fix CalendarView to show the month title properly.
Step to reproduce:
Do this test on a Tablet (i.e. do in multi-pane layout)
1. Settings > Date & time > Uncheck the Automatic date & time checkbox.
2. Select 'Set date' and set the month to January and Done.
3. Re-select 'Set date' then you will find no month title just above the calendar.
Framework/base: Added synchronization block to avoid race condition
Fix for the synchronization issue leading to access of an array
Index out of bounds. Issue occurs due to race condition between
removing the activities of a crashed process from history stack
and resuming a separate activity.
SystemUI: Fix Tablet UI Date View
Mobile indicator has been removed, is still showed in quicksettings mobile tile. http://goo.gl/1ZtuS
TRDS 2.0: Update Dark toggle state
Add Multi-Part and Split SMS Configs
MMS: Fix lookup of vanity addresses
Avoid the use of the function PhoneNumberUtils.stripSeparators for non-strict
phone numbers.
May.30.2013
TRDS 2.0: Update Dark toggle state
Make character picker for QWERTY keyboards use HOLO theme
Also, removed the cancel button. Instead, touching outside will close
the dialog
Improve auto-brightness handling
- Add a setting to control the auto-brightness algorithm responsitivity
- Make the algorithm react much faster when the ambient brightness
increases quickly, e.g. when receiving a call in bright sunlight.
Allow changing auto-brightness responsitivity.
FW : Allow user selection of Font Size
RC : Allow user selectable StatusBar FontSize
Settings: refactor TRDS toggle and add some apps
RC: fixup ribbons icon
*more appropriately sized and colored
Phone: transparent in call widget (optional)
To see the complete contact picture on incomming calls
a lot prefer to have a transparent background. This commit
introduces this feature as optional option.
As well a bit sorting of the phone settings screen
tons of other crap
and all of cm's m7 commits
https://github.com/CyanogenMod/android_device_htc_m7-common/commits/cm-10.1
May.31.2013
Fix MAP SDP record generation
Give the bluetooth app API to register a server socket for a specific
UUID/port pair. It needs that for registering two OBEX server instances.
Fix Profiles - Ring Mode
Frameworks: airplane_mode_on moved to global google and CM
Fix: AUTO_TIME and AUTO_TIME_ZONE moved to Global google
Fix Notification shortcuts icons picker FC
Settings: Call Ring mode what Google calls it, not Silent mode
Silent mode -> Ring mode cleanup
add blink lights from tbalden (as as everyone else implemented on sense)
a few other kernel adjustments
another cleanup.. changed rom name to m7ul now since cm split up all the devices to their own naming
June.02.2013
Reduce observers in SystemUI: StatusBarIconView
Currently, for each status bar icon view there is a observer that
listens for changes of STATUS_BAR_NOTIF_COUNT. With one
notification usually having one or more status bar icons
you may end up easily with 10+ more observers for ~5 notifications.
With this commit the internal observer class becomes a singleton.
This means there is now only one observer for all status bar icons
and additional binder calls on new notification are avoided.
Reduce observers in SystemUI: KeyButtonView
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all buttons.
On my Nexus 10 it reduced the observer count from 48 to 4.
Reduce observers in SystemUI: BatteryBarController
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all instances.
On my Nexus 10 it reduced the observer count from 15 to 3
Fixing crash in PhoneNumberUtils getNumberFromIntent
Handling intent with no data when trying to retrieve number from
intent.
audio: Add overlay to fix analog docks.
Of particular interest to devices using libhardware_legacy and
affected by commit 5a484b7: http://goo.gl/rVR1Z
which restricted the routing of AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET
to docks using FORCE_ANALOG_DOCK cases. The EXTRA_DOCK_STATE_CAR case is
returning FORCE_BT_CAR_DOCK, preventing the dock audio from routing properly.
Add an overlay option for overriding to FORCE_ANALOG_DOCK.
FW: Menu Overflow Disable - Different Implementation
Original method I used to enable the menu overflow disable option incorrectly disabled the menu overflow altogether for some devices due to a late night derp.
This implementation of the check to confirm if the menu overflow has been disabled through ROMControl should hopefully correct this issue.
Pie: set Big as default for item gap (2/2)
Screen: http://goo.gl/aocZ7
Pie: updates (2/2)
-pie angle: fixes, cleaning and new value (Huge)
-pie size defaults
-strings updates
Pie: Fix and easy recalculation for Chevron and Pie
Pie: set angle default to 12° (1/2)
Pie: let Chevron adapt itself from pie's angle.
> This make Chevron able to recreate the battery bar when the angle changes.
Fix unresponsive statusbar area.
Framework: GlowPad Torch
LongPress GlowPad...Torch.
Release...No Torch.
FavoriteToggle: DismissKeyguard
Small Fix
ClockActions: Dismiss Keyguard
Kanging SteveSpear's Brilliant
dismissal method here.
Doesn't require an activity
as ...OnNextActivity() does
Fix MAP SDP record generation
Give the bluetooth app API to register a server socket for a specific
UUID/port pair. It needs that for registering two OBEX server instances.
Fix Profiles - Ring Mode
Fix: AUTO_TIME and AUTO_TIME_ZONE moved to Global google
Frameworks: airplane_mode_on moved to global google and CM
Improve auto-brightness handling
- Add a setting to control the auto-brightness algorithm responsitivity
- Make the algorithm react much faster when the ambient brightness
increases quickly, e.g. when receiving a call in bright sunlight.
Settings: Call Ring mode what Google calls it, not Silent mode
Silent mode -> Ring mode cleanup
Fix Notification shortcuts icons picker FC
Allow changing auto-brightness responsitivity.
Adapt torch intent for Glowpad
Change intent for this feature as we do not use AOKP'S torch
Lockscreen Longpress: Unlock Logic
In my opinion, we should unlock after
user removes their finger.
This matches short-press unlock better
and allows the user to change their mind
on a target (I do that a lot).
Added a vibration action on longpress
being true.
Fix SMS sending.
ACTION_SEND_MESSAGE must be routed through the privileged receiver now,
otherwise it'll be dropped in SmsReceiver.
BatterIcon with Center Text should be fixed now
Logo to menu is now disabled by default.. To set use device options in settings.. thanks.[/
alsa_sound: add HTC CSD CLIENT board flag for special cases (BT)
New HTC phones like m7 have special settings for BTSco CSD device
ids. Adding board flag BOARD_HAVE_HTC_CSDCLIENT to handle
these special cases related to HTC's csd client.
Love seeing more dev support for our Sprint One. Thanks!
Sent from my HTCONE using Tapatalk 4 Beta
Yes was waiting for this
Sent from my HTCONE using xda app-developers app
I'm definitely flashing when I get off work later
Sent from my HTCONE using xda premium
+1 as soon as I get wifi, this is mine!
Kewl
Does this have the floating notification feature of paranoid android, or has that even been implemented in p.a. yet?
Sent from my HTCONE using xda premium
Does anyone know where volume rocker wake is located in the settings?
Sent from my HTC One using xda app-developers app
Mko979 said:
Does anyone know where volume rocker wake is located in the settings?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Vol rocker wake is n/a.
However, you can go to settings > Device Option > Touchscreen > Wake Method and choose one of those 3 options.
Download is so slow for me :banghead:
Sent from my HTCONE using xda premium
I notice in the screenshot the navbar and no status bar, is this feature available for the sprint version yet? In can't seen to find it in the settings.
Sent from my HTC One using xda app-developers app
Yea man thanks for bringing this to sprint one
Sent from my HTCONE using Tapatalk 2
Running like a champ! Thanks yet again for bringing this over!!
Sent from my HTC One using Tapatalk 4 Beta
Does wifi tether work this build?
Voice mail Error
the preset *86 for voicemail isn't working and can't be changed.. voicemail notification doesn't work only issue so far but can be a deal killer...any help!!!
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
sakenfenc said:
the preset *86 for voicemail isn't working and can't be changed.. voicemail notification doesn't work only issue so far but can be a deal killer...any help!!!
Click to expand...
Click to collapse
I use Google voice and it works well
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------
Mko979 said:
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It can be changed in settings display
Sent from my HTC One using Tapatalk 4 Beta
Mko979 said:
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Go to Hybrid Settings > Apps. Under 'Changed Apps' touch to open, move the slidebar to the right to increase the dpi, touch the check mark at the top of the screen. Repeat this for all the apps you want to enlarge the font size, close and reboot.... good to go.

[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto

Update 30.11.2022
End of life and open source.
Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source.
Code is accessible: https://github.com/borconi/obd2aa
I will like to thank all of those who supported this project.
App Requirement
Torque Pro
OBD2 Reader
Android Auto compatible headunit or at least a copy of the Headunit Reloaded App (see signature).
This app will have limited functionality if you are using Android Auto on a your phone, the only functions you will be able to use is to see are notification about the speed cameras and street card!
Gauges and torque data will NOT work!
Previous XDA purchases can be reclaimed here: https://www.b3itlabs.com/download.php
How to purchase:
Visit: https://www.b3itlabs.com/prod.php?id=2
Instructions on how to get it running:
Option 1 - Will work on any phone & car/headunit combination, however the following features won't: - AutoPlay Music, 6 Tap limit remover, DPI change
After installing the app from XDA Labs, sign up for beta testing here: https://play.google.com/apps/testing/uk.co.boconi.emil.obd2aa and update the app
Once app is updated, make sure you disable auto-update in PlayStore then please uninstall it and reinstall it from XDA Labs.
With your screen unlocked, plug in the phone to the car, when prompted which app to use make sure you select "Android Auto"
Option 2 - Might NOT work on some device combination (for sure it won't work on Xiaomi phones), but if this method works all functions of the app are available
Install
Make sure you do not have any other 3rd party app Android Auto app installed.
Open the app and hopefully it will be quite self explanatory on how to set it up (choose colours, set gauge number, etc)
Open Android Auto (on the phone), go to About, tap the "About Android Auto" header 10 times, once you are a developer from the 3 dotted right corner menu select "Start Headunit Server" (ROOT users can skip this step!)
Close Android Auto
MAKE SURE YOUR SCREEN IS UNLOCKED and connect to the car, when prompted which app to use select "OBD2AA" and always (this needs to be done one time only) - If you are a HUR user select Android Auto and always! (If you do not see the prompt to chose, please go to settings -> apps -> all apps -> Google Play Services -> Clear Defaults and then try again)
Select the last tab on the right, by pressing it again you should see an app selector and choose OBD2AA
Give it a bit of time to start pulling the data from Torque.
Change log
Version 3.2 and 3.3 released 04/11/2018
Fix "drunk" map effect on Sync 3 units
Fixed rooted devices not being able to start headunit server.
Added option to change DPI for your screen!
Added option to auto play music on start
Added option to select default start screen.
Version 3.1 releases 26/08/2018
Compatibility fix for Pie devices.
Tap limit remover now working on all device
Tap limit remover allows Maps to be searchable even when driving.
Can be used for those who have problem with the parking brake wire.
Freeze issues fixes.
Important notes
Version 3.0 releases 05/07/2018
Compatibility fix for AA 3.0 and above.
Added option for overriding 6 tap limits
Added option for Bluetooth Audio output.
Important notes
Thanks to @slash_m_a_x for the support offered on this.
- Some users have reported choppy audio when using the app, this will mainly be due to the speed of the phone, the buffer on the car/headunit and other factors which are out of my control, if that is the case and you cannot use the app please feel free to contact me for a refund.
- Bluetooth Audio output might not work on all devices, it does depend how the car/headunit handles the Bluetooth. There will be devices which completely disable A2DP/Bluetooth capabilities of the car when Android Auto is running. In this case all the sound will be heard from the phone speaker rather then the car speakers.
- Tap limit will be disabled only for cars/headunits which are equipped with a GPS.
- In rare cases it can happen that after unplugging the phone from the headunit you will see a message which says that you are still connected to Android Auto, simply Force Stop the Google Play Services.
- You always need to make sure that Headunit Server is running on the phone (unless you have root), if the icon bothers you simply hide it.
Change log
Version 2.0 releases 17/01/2018
Added new layout option
Added styled gauged
Option for custom background on each gauge.
Option for custom needle on each gauge
Removed integration for CamSam/Blitzer.de (fully integrated now)
Possibility to change needle color
Possibility to adjust arch (indent, position, length) when using custom bg
Separated speed camera settings
Option to only download speed cam db over Wifi
Fixes for min/max value
Speed camera warnings over car speaker (Thanks @martoreto for the how-to)
Street info card
Added French translation (Credit to @fbike for doing the translation)
Added Danish (Credit to @Gunde for doing the translation)
Added Finnish (Credit to @Pyrres for doing the translation)
Added Spanish (Credit to @madabase for doing the translation)
Added Italian (Credit to @ilgaspa for doing the translation)
Version 1.6a - releases 03/10/2017
Fixed negative input for min/max values
Code cleanup
Added Greek language (credit to @sosimple for translating)
Version 1.6 - releases 29/09/2017
Fixes for custom PIDS
Fixes on Graphics rendering.
Fixed overlapping text
Fixed PSI/BAR conversion
Enhanced the gauge style.
Different approach for torque data pulling.
Moved to service should start work automatically when connected to the car
Added Supports PID alarms from Torque.
Added Toggle/Collapse layout for Pid settings.
Added Preview button with random data
Added Option to toggle units display
Added notification cleanup on exit
Added translation for DE,HU,RO (Credit to @FormelLMS for DE)
Added import/export setting option
Added option for colored text
Added TPMS option/screen
Added option to override car's headlights based on day/night
Added warning screen if nothing is configured to prevent black screen with no information.
Added more settings and move them to separate Settings options.
Added customizable background
Added search for PIDs
Added Support for Heads-Up notification
Added Speed camera warnings (powered by CamSam Plus)
Supported settings/Features:
3 x Colors for each gauge
Text color
Toggle needle, arch,units,scale,decimal and text for each gauge.
Variable number or gauges ( 1 - 15 )
Set warning limit for each gauge (percentage). This will be calculated relative to the given PID max value which is retrieved from Torque at runtime.
Possibility to set gauge in reverse mode. (example fuel tank)
Units will be converted automatically based on your Preferences in Torque
TPMS Screen (if you have PID's for TPMS data)
Possibility to use custom background/needle for each gauge
Low Fuel warning
Warm Engine warning
Speed Camera Heads Up Warning
Option to Overwrite Headlights state based on calculated sunset/sunrise
How to use it?
Open app and select each PID you want to display on your screen, adjust the number or gauges you want to see adjust the preference for each PID. If you want to use custom background/needle and interested on how to, please read HERE
Locking Pid values
On some PID's Torque reports wrong min/max values, by default if while using the application a reported value is higher/lower than the initially reported range, the app will adjust the range to the new values. However in some cases this is not desired and you will like to specify manually what is the min and max value for the give PID. In this case, simple edit the minimum/maximum for the pid and they will become locked, meaning the app won't make any adjustments.
By editing, it means you have to change the min or max value, the lock is triggered by the first keypress on this input fields.
The lock will be automatically removed when you select a different PID for the same gauge.
Preferences menu
Alternative pulling - Only enable this option if you have difficulties getting gauges updated, it uses an old deprecated method of obtaining data so should not really be used.
Enable debugging - Only enable it if you have problems with the app and I requested you to collect a bug report, otherwise it will spam the logs for no reason.
Automatically start Torque on Android Auto - Nothing to explain here
Launch FartKontrol on start - launches a Danish Speed Camera app (useless outside Denmark)
Custom Background (any background you will like to use instead of the black color)
Demo - When enabled random data is generated for the PID's just to see how things will look (in case you do not have an OBD2 adapter), so don't enable it.
Pid Alarms section. You can set up a low level fuel warning (displayed as a heads up notification) and a notification when the engine is warmed up. There a several PID options for both of this, pretty self explanatory.
TPMS Settings
- You set up the 4 PID's for TPMS, this will be used to display the tyre pressure values on the TPMS screen inside Android Auto
Speed Camera
Show current street card - Displays information about current street (name and speed limit if know). This information is updated once in 5 seconds and at a minimum distance of 200 meters so it's not 100% accurate it's more for general information.
Enable speed camera warnings - This will enable the app to display speed camera warning when driving, like any app which does this it relies on a database, which means it does NOT guarantee that it will warn you of all the cameras, and it might also produce false warnings. All options are pretty self explanatory.
Export & Import
- Allows you to export your current app configuration file which can later be imported (grate way of saving time of re-doing everything) after a clean install or so. The format use for Export & Import is JSON so if you want you can manually edit/adjust the values. Please see following post for more details about the sturcture/value/meanings
Permissions
Read notification permission - Only required so the app can read the notifications from CamSam and display them on AA scren
Locations - Only required if you want the app to overwrite the day/night theme based on sunset/sunrise
Storage - Only needed if you want to use your personal image as a background and/or planning to import/export settings
Can I create my own layout for the gauges?
- Yes, see instructions below:
Here is an example of the XML structure required, once you created the XML please send it over by email to [email protected] and I will include it in the next build.
Code:
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:tag="wrapper_layout">
<!-- Left column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|start"
android:tag="gauge_2"
/>
<!-- Middle column -->
<View
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_gravity="center"
android:tag="gauge_1" />
<!-- right column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|end"
android:tag="gauge_3" />
</FrameLayout>
Important
Each view must contain a tag, which is formated like in the example, where the number corresponds to the Gauge number from the setting screen.
The layout which wraps everything together must have a tag called: wrapper_layout
You are free to use any Layout you want, except ScrollView.
How to produce bug report?
Step 1 you need to enabled debugging in OBD2AA app, then follow this instruction set:
2. Enabling Developer Mode
Open Settings > About phone.
Scroll down to the Build number.
Tap the Build number 7 times in quick succession until "You're now a developer" appears.
Return to the Settings menu and select Developer options.
At the top of the screen, make sure 'Developer options' is set to On (green).
Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
3. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
Hold the Power button down until the menu appears.
Select Take bug report. and wait for the device to capture the bug report.
Tap the 'Bug report captured' notification when it appears.
Share the bug report. (I recommend to email it to yourself.)
Download the bug report to your computer.
Send the bug report by email to [email protected]
I have decided to open up my software, meaning I have made the source code available on GitHub, but it's only available for personal use, and you are not allowed (under any form) to redistribute your own version of the app. You can download and compile it yourself if you wish to do so, and you can implement your own changes for your own personal use, but you cannot create clones of the software which you redistribute under your own name. Source can be found here: https://github.com/borconi/obd2aa.
Due to the fact that there are some irresponsible developers out there, who created video apps for moving cars, which was one of the main reasons Google blocked 3rd party apps, I won't be updating the code on github any more, to try to prevent those developers to use my technique to overcome the limits. If you are developing a 3rd party app and you will like to know more about how I have done this, you are always welcome to contact me. If your project is something useful, I will be more then happy to share things with you.
This does not mean it is now a free app and apk can be freely shared!
Amazing work Emil, this along with your (and ofcourse @mikereidis) Headunit Reloaded app is perfect for Android Auto on the cheap ,
Gotta subscribe to this thread! The possibility of custom PIDs would be of huge interest to me.
Seems like its stuck without any option to change on Kmph rather than mph for speed etc, its set to mph in torque
fma965 said:
Seems like its stuck without any option to change on Kmph rather than mph for speed etc, its set to mph in torque
Click to expand...
Click to collapse
Yeap a few things to iron out....
Just to tired to work on it tonight.... it was a long one yesterday to get the alpha done for today but planning to work on it this weekend....
Emil Borconi said:
Yeap a few things to iron out....
Just to tired to work on it tonight.... it was a long one yesterday to get the alpha done for today but planning to work on it this weekend....
Click to expand...
Click to collapse
No worries, i wrote that quickly... other than that seems good, still figuring out what my car supports though. thinking about selling my tablet setup and buying the same car thing as me
fma965 said:
No worries, i wrote that quickly... other than that seems good, still figuring out what my car supports though. thinking about selling my tablet setup and buying the same car thing as me
Click to expand...
Click to collapse
Well I love my setup but I HATE my handsfree, have to come up with some solution for that because it's cr...
Emil Borconi said:
Well I love my setup but I HATE my handsfree, have to come up with some solution for that because it's cr...
Click to expand...
Click to collapse
does it not support external microphones?
fma965 said:
does it not support external microphones?
Click to expand...
Click to collapse
No. I have to try with a USB soundcard (which I use with my Odroid) but haven't got the chance yet, or I might just hook my himbox to the AUX in and use it that way. The built in mic is almost unusable especially over 30 MPH.
And first version of the app is live!
Bought, installed and looking good.
I've got the Prius PIDs plugin installed in Torque so I can see the data on my Prius C.
Only about half those PIDs are available to be selected, it looks like it's hitting the maximum number of allowed items in the "Select PID" list.
Great, could you please tell me, where I can find it?
FormelLMS said:
Great, could you please tell me, where I can find it?
Click to expand...
Click to collapse
The XDALabs app was a pain, I had to:
Install the XDA app from the Play Store
Log in
Install the XDALabs app it prompted me to install
Log in again
Then open Emil's link from the first post in the XDALabs app.
Ok, thank you. Any chance to have this in play store?
Hi.
Sorry for the pain caused by XDA labs, unfortunately Google play rejected the app submission so I cannot make it available trough that channel.
As for custom PIDs yes intending to support them in the future. Currently torque doesn't provide a method to expose them to 3rd parties so I need to speak with Torque developer if that is possible, alternatively I will need to fallback to manual PID configuration.
I will see if I can build a quick webpage to host/sell the app could potentially make it easier to get the app, but it will make it more difficult to keep it updated.
Emil Borconi said:
Sorry for the pain caused by XDA labs, unfortunately Google play rejected the app submission so I cannot make it available trough that channel.
Click to expand...
Click to collapse
Understood, I had a feeling Google wasn't going to allow it.
One of the issues with XDA is that you can get there via the web but it's not obvious at all how to buy it from there.
Then you have to jump through hoops to get the right app.
Emil Borconi said:
As for custom PIDs yes intending to support them in the future. Currently torque doesn't provide a method to expose them to 3rd parties so I need to speak with Torque developer if that is possible, alternatively I will need to fallback to manual PID configuration.
Click to expand...
Click to collapse
It's already showing around half of the Prius custom PIDs, it's like the list just runs out of space for more items.
edit:
Screenshot link
leonkernan said:
Understood, I had a feeling Google wasn't going to allow it.
One of the issues with XDA is that you can get there via the web but it's not obvious at all how to buy it from there.
Then you have to jump through hoops to get the right app.
It's already showing around half of the Prius custom PIDs, it's like the list just runs out of space for more items.
Click to expand...
Click to collapse
I'll send you a logging version at some point this weekend just to see if how much data Torque actually send over. For example it doesn't show any of my custom PIDs for KIA.
Thanks for this, it is awesome..
A magnificent add to the current great app.
Here is photo of my test
too low ISO 320.
My Observation:
1: I added in Gauge 2 : Volts(CM), then put "13.5" in W.Level 1, and 12 in W.Level 2, when I switch to ODB2AA it wont open and switch back to the current tab.
then I changed W.Level 1 to "13" and it works, so looks like it wont accept a decimal value!, don't know if its a bug or error from my side.
2: Each time I switch to the OBD2AA tab it takes 13s for the data to be pulled.
3: Just once "no data pulling", I had to unplug/plug usb to work.
suggestion:
* It would be good if there is a timeout option for the data pulling to stop, so no 13s delay when switch back and forth in that time, I don't know if it is applicable in AA.
Great job Emil.
MAJED.y said:
A magnificent add to the current great app.
Here is photo of my test
My Observation:
1: I added in Gauge 2 : Volts(CM), then put "13.5" in W.Level 1, and 12 in W.Level 2, when I switch to ODB2AA it wont open and switch back to the current tab.
then I changed W.Level 1 to "13" and it works, so looks like it wont accept a decimal value!, don't know if its a bug or error from my side.
2: Each time I switch to the OBD2AA tab it takes 13s for the data to be pulled.
3: Just once "no data pulling", I had to unplug/plug usb to work.
suggestion:
* It would be good if there is a timeout option for the data pulling to stop, so no 13s delay when switch back and forth in that time.
Great job Emil.
Click to expand...
Click to collapse
Check your email The version you are mentioning is the Beta, the release version has all those sorted
Sorry I'm moving too fast

Categories

Resources