Related
XDA Live has come to the Tilt....
This ROM is based on the not yet released at&t (AKU 0.4.4) Rom.
It has been debranded cosmetically, this is intended for Tilt Owners who want a lite version of the Tilt ROM.
Everything that has been removed can be added back via cabs (see link at the end of this post)
On a fresh configuration (hard reset), I have 160.83 mb of free storage memory out of 162.92 total!
Fixes:
* at&t MediaNet & WAP Data Connections are defined by default
* PIE scroll when loading large page fix applied
You will find to following removed:
* MS Office Mobile
* Solitare & BubbleBreaker
* Calculator
* Windows Update
* HTC Home & MediaPlayer PlugIns
* Cyberon Voice Dialer
* at&t PTT (Push To Talk) Support
* Quick GPS
* jbed Java
* RealPlayer
* Acrobat Reader
* Zip
* Sprite Backup
* at&t Dialer
* HTC TaskManager (X-Button)
* The Slider Sounds are removed & disabled
* ALL at&t bloatware
Registry Tweaks:
* SDK Certificates have been installed
* Disable Security Warning for Unsigned Apps & Cabs
* TCP-IP Tweaks
* Enable GPS Data in Photo Data
* Enable Assisted GPS
* Disable Sent SMS Notification
* Disable In-Call Fast Sleep
* Hide SIM Contacts (yes it sticks!)
* Long Press of RED End Key locks device
* Glyph (GDI/Font) Cache set to Large
* Enabled File System Cache
* Enabled File System Filter Cache
REQUIREMENTS:
1. Have Hard SPL on your Phone.
2. Read about and Understand the risks of Flashing Roms to your phone.
3. Understand that this Rom is currently in the development cycle. I plan for a new point version (v1.0, v1.1, v1.2 etc) to be released each Wednesday until it is at a point where this is no longer neccessary or feasible. So back-up your personal data preferably using either your PC (Outlook for PIM) or an Exchange Server as there have been reports that some PIM backups from other roms can cause problems (such as the SOD).
4. The new at&t Radio (1.27.14.09).
5. Report your experiences here.
KNOWN ISSUES:
None Yet!
DOWNLOAD LINKS:
The Rom:
-- No Radio Included (flashes faster but YOU MUST ALREADY HAVE new at&t Radio (1.27.14.09) on your device.
-- -- (RapidShare) (MegaUpload)
-- With Radio (It includes the new at&t Radio (1.27.14.09) which IS REQUIRED.)
-- -- (RapidShare) (MegaUpload)
Applications: XDA-Wiki Page
Per user requests: Support XDA-Live Tilt Rom Development via PayPal...
Plans for Version 1.2
Here are the changes I'm considering for Version 1.2
Fixes:
Got any ideas? Let me know.
Application Removal:
* Arcsoft MMS Composer
* Error Reporting
* Windows Media Player (is this possible?)
* Voice Recorder
* Sim Manager
* Sliding Sounds Settings Applet (will be added into the Restore Sliding Sounds Cab File)
Misc File Removal:
* MusicPlayerToday.dll
* MusicPlayerToday.dll.0409.mui
Registry Settings:
* Disable TouchFLO
Reserved 2
again saved
Reserved 3
Final one I promise
One request, could someone zip all the cab files into one archive. The restrictions from Rapidshare and Megaupload are horrible and it would take days to get the files.
aadadams said:
One request, could someone zip all the cab files into one archive. The restrictions from Rapidshare and Megaupload are horrible and it would take days to get the files.
Click to expand...
Click to collapse
Actually most of these files are small enough that they don't even show-up on the quota radar.
I prefer to keep them seperate because then as things are added/improved then you only have to download the changed files instead of a largeer archive.
Also note that if you use links other than the ones I put in the wiki I can't promise to support/bug fix them because I don't know what the source of the files is.
Rapidshare cut me off after the ROM for 67 min, but megaupload seems to be working for the add-ons.
Thx Kyphur
Thx Kyphur,
I absolutely love your ROM, and with all the apps as cabs, I can custom build what I want.
Do not like the HTC ROM at all-that big clock/monochrome UI is WAY overated. Thx again, one quick question, did ya ever get Windows Update figured out?
Alemaker
Alemaker said:
one quick question, did ya ever get Windows Update figured out?
Click to expand...
Click to collapse
I was on the fence about removing it already and I just decided to remove it. Even once MS starts putting out updates there is a greater possibility that the updates coulkd break a cooked rom.
Choices & Choices
I have upgraded to the AT&T latest ROM for a few days. Other than it came with a lot of garbages files, it basically ran fairly well. I am not totally happy with the speed performance but I am not sure other cooked ROM's will do better.
I have been downloading and flashing and testing ROM's for the past several months since I got my Touch when it first hit the market in Hong Kong, now I got the Tilt. I thought I could stop flashing but that is just the opposite.
Can some one able to comment on the speed on the stock AT&T ROM, Dutty's ROM, Sleuth's ROM and this XDA ROM? I know it is a lot of work and curiosity, but that is what we "flash-a-holics" doing every day, weeks, months .........
Like the Warning in Wiki, reading this forum may damage your health.
It is true!!!, your job and your marriage too!!!!!
thx again,
160.53MB of Storage and lovin it!!!
m
1.0 is working so fantastically but of course im going to flash again!
jychan28 said:
I have upgraded to the AT&T latest ROM for a few days. Other than it came with a lot of garbages files, it basically ran fairly well. I am not totally happy with the speed performance but I am not sure other cooked ROM's will do better.
I have been downloading and flashing and testing ROM's for the past several months since I got my Touch when it first hit the market in Hong Kong, now I got the Tilt. I thought I could stop flashing but that is just the opposite.
Can some one able to comment on the speed on the stock AT&T ROM, Dutty's ROM, Sleuth's ROM and this XDA ROM? I know it is a lot of work and curiosity, but that is what we "flash-a-holics" doing every day, weeks, months .........
Like the Warning in Wiki, reading this forum may damage your health.
It is true!!!, your job and your marriage too!!!!!
Click to expand...
Click to collapse
I tried many ROMs and came back to this XDA v1.0. Now dowloading the v1.1!!! Just try and you can realize the differenciations!
When you talk about 'good ROM' you should think about the speed and the stability only!
Windows Live?
I also love the 1.0 (and now 1.1) version of this ROM. Very fast & stable, and I love to be able to choose my own apps on top of it.
I am having difficulties with Windows Live, however. I've tried both v10.6.33.0600 version and v10.6.32.2100 and both stall at the 2nd setup step. The phone doesn't lock up, but the install just hangs and the Windows icon stops spinning...
/av
alvalvano, try running the removehiddenproxy cab before setting up Windows Live.
Thanks for the suggestion...
akadonny said:
alvalvano, try running the removehiddenproxy cab before setting up Windows Live.
Click to expand...
Click to collapse
Tried that, too
No love.
alvalvano said:
Tried that, too
No love.
Click to expand...
Click to collapse
Windows Live wouldn't install or work for me properly if I tried installing to the storage card, only if I install to the device.
Alemaker
my work around...
Alemaker said:
Windows Live wouldn't install or work for me properly if I tried installing to the storage card, only if I install to the device.
Alemaker
Click to expand...
Click to collapse
Regrettably, I am also installing to device. My workaround was to turn on wifi for the initial setup. I have successfully configured it, but I still cannot connect over the air.
Many thanks for the replies.
/av
is there any way to enable the video call as in non tilt users ?
Sorry, I don't use Windows Live.
Anyone else using Live succcessfully "over the air"?
Also, 2 new CAB files added to the collection (follow wiki page link in first post): HTC Home Plugin and WMP Plugin...
I open the post so those interested can share which apps work and wich do not work in our Polaris devices (no keyboard, chip kinda old, 240x320, etc), and why these apps are so unique to you. It is not a ranking or a directory intented to list 1.000 apps.
Please refrain from asking for codes, warez, etc. Only links to "official pages". No attachments please. I will update this first post whenever I think it is relevant for the original idea of the post, so here we go:
Desktop
File explorer
Google Tools
- Google - My Maps Editor 1.1.6 : Not working in Froyo
- Google Earth: Not working in Incubus RLS14 neither 1.0 nor 1.1
- Google Sky Map: Working but inverted.
In the cloud
- mspot: upload with your desktop utility and listen the music in the desktop or anywhere with your device with wifi.
GPS related:
- c:geo: Geocaching program linked to your account at geocaching.com, you can download caches at home and work off line (with the gps on, off-course) later.
Connect to PC
- Web Sharing Works great with Incubus RLS14. You can browse your device from a web explorer, play music, videos, download and upload files, etc.
- Dual Mount SD Widget Works great with Incubus RLS14. You can connect your device to USB as a pendrive, both in windows and ubuntu
Games not suitable for Polaris (they require keyboard or another screen resolution)
- Abduction: No keyboard
No solution found so far for:
- Internal Radio
- TMC
- Adb device name ?
Camera, my camera got broken (the glass) so I can not tell a lot:
- Quickmark QR-Code works great
- Barcode Scanner works great
If you like installing many apps, please share your current configuration:
- mine is NAND install with 1G system.img and 2G data.img installed in SD Card. Pros: lots of space CONS: I think it takes longer the first minutes after booting (it gets smooth afterwards) and the system becomes less responsive when I enter the apps mantainance tool and you must be tidy when activating and deactivating the usb mode.
This patch will disable the compatibility flag inside the framework.jar.
I know there is a checkbox in the DevTools and SpareParts application, but it seem this wasn't working for all apps (e.g. Google Reader)
The patch simply disabled the parts in the system where the framework checks if the device screen configuration is supported by the application and would have set the compatibility flag.
To install:
- Rename CompatibilityFix-v1.0-update.zip to update.zip
- Copy the update.zip to the root of your SD Card
- flash using recovery
Tested on FolioMod v1.3d
As always source is attached to port this to other devices/roms.
ok this trick work very well with reader, thank you very much!!!
would this solve the scewups with some games? mainly diner dash, robo defense, farm frenzy etc?
Hello, does it work with foliomod1.4? Thanks
Yes it works.
Please note that some apps will still run using only part of the screen, but most of them will get full screen. As some of the apps are written to use only certain resolutions and certain DPIs values they may fail to adjust.
Regards.
Doesn't work in android 4.2
Profile Aim
Tasker will use a number of triggers to detect, log, monitor and report when your device has been in a deep-sleep state, and more importantly; when it hasn’t. The profiles identify both potential and actual deep-sleep-behaviour, providing statistics and real-time alerts should your device fail to enter deep-sleep in the absence of any common preventing factors. The alerts will enable you to identify the troublesome processes and applications that love to kill your battery.
Pushing Tasker to its Limits?
Composing this after just uploading V13, I can confidently say that I'm pretty sure I've now pushed Tasker to its limits when it comes to using its functionality and to build as close as I believe you can get to a fully fledged application:
* Installation tasks to inject binary and set permissions
* Tasks dynamically compose and execute shell scripts
* Automated and ad hoc error logging
* 'Self-checking' error loops
* Tasker/shell generated reporting
* Media and interactive notifications
* 28 intertwining tasks totalling 500+ actions triggered by 11 contexts
Theory
Finding out when your device has entered deep-sleep, is rather like asking someone to drop you a quick text as soon as they’ve died. As impossible as that sounds, you can of course always get them to let you know they aren’t dead; establish they are doing something else so currently can’t be dead; or discover they are indeed still alive and therefore conclude they weren’t dead in the first place…
I’ll stop talking in riddles and start where I started, which is when your device has the potential to enter deep-sleep:
* When the display is off
Yes, I know that was a pretty obvious one to start with, but if we just record potential deep-sleep-time as ‘screen off time’ we will be left with major inaccuracies such as:
* Media Playing
* During Call
And more importantly:
* Device charging
Those example factors already start to narrow down the times of when your device enters the zone of deep-sleep-potential (DSP).
Practice
We can retrospectively establish the amount of time the device has spent in deep-sleep, by looking at the file:
Code:
sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
Next to each available scaling frequency is the amount of time in milliseconds the device has spent at that frequency since last boot. This is my example file:
Code:
245760 319834
384000 4651
576000 3736
768000 2271
998400 6983
1113600 24953
The up-time of the device, less the sum of the individual frequency times, provides us with the amount of time that the CPU was not active = Total-Deep-Sleep-Time. We can compare this proportionally to the up-time and simply report deep-sleep as a percentage of the current usage (since last boot).
That is all well and good, but if the percentage is very low, it immediately suggests poor device performance and that may not be a true reflection. To make this figure more accurate (and perhaps less alarming) we first need to establish the DSP your device had and base our statistics on that.
Overview
Dealing with the obvious first, we know that DSP occurs only when the screen is off and ends when it turns back on. At the point the display goes off, we can take a log of the current up-time and compare it to the total time in frequency state. Subtracting one from the other gives us a constant we can refer to.
If the device does not enter deep-sleep prior to the screen turning back on, then performing the same calculations at the display on trigger should provide the same constant.
Any difference between the display off/on constants will notify us not only that the device has been in deep-sleep, but also for how long. This information can be immediately relayed and/or totalled up to be used against DSP times to build a more accurate, real-time and ongoing reflection of your device’s deep-sleep-behaviour (DSB).
Already starting to narrow down DSP times, and we can further exclude the events that were listed above (such as charging) from our DSP calculations.
Profiles and Tasks
I think I may have permanently damaged my brain making these profiles work, report and intertwine correctly… I have many further plans which I’ll list below – albeit theoretically….
Unlike my other Tasker posts, I’m not going to make this a tutorial (*group sigh?*), as in brief terms (which does not reflect the extent of my hair-loss), it keeps checking the time-in-state files against constants whilst making sure no DSP excluding factors or events are active. It performs a sh*t load of comparable percentages, converting a lot of milliseconds to hours and minutes to make it user-friendly for you. Yes, that was my hint to you to hit the thanks meter
Honestly, the thought of writing this one out in detail makes me feel bored, so I doubt it would make very exciting reading… The logic in the profiles is there to follow of course and I’ll be happy to answer any of your questions, but for once this really is just a ‘plug and go’ – there’s nothing for you to edit, other than perhaps choosing to align triggers with your existing set-up.
Future Development
It's my understanding that power management and wakelock debugging can only be implemented when Android is compiled and therefore we have no specific "I'm about to fall asleep, quick take a log" trigger to work with (I'd love you to tell me otherwise) for analysis, so as the profiles develop, more deep-sleep preventative 'events', such as receiving an SMS will be included in order to build a greater picture of what is happening before and after deep-sleep.
The ultimate goal would be to gather comparison logs to flag up the likely suspects for the device not entering deep-sleep in the first place or waking up from it too often. You can almost see the UI notification now:
YouPorn Mobile and has been killing your battery - uninstall it by clicking here
Click to expand...
Click to collapse
That may be a few versions away, but we've all got to have a dream... and preferably one that involves every noob with battery issues downloading my application for a dollar from the market
What? You didn't think I was doing this all for the love of the community did you?!
Simple Preparation
Before importing the profiles and tasks:
* Make sure you are running the latest version of Tasker 1.2u2
* Install the Glossy Silver HD icons apk (Open any existing task, click on the icon selection button - Download More Icons)
* Backup your profile data and tasks and a recent nandroid never does any harm.
* Ensure Tasker has 'Accessibility' and 'Administrator' permission on your device.
Installing instructions are in post #3
------------------------------
Ad-hoc
I've added in an ad-hoc task from V3, so you can check the statistics at any time. Easiest way to launch it is via an icon from your homescreen using a Tasker 'run task' widget, available in the widget options on your launcher. DSDAdhoc should be triggered first, which in turn will trigger further tasks and information will appear on your display.
Trigger Information
The profiles currently use the following triggers:
* Display On
* Display Off
* In Call
* Call End
* USB Plugged Power
* Device Boot
* Device Shut-down
* Media
Depending on your current set up, you may already have most of these contexts, so assuming you wish to keep the profiles installed, you may wish to use Perform Task actions as opposed to doubling them up. You must make sure these profiles run with a higher priority than your others to avoid the loops catching one another...
Files and Logs
The Deep Sleep Detective writes files to your SDCard:
DeepSleepDetective.txt is triggered when your device has not been in DS for more than 80% of DSP. It provides a list of your running applications, historic wakelocks, statistics and active wakelocks at the point the display was turned off - The information provided will become more specific and user friendly as the version go on.
DSD-BootLog.txt is triggered when the device boots up. It writes DSD statistics taken prior to the last shut-down.
A DSD directory is set-up that contains relevant files. There is also a back-up folder where previous Detective Reports will be stored so they are not overwritten.
-----------------------------------------
I'll add more to the above when I get time
-----------------------------------------
Credits
waydownsouth - HUGELY MASSIVE Terminal & Script help
nobnut - HUGELY MASSIVE amount of testing
Pulser_g2 - Solving my toolbox woes
Change Log
Code:
[B][U]V13[/U][/B]
* Direct execute shell commands via Tasker (no longer use locale plugin)
* Changed logic for end call to prevent 'display off data stolen' errors
* Removed incorrect %DSCOFF variable clear in TIS tasks
* Corrected the DSDAdhocTIS upload
* Cleared errorlog.txt to avoid file failures
* Included toolbox generic tests in error log
* Populated XDA Username in error log and ReadMe
* Included busybox version in error log
* Let DisplayOff handle %NOCOUNT clearing
* Calculated time_in_state using shell (too many frequencies on recent devices)
* Included IF/ELSE logic in certain tasks
* Added failsafe for missing time_in_state files
* Set permissions using busybox to avoid permission to set permissions error!!
* Corrected binary PS request
* Increased data collected in error logging (nothing personal of course).
* Tried my best to make notification click work correctly...
* Collected DSP data when incoming call wakes from sleep and display goes off.
* Included Tasker version number in error log - credit [URL="http://forum.xda-developers.com/member.php?u=2440628"]fubaya[/URL]
* Replaced all Test File actions
* Improved logic in almost every task
* Lots of other things I can't remember...
[B][U]V12[/U][/B]
* Uploaded [B]DSDAhocTIS [/B] in the V11 .zip file instead of [B]DSDAhTIS[/B] :mad:
Credit - [URL="http://forum.xda-developers.com/member.php?u=2824949"]1337GamingNinja[/URL]
Please got to [URL="http://forum.xda-developers.com/showpost.php?p=16089263&postcount=760"]this post[/URL] for the additional [B]DSDAhTIS[/B] download to the V11 .zip below
[B][U]V11[/U][/B]
* Inserted IF to deal with %CPUDSD being set to 'EOF' in DSDADhoc & DSDDO
* Inserted 'variable add' in DSDNotify to deal with %DSCOFF being set to zero on first display off'
* Included uptime output in error log
* Included %DSDDO & %CPUDSD in error log
* Added %UTEOF, %TISW & %UTW variables and loops to diagnose read/timing errors
* Added uptime fail-safe with routed task to time_in_state
* Added notification short-cut 'on-click' actions
* Included DSD version number in error log
* Added standard 2 second reduction to %DISPOFFINT due to lag
* Stopped scrolling notifications when in call
* Changed permissions levels
* Added flag-pass variable to prevent overlap
* Added 5 second wait to display off/on profiles to handle screen on/off 'flicks'
* Increased intelligence of loop checks
* Added sound to certain events
* Included ROM version in error reporting
* Removed %DSCL loop in favour of odd/even flag-pass
* Fixed %NOCOUNT prevention
* Included a second shutdown profile in case toolbox method is failing
* Moved binary folder inside DSD folder for ease
* Included Adhoc error reporting to save user requests
* Prevented cancelling all Tasker notifications on display off
[B][U]To Do[/U][/B]
* Make the information in the Detective Report more user friendly and understandable
* Receivers for wakeups during deep-sleep
* Solve Tasker media 'bug'
* Include Tasker version number in error log - Dev including in next beta
[B][U]V10[/U][/B]
* Called time in state data via script to avoid permission errors
* Reverted DSDDO, DSDShutdown, DSDAdhoc to the above
* Added wait times and loops to allow for delays
* Removed DSDXDAUN as it was too buggy
* Reordered tasks to allow for multiple calls of single script
* Removed directory/file making tasks to minimise possible set-up errors
* Removed unnecessary permissions from script
* Added further dynamic script controls to increase speed of shutdown task
* A few more bits and bobs...
[B][U]V9n[/U][/B]
* Added missing files! Thanks [URL="http://forum.xda-developers.com/member.php?u=2393301"]nobnut[/URL]
[B][U]V9[/U][/B]
* More notifications of what is going on to update the user and identify error sources
* Error logging and request to email the details included
* Updated reporting tools and information
* Increased intelligence of tasks
* Included 'self-checking' of necessary actions
* Standard binary injection
* Standard file permissions on boot
* Fixed screen off/on/power/on/off entanglement
* Updated aesthetics
[B][U]V8a[/U][/B]
[!] Sorry to those that have already downloaded V8, but I needed to make changes for the reports to function correctly - Damn those SU requests!
* Changed set-up tasks to try and ensure SU requests are approved.
[B][U]V8[/U][/B]
* Added preventative for %DSCOFF failing to populate in DSDDO
* Added notification to DSDDisplayOn if DSP was unavailable during screen off time
* Added wakelock capture to DSDDisplayOff
* [strike]Added IF != 0 to %DSCON in set to % action of DSDNotify[/strike]
* Added wakelock hunter to DSDDisplayOff
* Changed multiple locale commands to shell script dynamically composed by Tasker
* Added script to match wakelocks to owner applications/processes - BIG thanks to [URL="http://forum.xda-developers.com/member.php?u=3390610"]waydownsouth[/URL]
* Cut report building time down to under [strike]10[/strike] 5 seconds
* Added IF and GoTo actions to avoid the bad maths eval errors on constants
* Added DSDSetUp task with ReadMe.txt
* DSDSetUp to create directories and files
* Added 'spoiler' preventing to DSDNotify
* Added display off media context
* Added Further test file actions to avoid empty reports
* Changed collision handling and task priorities
* Added additional variable clear actions to avoid possible data corruption
* Too many more to list...
[B][U]V7[/U][/B]
* Removed due to a patent infringement claim by Apple
[B][U]V6[/U][/B]
* Removed additional % in DSD-BootReport - credit [URL="http://forum.xda-developers.com/member.php?u=2393301"]nobnut[/URL]
* Reverted to linux/locale 'toolbox' commands for report information - credit [URL="http://forum.xda-developers.com/member.php?u=2178960"]Pulser_g2[/URL]
* Reverted to Tasker handling all calculations - Speed Test proved Locale Plugin to be much slower
* Removed pop-up tasks as they are fugly
* Added 'wait until' actions before %CPUTIS to ensure data from file is written
[B][U]V5[/U][/B]
* Changed PSD to DSP in Flash action #33 in DSDAhMaths - TYPO! Thanks [URL="http://forum.xda-developers.com/member.php?u=2393301"]nobnut[/URL]
* Removed unneeded variable clear action in DSDNotify
* Ticked missing 'do maths' in action #13 of DSDAdhoc
* Added minimal uptime threshold until tasks are expected to perform maths to avoid data corruption
* Corrected %CPUDSDD error in action #8 of DSShutdown
* Corrected adding X% in DSD-Shutdown write file action as '%' is looked for for errors... Oops.
* Removed append from above write action to minimise possible errors.
* Added functionality to sum scaling frequencies using locale
* Added above command to DSDSuperuser, DSDAdhoc & DSDDO
* Added additional variable clear caution in DSDDO to avoid %CPUDSDD1 & %CPUTISD1 being used.
[B][U]V4[/U][/B]
* Append box should be unticked in action #1 of DSDShutdown
* Corrected variable clear data in %DSDDO
* Added variable clear %DSDDOS to end DSDDispOn
* Added file existence check to DSDDeviceBoot
* Added safety value to %DISPOFFT to prevent knock-on failures if not set
* Reverted to V1 DSDDO due to toolbox differences in devices
* Reverted to V2 DSDAdhoc due to toolbox differences in devices
* Removed unneeded actions from DSDSuperUser due to revert
* Added '+' '-' & 'Zzzz' popups to confirm task flow
* Added DSDAdhoc into .zip
* Reverted to V2 DSDShutdown due to toolbox differences in devices
[B][U]V3[/U][/B]
* Removed 'append' from action #1 of DSDShutdown to avoid looping data corruption
* Corrected error in IF statement in the task DSDIntMaths
* Added 400ms wait task after locale fetch in #2 of DSDDO
* Ad-hoc tasks added so information can be viewed at any time
* Restructured A LOT of the tasks
* Included more information in report files
* Lots more I've forgotten
[B][U]V2[/U][/B]
* Changed 'between boot report maths' to boot instead of trying to rush them in before shutdown
* Used locale/linux to perform some of the maths as I assume it's quicker?
* Cut down task sizes due to above
* Altered structure of output files for easy reading
* MASSIVE boot task that hurt my brain
Bugs
* Transition power on/off / display on/off + incall - Solved in V9
* Binary package differences from device to device - Solved in V6 - Credit Pulser_g2
* DSDAdhoc providing erroneous results on first run after charge - Solved V6
* SGSII needs different files - post if you need them - Solved in V4
* DS Data Failure Notification on boot - Solved in V2
* I'm getting a prompt to click on a file at boot, but it fails? - Solved in V2
* I'm getting Not Numeric errors when I open Tasker - Solved in V3
* I'm getting an error %CPUDSDD is not numeric? - Solved in V3
* DSDDeviceBoot is not running correctly? - Solved in V3
* The boot file isn't being written? - Solved in V3
* Media profile is deactivating when the music application is no longer in the foreground - Dirty solution for now is to switch the screen off only when you are in the application... - I'm on it
Installation Instructions
* Delete all profiles and DSD* tasks from Tasker
* Delete all DSD* profiles and DSD* tasks from the folders Tasker/Profiles & Tasker/Tasks
* Unzip the latest version download
* Place the task files in /sdcard/Tasker/Tasks
* Place the profile files in /sdcard/Tasker/Profiles
* Place the folder DSD on the root of your storage card (after deleting/renaming any current folder from a previous version)
In Tasker, from the menu options/profile data 'Import One (15) Task':
DSDDON
DSDDONTIS
DSDDOFF
DSDDOFFTIS
DSDIntMaths
DSDNotify
DSDAdhoc
DSDAdhTIS
DSDAhMathsDST
DSDAhMathsUPS
DSDFileSetUp
DSDSUPOP
DSDSuperUser
DSDWakelock
DSDErrorLog
In menu options/profile data 'Import One (11) Profile':
DSD-DisplayOn
DSD-DisplayOff
DSD-Incall
DSD-EndCall
DSD-Power
DSD-Boot
DSD-ShutDSH
DSD-ShutDTIS
DSD-Notify
DSD-Reboot
DSD-Media
The above profiles also contain the following 13 tasks, which will be automatically imported:
DSDDispOn
DSDDispOff
DSDDeviceBoot
DSDDuringCall
DSDEndCall
DSDCharging
DSDChargeEnd
DSDMedia
DSDMediaEnd
DSDNClick
DSDShutDSH
DSDShutDTIS
DSDReboot
First Run
* Ensure all of the task and profiles imported correctly
* Save out of Tasker to preserve the changes made
* Load Tasker and select the task DSDSuperUser
Thanks to nobnut and his testing, I've been able to establish that the SuperUser requests can take up to 30 seconds to appear. There is only one command that needs permission. DSDSuperUser has a 30 second wait time to give the SuperUser application a chance to prompt. If it hasn't appeared by the end of the wait time, there is a pop up asking if you want to run the task again - I hope you'll only need to run it once though!
* Press 'test' in DSDSuperUser and follow the instructions from there! PLEASE do read the readme file as it contains other important instructions!
Let's get detecting...
The thanks meter lets me know I'm appreciated!
Oooh, me likey.
It's a shame you decided against the tutorial part as normally I just read that bit, nick the ideas, and write my own profiles.
Still, this could come in extremely handy. Keep up the good work.
neilix said:
Oooh, me likey.
It's a shame you decided against the tutorial part as normally I just read that bit, nick the ideas, and write my own profiles.
Still, this could come in extremely handy. Keep up the good work.
Click to expand...
Click to collapse
Thief!
Maybe I'll explain a little... Perhaps a YouTube video is the way forward...
What should have been provided within Android by default. Excellent idea.
@ Brandall
you should look into the output of these terminal commands:
Code:
uptime
Code:
cat /proc/wakelocks
HTH
waydownsouth said:
@ Brandall
you should look into the output of these terminal commands:
Code:
uptime
Code:
cat /proc/wakelocks
HTH
Click to expand...
Click to collapse
Thanks waydownsouth, you were already getting a big credit in this thread as it was! Knowing I could output sleep-time would have saved me a few lines of maths!
Understanding how the cat /proc/wakelocks output could identify a deep-sleep preventer is probably going to take a few more nights on Google! You best sign out of G-talk
Watching with Interest as I've noticed (since I've got Gingerbread battery logging that actually shows such info) that *something* has been keep my device on partial-wake at night, but not EVERY night, just some nights. Haven't been able to identify WHAT yet, as it isn't making itself known through any abnormal CPU usage, just by the fact my device doesn't go to deep sleep and thus drains battery more than it should.
Hi, I'm getting the notification on reboot that shutdown didn't go correctly.
nobnut said:
Hi, I'm getting the notification on reboot that shutdown didn't go correctly.
Click to expand...
Click to collapse
Thanks for letting me know - At least I know the boot notification is working!
Attached is the V2 version I'm working on. In case you need instructions (I never know anyone's level): After you've imported it, click on DSDReport in the profile screen, click add, select DSDReportV2 - then delete DSDReport.
I hope this one runs quicker... You'll need to give it SuperUser permissions as normal, so please 'test' it a couple of times before trying out a reboot...
Please let me know it works!
lotherius said:
Watching with Interest as I've noticed (since I've got Gingerbread battery logging that actually shows such info) that *something* has been keep my device on partial-wake at night, but not EVERY night, just some nights. Haven't been able to identify WHAT yet, as it isn't making itself known through any abnormal CPU usage, just by the fact my device doesn't go to deep sleep and thus drains battery more than it should.
Click to expand...
Click to collapse
Well I hope in a few versions time this will be able to tell you... Messing with sleep preventing wakelocks right now...
brandall said:
Thanks for letting me know - At least I know the boot notification is working!
Attached is the V2 version I'm working on. In case you need instructions (I never know anyone's level): After you've imported it, click on DSDReport in the profile screen, click add, select DSDReportV2 - then delete DSDReport.
I hope this one runs quicker... You'll need to give it SuperUser permissions as normal, so please 'test' it a couple of times before trying out a reboot...
Please let me know it works!
Click to expand...
Click to collapse
I just realised something! There was no DSDReport in the original v1.0 zip.
nobnut said:
I just realised something! There was no DSDReport in the original v1.0 zip.
Click to expand...
Click to collapse
I combined it into the DSD-Shutdown profile import - I assume when you expand this context the original task DSDReport was showing??
Yes, sorry about that.
Just tried it again (having granted SU before rebooting) similar thing happened.
I received a 'DS Data failure - Incorrect shutdown - Resetting Data' notification.
EDIT: I'm also getting a 'DS Data Failure' on subsequent reboots.
Report attached for information.
nobnut said:
Yes, sorry about that.
Just tried it again (having granted SU before rebooting) similar thing happened.
I received a 'DS Data failure - Incorrect shutdown - Resetting Data' notification.
Click to expand...
Click to collapse
Damn it... That notification is happening because it is detecting %DSBOOT didn't set to 1 before shutdown, suggesting it didn't gather the necessary data to provide a full 'daily report'.
If you get time, could you let me know which data it did manage to gather by adjusting the task DSDDeviceBoot? Could you remove these actions:
IF %DSBOOT Not set
Notify vibrate DS Data Failure
GoTo action
End IF
That way it will continue to write the information it did gather to the file DS-BootReport.txt. A screen prompt should ask you if you want to view this file shortly after rebooting.
Please keep a copy of the original DSDDeviceBoot task so you can re-import it afterwards! Your thanks meter will be increasing....
brandall said:
IF %DSBOOT Not set
Notify vibrate DS Data Failure
GoTo action
End IF
Click to expand...
Click to collapse
Just to confirm,
Line 1... Mine currently reads 'IF %DSBOOT Set'
What would you like me to do? Delete it or edit it and try again?
nobnut said:
Just to confirm,
Line 1... Mine currently reads 'IF %DSBOOT Set'
What would you like me to do? Delete it or edit it and try again?
Click to expand...
Click to collapse
Is there not a '!' between %DSBOOT and Set ?
Thanks for the upload of the file - I'm very confused now though, as that file shouldn't be written if the DS failure notification triggered... What number is your GoTo action set to? Does it take you to the variable clear action right after the write file DS-BootReport ?
Thanks for this
Set to 7.
Yes there is a '!', I was just checking.
Shall I go ahead and delete those lines?
EDIT: Yes, I am directed to the view/clear.
EDIT2: Deleted lines and now get a "DS Boot Report: 0%" notification.
When clicked, I am not redirected (no clear /view option).
EDIT3: Could the report be written when clicking 'Test' to get SU granted?
nobnut said:
Set to 7.
Yes there is a '!', I was just checking.
Shall I go ahead and delete those lines?
EDIT: Yes, I am directed to the view/clear.
Click to expand...
Click to collapse
Thanks.
I don't understand how it can be applying both for you...? IF the failure notification action happens then it should go to action 7 which is after the write file action??
I can see from the text file you attached that your data is populating correctly (somehow!?) - No need to delete the actions for now as you're still getting the desire output - delete it if you find it annoying though!
I'm baffled as to how it is doing both actions regardless... hmmm - I'll have a ponder and come back - off to a meeting now. Thanks again for looking into this for me - appreciated.
EDIT2: Deleted lines and now get a "DS Boot Report: 0%" notification.
When clicked, I am not redirected (no clear /view option).
EDIT3: Could the report be written when clicking 'Test' to get SU granted?
Click to expand...
Click to collapse
When you make the changes, are you saving out of Tasker and going back in?? If it's providing a notification when the action is deleted, something is seriously wrong!!
Yes on the SuperUser idea... I didn't consider looking at the date/time as don't know what date/time zone you are from! Could you delete the text file please... Have to dash!!!
EDIT: I'll upload a changed version on my return if it's still functioning strangely
Hello everyone!
I'm here to make a guide for people who are new to their Galaxy R, and also the Android world
Our phone has the following specifications:
- 1Ghz Dual-core ARM Cortex A9 processor (ARMv7)
- NVIDIA Tegra 2 AP20H chipset (Delivers one of the best graphical performances)
- 1GB of RAM (even though Samsung only gives it 724MB of it for real practical use)
- 8GB of internal memory storage (2GB ROM + 2GB for applications + 4GB user available) thanks m.kochan10 !
- SDcard support up to 32GB SDHC
- 5MP Camera with 1.3MP front-facing Camera (we have a chance for face unlock ) therefore it supports video calling
- SD-LCD () capacitive touchscreen, 16,000,000 colours
- Runs on Gingerbread (2.3.3)
- Supports Quad-band GSM (GSM 850 / 900 / 1800 / 1900) and Quad-band HSPA (HSDPA 850 / 900 / 1900 / 2100) with HSDPA+ (21Mbps) and HSUPA (5.76Mbps)
- Weighs 135g (LIGHT!)
- Has a scratch-resistant glass with multitouch
- TouchWiz UI v4.0 :O
- Has official ICS support
Taken from http://www.gsmarena.com/samsung_i9103_galaxy_r-3967.php
Q&A coming soon from cooleagle
Basic noobie questions:
Q1: What is Android? I heard that my phone has this as said by the guy who sold me this phone......
A1: Hello new user, Android is an Operating System (a.k.a OS) for phones, like how Windows is for computers. It is meant to be simple, efficient and customisable.
More can be seen here:
http://en.wikipedia.org/wiki/Android_(operating_system)
Q2: What is root? What does it do?
A2: Rooting is the process of attaining superuser (su) access to your phone. It is similiar to the jailbreaking process on Apple phones
Q3: What are the different Android versions available for our phone?
A3: Currently only 2.3.3 to 2.3.6. Don't worry, Cyanogenmod 7 will have 2.3.7
Q4: I've heard all this commotion about "stock" firmwares. What are they?
A4: Okay, stock firmwares are update files from Samsung which are available for download. This stock firmware may also stand for factory firmware (if you didn't update)
Q5: What's build.prop? What are some of the build.prop tweaks and meanings?
A5: Build.prop is a file that defines the build properties of the build and phone. It is a necessary part of the phone and if it's missing, the phone may not be able to boot.
Here are some build.prop tweaks:
pm.sleep_mode=(0 or 1)
Enables the phone's sleep mode.
0 to disable, 1 to enable.
ro.ril.disable.power.collapse=(0 or 1)
Disables the network power collapse, allowing the phone to sleep better.
0 to disable, 1 to enable tweak.
dalvik.vm.heapsize=(amount in mb, e.g 48m)
Defines the Dalvik Virtual Machine Heapsize for games to run better.
ro.sf.lcd_density=(0-999, Galaxy R default is 240)
Defines the LCD density (in dpi) for your device. It's recommended not to change your density for Samsung phones as they will cause problems with your phone's Dialer service.
wifi.suppliant_scan_interval=(time in seconds, e.g. 60)
Defines the time taken to scan for new WiFi networks if no open networks are found. Setting the option higher may save more battery as it scans lesser.
persist.sys.camera-mute=(0 or 1)
Turns off the camera shutter sound (Be careful with this, it may be illegal in yoir region!)
You can also try this suggestion by pudup:
pudup said:
To disable the camera sound, there's a few things you can do.
1. This one is kinda annoying but if the sound annoys you more, you could just put your phone on silent or hold the volume down button until the volume is off. The camera shutter sound shouldn't be heard.
2. Download an alternate camera application. Eg. LGCamera.
3. Wait for the CyanogenMod 7 rom. That has the option to disable the sound in it's settings.
Click to expand...
Click to collapse
0 to turn sounds, 1 to turn off sounds.
video.accelerate.hw=(0 or 1)
Enables hardware decoding of videos. Only for video formats natively supported by phone.
0 to disable, 1 to enable.
ro.ril.hsxpa=(0, 1, 2 or 3, default is 1)
Determines the speed of your HSUPA.
0 = HSUPA disabled (very slow upload)
1 = Stock HSUPA enabled and capped (slow upload)
2 = HSUPA enabled but capped (good upload)
3 = HSUPA enabled and uncapped (best upload)
Q6: Does this phone support overclocking? I feel that I'm not getting the most out of this phone :/
A6: Yes this phone does support overclocking. The kernel by ardatdat should be in the Development section. It even supports undervolting to save battery!
Q7: Why is there a yellow triangle below "Samsung Galaxy R GT-i9103" on boot?
A7: That's because you probably flashed a non-stock kernel through Odin3. Try reflashing a stock ROM and use CWM to flash the phone next time.....
cooleagle and I will add more info to come
Guides:
Guide 1: How to make use of ADB (Android Debug Bridge) for debugging and testing
By now, you all should've known that Android makes mistakes. Actually, not just Android. EVERYONE makes mistakes. Well, for this case it's something going wrong with a game, or just something wrong with a ROM.
The developers @ Google were smart enough to make this logging binary called
Code:
logcat
and it logs everything going on inside Android, from bootup, to dexopt, basic processes and even to shutting down!
There are 2 ways of accessing Android's logcat:
WAY #1: Using Terminal Emulator
Requirements:
A working phone that boots
Rooted with Superuser
Advantages:
It allows debugging without a computer, unlike the 2nd way.
Terminal Emulator is easily downloadable from Google Play: https://play.google.com/store/apps/...251bGwsMSwyLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
Disadvantages:
It's harder to debug using the phone, especially if it is stuck at the bootanimation or splash screen.
Root is needed otherwise you will get
Code:
logcat: permission denied
in the terminal
Steps:
Download Terminal Emulator from Google Play or the link above
Once you've entered it, type in
Code:
su
using the virtual keyboard
Allow it in the Superuser prompt
Then go ahead and type
Code:
logcat
, you will see a bunch of crazy things.
If you want to save a log, do:
Code:
logcat > /mnt/sdcard/logcat.txt
WAY #2: Using Windows/Ubuntu for logcat using the Android SDK (Software Development Kit)
Requirements:
A computer running Windows/Linux or other distros
The Android SDK must be installed: http://developer.android.com/sdk/index.html
Android USB cable (for connecting the phone to the computer)
An Internet connection
Advantages:
Allows debugging using the computer for more accurate findings
Allows logging much better than the method in Terminal Emulator
Ubuntu allows live copy/paste in its Terminal so there is no need to save a log.txt file
Disadvantages:
It uses the Internet to download the required packages
You need a USB cable to connect the phone
If the USB cable/port is malfunctioning logcat will not work
This is more complex than the phone method as it requires you to set a path in Windows's environment and in Ubuntu's .bashrc if you want to be able to use it in the Terminal/Command Prompt at any time.
Steps for Windows:
Launch the Android SDK Manager in
Code:
32-bit Windows:
C:\Program Files\Android\android-sdk\SDK Manager.exe
64-bit Windows:
C:\Program Files(x86\Android\android-sdk\SDK Manager.exe
Wait for it to finishing loading all the repositories
Install the Android SDK platform-tools and let it finish its install
You have now installed the Android SDK's Platform Tools, which is in
Code:
C:\Program Files\Android\android-sdk\platform-tools
and it contains the Android Debug Bridge (adb.exe), which fits this description:
The adb tool has moved to platform-tools.
If you don't see this directory in your SDK, launch the SDK (execute the android tool) and install "Android SDK Platform-tools"
Please also update your PATH environment variable to include the platform-tools/ directory, so you can execute adb from any location.
Click to expand...
Click to collapse
To test whether adb will work, run Command Prompt and go to the folder described above , respective for 32 and 64-bit.
Run:
Code:
adb logcat
and if it works, the same crazy code will be there
TO BE CONTINUED
GALAXY ‘ROYALE’ FAQ's:
(More than 25 Questions are already here & more to be added with solutions if & where required. )
THOUGH ENOUGH CARE HAS BEEN TAKEN TO CHECK THAT THE INFO GIVEN HERE IS CORRECT, BUT USE IT AT YOUR OWN RISK & IT HAS BEEN PROVIDED AS IT IS. NEED INPUTS FROM OTHER FORUM MEMBERS TO POINT & CORRECT MISTAKES IF ANY. REQUEST HERE IF ANYONE WANTS TO ADD MORE QUESTIONS. THANKS.
Q. What is the Samsung’s Model Code for our device?
Its GT- i9103.
Q. What's resolution of the screen of Galaxy R ?
It has a resolution of 480 x 800 pixels (Same as Galaxy S2)
Q. I want to see the internals of Galaxy R?
Head to => Thread
Q. What is a Android, ROM, Kernel, Superuser, Root, Governer ?
Check out this thread if you want to learn about basic Android terms & acronyms & also about the hardware terminologies / arcronyms: Android Definitions & Terms
Q. Does Galaxy R have a locked Boot loader?
No, it isn’t locked and you can flash custom ROMS & Kernels, but do read the terms and conditions & instructions before rooting/ flashing as it can void your warranty.
But there’s a workaround to unroot it & flash it back to the stock ROM & kernel to give it for repairs. Gather all the information required before rooting and root it only after you are confident of rooting it as its better be safe than sorry and brick your Galaxy R.
Q. WTH my Galaxy R shows only 4GB internal memory free? Samsung fooled me!
No, Samsung did not make a fool out of you.
It actually has 8GB internal storage which is divided as follows:
2GB ROM + 2GB for applications + 4GB user available.
Q. WTH my device shows only 724MB RAM available but I was promised of 1GB! I will sue Samsung!
Don’t sue Samsung you’ll surely make a fool of yourself.
Some part of the RAM is used by the OS & GPU and isn’t available to the user.
Q. Will Galaxy R get ICS 4.0 update & When?
According to an Official Announcement by Samsung, Galaxy R will be updated to ICS 4.0 but there’s no specific date announced but general opinion is around Q2 - Q3 of 2012. You can keep a track of the developments & rant on this thread: Track the Release of ICS 4.0 on Galaxy R / Z i9103
Q. Which Data protocols does Galaxy R support?
HSDPA 21.1MB/s, HSUPA 5.76 MB/s, Wi-Fi b/g/n, Bluetooth 3.0 EDR, Wi-Fi Direct.
Q. What audio formats does the Galaxy R support natively?
Formats Supported: FLAC, MP3, OGG, AAC, AAC+, eAAC+, etc
Q. What video formats & resolution does Galaxy R support for Video Playback?
Formats Supported: MP4/DivX/XviD/WMV/H.264/H.263
Resolution Supported: 1080p low birate videos(Using free Dice Player) & 720p videos.
Q. Which Games can I play on Galaxy R ?
It has support for playing many Games as it’s a TEGRA 2 device. Specially games available on www.tegrazone.com , the one’s available in Samsung’s Game Hub, the ones designed by Gameloft & Electronic Arts(EA).
Q. Does it support USB On-The-Go as I didn't get a USB OTG cable in the box?
Yes it does but you’ll have to buy the cable separately. Galaxy R supports connecting Pen Drives, Mouse, Keyboards & Card Readers.
Q. Does Galaxy R support MHL?
The TEGRA 2 chipset does support MHL natively, but Samsung has disabled it due to unknown reasons, so hang in there till our devs find a solution/mod for enabling it.
Q. Does Galaxy R support Video Calling using the front camera?
Yes it does. You can video call using a 3G network or without costing a dime by using free apps like Skype, Fring, V-Tok, etc.
Q. Does Galaxy R support multi-touch?
Yes it does & has up to 5 finger multi-touch support.
Q. Which sensors does Galaxy R have?
It has:
GPS
Magnetic Sensor
Proximity Sensor
Gyroscope
Light Sensor
Accelerometer
Battery Temperature Sensor
Q. My friend's iPhone has got ‘Siri’ Voice Command support, why doesn’t my Galaxy R support it?
Hold your horses, it does. Amazing right?
It can take Voice Commands using the inbuilt Vlingo app. (Double tap home key to launch.)
Sending SMS/Email by dictating the text.
Calling/Redialing any person.
Playing a specific song from your playlist.
Dictating & saving notes / memo.
Navigating/Asking for directions using Maps.
Search the Web, go to any website.
Playing Radio & Settting Alarm.
Update Facebook & Twitter status.
Open any app.
Record your voice.
Checking your schedule.
Q. I can’t get a proper figure for my 3G/2G data usage on my network using any app from the market or elsewhere!
Yes it’s a known issue for devices on stock kernel. It can be solved by using ardatdat’s kernel as it has a fix for that or wait hoping that Samsung solves it in the next update.
Q. Does Galaxy R have any freebie Apps & Games from Samsung?
Yes it does ! There are so many available just go to Samsung Apps(Application) in your Galaxy R to get the full list. Specifically Modern Combat 3(by Gameloft) & Dead Space(by EA) are available for free.
Q. Can I retrieve my Galaxy R & protect my personal data if God forbid it’s lost?
Yes, you can but it depends on many variable factors to get a lock and use all the available features. It natively supports it by using Samsung Dive to:
Track your mobile.
Ring your mobile.
Send an SMS if the SIM is changed to a pre-defined number.
Erase all your Personal Data on the mobile.
Q. My Galaxy R has freezed/hanged ( It’s mostly due your antics or some app specific bug and not due to the device’s fault as it normally does not hang even on heavy usage ) What to do?
Hold the power button for more than 7 secs and it should automatically restart.
Q. Can I flash Custom ROMs?
Yes you can use Odin or ClockWorkMod(CWM) to flash them but beware you can lose your warranty.
Q. Does flashing increment my counter?
Yes & No. Wondering how both are possible? If you flash using Odin then it increments your counter but if you flash using CWM packages it doesn’t, so it depends on the method you use. But flashing a rooted / custom kernel will increase your counter even if you flash it using CWM.
Q. My device is DEAD & shows APX mode driver required on connecting to my PC! What to do?
You are lucky! Here’s a solution to it. Head to => LINK
Q. My device is not being detected on being connected to my PC but I can charge it via the wall / normal charger ! What to do?
First of all check if you have the latest Samsung Kies software installed as it also installs the latest Samsung USB drivers along with it which are required to connect your device to the PC. If they are installed & still your PC doesn't detect the device then you probably have corrupted drivers. To resolve this follow these steps: Uninstall Samsung Kies / Samsung USB drivers currently installed => Restart your PC => Reinstall Samsung Kies / Samsung USB drivers.
Q. I can't charge my device & my device is not being detected after connecting to my PC & Odin is not detecting my device ! What to do?
(The solution is valid only if you are experiencing all of the above conditions simultaneously)
Checkout this thread which could help you: => [Partial Fix] Galaxy R not getting detected on PC nor charging via a charger.
Q. I didn't backup my /efs folder and my IMEI is messed up ! Is there any way I could recover my IMEI number ?
There is a GUIDE to recover your IMEI for Samsung Galaxy S2, as being from the same manufacturer there is a chance that it may work but there is not guarantee that it'll work, you are going to use it completely at your own risk (it may hard brick your handset). I am not aware if any member was able to recover Galaxy R's IMEI using this method.
So if you willing to take the risk then Head To => Thread & do tell us if were successful in recovering your IMEI by following a particular procedure.
Q. Which Custom ROMs are available for Galaxy R?
Infected ROM v2[2.3.6][ZSLE5]
TitaniumS ROM v2.1[2.3.6]
TheFrankenstein MOD^1.1[2.3.6][ZCLA]
NeoROM v2.1[2.3.6][ZSLE5]
NeoROM v3.0[2.3.6][XWLA4][AROMA]
Anatasia ROM[2.3.6]
Turkbey ROM[2.3.6]
MaZel ROM v 1.1 [2.3.6][XWLA4][AROMA]
Q. Which ROMs are being developed for Galaxy R?
[DEV] CyanogenMod Project - Epsylon3 Nightlies
AOSP Build (No new developments)
Q. Which Custom ROMs do we want?(State it and I’ll update it here )
CM9, MIUI, AOKP, AOSP, PARANOID ROM & any other ROM with better features and functionality!!
So if you are a dev then kindly help or if your friends are developers don’t forget to request them to make it available for our device !
Q. Which Custom Kernels are available for Galaxy R?
ardatdat’s Kernel v1.8.3
Cranium Kernel
Ultimate Kernel
If any of the above helped please don't forget to appreciate by hitting 'Thanks'.
REGARDS,
‘cooleagle’
GALAXY 'ROYALE' HOW To's:
Q. How to connect my device in mass storage mode?
Here’s what you need to do, go to Settings => Wireless & Network => USB utilities => Click on ‘Connect storage to PC’ => Connect USB cable => Done.
Q. How to use my device’s internet by Tethering on my PC?
Here’s what you need to do, go to Settings => Wireless & Network => Tethering & portable hotspot => Connect USB cable => Click on to enable ‘USB tethering’ => Done.
Q. How to disable the annoying camera sound on Galaxy R?
You have two options:
Put the handset in 'Silent mode'.
Install any other Camera app from Android Market/Play Shop, e.g lgCamera, Cymera, etc
Q. How to Backup my apps and data on Galaxy R?
You can use ES FileManager/ Astro File Manager(free & no need for root to backup apps), Titanium Backup Pro(needs root but has much better functionality.)
Q. How to take a screenshot in Galaxy R?
Press the HOME + POWER keys simultaneously to take a screenshot. After that check the 'Gallery' it should automatically update & show your screenshots.
Q. How to find Easter eggs in Android ?
Here’s what you need to do, Go to Settings => About Phone => Repeatedly hit on the field 'Android version' => You'll get an image which is your Easter egg.
Q. How to install CWM on Galaxy R?
Q. How to flash stock ROMs using Odin ?
Q. How to reset my counter back to zero?
Q. How to get a logcat dump & install ADB?
Q. How to configure Samsung Dive?[FONT="][FONT="]
[/FONT]Go to www.samsungdive.com. Create a Samsung account/Login with an existing one and configure it.
Q. How to block the ADs in my Galaxy R?
You could try any of the free apps available in the Android Market/Play Shop which block ADs.(For e.g. AdFree app)
Q. How to install Indian regional fonts on other ROMs(only for XWLA4 based ROMs)?
Same method may work for other regional fonts also, so you can try it at your own risk.[/FONT]
Q. How to make an USB jig at home at your own risk of damaging anything or everything?
Check out this => Video(YouTube)
Q. Links to various Developer Guides if you are interested in developing for Galaxy R
Q. HOW TO REPAIR A BRICKED GALAXY R / Z i9103
Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phone <= Skip the first 7 posts for instructions.
Unbrick, Downgrage bootloader to 2.0 / Reset custom firmware counter without using an USB jig on Galaxy R i9103(But be careful).
Files that you may need to bring back your Galaxy R to life & give it to the Service Center (flashed via CWM, have been uploaded by XDA member pankaj88):
Stock Recovery
Unroot
GALAXY 'ROYALE' MODs:
Q. MOD to change boot animation of Galaxy R?
Some custom boot animations have been uploaded in this Thread.
Q. MOD to add 14toggle, CRT Off, Battery % to Galaxy R ?(Designed for deodexed XWLA4 but works on some other ROMs too)
Q. MOD to swap internal & external SD memory for Galaxy R?
Q. MOD to activate BLN(BacklightNotification) for Galaxy R?
Currently we don't have any MOD or info(we also need a kernel with some modifications for it) for adding this MOD to Galaxy R. You can request the developers to create one/create one yourself and post it in our forum if possible.
[FONT="]If any of the above helped please don't forget to appreciate by hitting 'Thanks'.
REGARDS,
[/FONT]‘cooleagle’
Good job guys, lots of good information. This thread is now stuck!
Thanks cooleagle !
Herpderp Defy.
GALAXY R KNOWN BUGS & SOLUTIONS:
3G / 2G Mobile Data count applications don't function correctly.
Can be solved by using a custom kernel which has this bug fixed.
Date & Time of the handset changes randomly even when it's set to update automatically according to the network.
Go to Settings => Date & Time => Uncheck & then Recheck 'Automatic' to re-sync with your carrier's / service provider's time & date. No known solution which permanently resolves the issue.
The person at the other end can't hear you at all / Headset Jack bug
Sometimes after unplugging your headset you experience problems while making a call, usually a reboot solves the problem but sometimes it doesn't. It can be identified by the following symptoms: When you're making a call, the person at the other end can't hear your voice but you can hear them clearly / you pick up the call then you can't hear any voice & the person can't hear you either.
It's most probably a software bug as the handset thinks the headset is still attached to the handset & routes the call as if it were being made when a headset would have been connected. But in some cases it could also be due to a hardware problem i.e a faulty 3.5mm headset jack.
To confirm if this is the problem you are facing:
- Plug in Samsung's headset & make a call to check if you can communicate / talk with the person at the other end normally & without any problem.
- If you can talk normally then it's confirmed that it's due to a software bug if not then it could be due faulty 3.5 mm jack.
To resolve it:
- Update your firmware to the latest version available even though it may not be for your region as it could have possible fixes. i.e (ZSLE5 / ZSLE6 / Latest firmware of any region)
- Plug in & out the headset a couple of times while playing music till it gets resolved i.e when the firmware understands that the headset has been removed & then it'll work normally.
- You can also take it to a service center where they could replace the headphone jack & may also reflash the stock firmware which should resolve the problem if it's due to a faulty 3.5mm headset jack.
[FONT="]If any of the above helped please don't forget to appreciate by hitting 'Thanks'.
REGARDS,
[/FONT]‘cooleagle’
If I may suggest something, I would change: 4GB of internal memory storage to
"8GB of internal memory storage (2GB ROM + 2GB for applications + 4GB user available)"
m.kochan10 said:
If I may suggest something, I would change: 4GB of internal memory storage to
"8GB of internal memory storage (2GB ROM + 2GB for applications + 4GB user available)"
Click to expand...
Click to collapse
Sure I'll ask Emo to update it his post.
Any need for modification just ask here , there's no need to PM
Herpderp Defy.
Updated with build.prop tweaks
Herpderp Defy.
FAQ's Added . . . !
How To's Added . . . !
If you have any suggestions or if you find any inaccuracies post it here I'll update them.
Silent camera?
i'm on Titanium ROM v2.1
when i turn off the system sound, the camera is silent!
Guys help needed on how to turn off the camera's shutter like sound.
Is there any Mod for the same ?
bboykang said:
i'm on Titanium ROM v2.1
when i turn off the system sound, the camera is silent!
Click to expand...
Click to collapse
Thanks I'll update it in the FAQ but it'll be only Titanium specific.
But if there's a universal method for all the ROMs and even on rooted stock it would be more helpful.
Capturing screen shot.
Hi,
We can capture the screen by pressing power and home button at a time, can you please add this.
bboykang said:
i'm on Titanium ROM v2.1
when i turn off the system sound, the camera is silent!
Click to expand...
Click to collapse
Possible reasons
1) Your camera shutter sound is silent
2) There's a setting which allows silencing of camera shutter
3) Build.prop tweak
Herpderp Defy.
mj.vikram said:
Hi,
We can capture the screen by pressing power and home button at a time, can you please add this.
Click to expand...
Click to collapse
Yes sure, I am going to add a few more questions so I'll add it with them.
EmoBoiix3 said:
Possible reasons
1) Your camera shutter sound is silent
2) There's a setting which allows silencing of camera shutter
3) Build.prop tweak
Herpderp Defy.
Click to expand...
Click to collapse
Hey man can we tweak build.prop to make the camera shutter sound permanently silent even on stock rooted handsets?
If yes then can you include how to do the same in your first post ?
Holy awesome posts batman!
Great work in here guys
EmoBoiix3 said:
Possible reasons
1) Your camera shutter sound is silent
2) There's a setting which allows silencing of camera shutter
3) Build.prop tweak
Herpderp Defy.
Click to expand...
Click to collapse
the shutter volume changes with the system volume in the sound setting.
OR
u can rename/delet "Shutter_01.ogg" to get rid of the shutter sound
but i cannot find the focus lock sound, that must b with Camera.apk or something...