[SCRIPT] Lager - Untethered background logcat logger - Kindle Fire Android Development

Okay,
This is a super simple script that continually saves the output of 'logcat' to file so there will be a record of what happened on your device in case you are forced to reboot. It's possible this will lead to identifying the cause of some SODs.
Requirements:
* Android Terminal Emulator (or equivalent app)
* Root privileges
* bglager.zip
Instructions:
* Download and unzip bglager.zip to your data directory
* Launch the Terminal Emulator and enter the following commands:
Code:
cd data
su
sh lager
Afterwards, just press the 'home' or 'back' key and go on about your business.
What you need to know:
* Most, if not all terminal emulators will run in the background until you explicitly close or kill the app. There should be an icon in your notifications bar to indicate the emulator is running. As long as the emulator is running, the script will be running also.
* It will run in the background and you can use your device as you normally would, but it will be run in active memory. I'm not sure how much of your resources will be required to run it but I'm sure it won't be too noticeable...if at all.
* The script takes the output of logcat and saves a new file for every 1000 lines logged. Each file saved averages between 80 and 100 kB in size. The number of files saved in an hour will vary depending on usage. Keep an eye on your /data folder to get an idea of how much space will be required to run over a period of time and to make sure it doesn't eat up all of your internal storage. This shouldn't be too much of a problem and you can easily go several hours (probably overnight) without worrying about it. The files will be saved in '/data/cat-logs', so if needed, delete the oldest ones to make more room. Again, this shouldn't be much of a problem...just don't forget that it's there. I'll be working on a way to zip the files and shrink them down to around 5 - 10 KB each, but this will work for now.
* The script will still work while the device is asleep, but rebooting will definitely kill it. If you reboot or for some strange reason get a terminal emulator FC, start up the terminal and run the script again.
* Don't post your logfiles in the forums. They may contain sensitive information that you wouldn't want to get into the wrong hands. Take the last one or two logfiles saved (or more, depending on the Developer's needs) and send a PM or email to the respective Developer, if requested. No spamming, please.
I don't suggest anyone use this script just for the hell of it. It's intended for people with SOD or similar issues that would prevent logcat to be run normally. Hopefully this will be a useful tool in helping the Developers get to the root some major problems.
Developers:
Obviously this is a simple script and the same idea could probably be implemented for kmsg, cpu stats, or any other rolling logs or messages. Let me know if you think anything like this would be helpful and I'll see if I can work something out. Plus it will give me a chance to learn more about Android and shell scripting.
Update: 12.13.2012
I've updated the script to compress each file that hasn't already been compressed, once every hour. If you're running the original release of this script, shut down the terminal running the script, replace it with the new one and run it as before. With compression, one could easily go several days and lose no more than 20MB of storage. Without compressing the files, that number could easily be nine times that amount and your internal storage can be eaten up pretty quickly. Please update if you plan on running this script for any considerable length of time. (download link has been updated accordingly)
Download:
* bglager.zip

Super soupy!

Thanks, downloading now. One question/suggestion.... might it make sense to create new files after every 100 or 200 output lines instead of 1000, since presumably the script won't be able to run once the SOD has occurred?
I may try editing the script myself to make that change, if it's clear in the script.
Thanks!
Sent from my Amazon Kindle Fire using xda app-developers app

waffull said:
Thanks, downloading now. One question/suggestion.... might it make sense to create new files after every 100 or 200 output lines instead of 1000, since presumably the script won't be able to run once the SOD has occurred?
I may try editing the script myself to make that change, if it's clear in the script.
Thanks!
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
It creates a file, fills it up line by line until it gets to 1000, then creates a new file. The last file will have the most recent events.
Sorry for the confusion.
"That's a special kind of stupid. The kind that makes me laugh."

Ah, great, so it doesn't wait until the log has a 1000 lines in it before writing to the file.
Running it now, we'll see what happens.
Thanks for putting this together..
Sent from my Amazon Kindle Fire using xda app-developers app

Script and OP updated.
Please take a look if you are already running the script.

Soupy,
Do I need to modify anything in particular to get this working on my Samsung GT-N7000?
Sent from my GT-N7000 using Tapatalk 2

asf58967 said:
Soupy,
Do I need to modify anything in particular to get this working on my Samsung GT-N7000?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Oh wow, I forgot all about this.
No, as long as you have write access for your data folder, it should work just the same.

You should repost this in general dev
Sent from my GT-N7000000000 using Tapastalker 2

Related

[APP] Apps2NAND - fast data access - choose what to move! [added support for Froyo]

I think this better to be posted to Galaxy S I9000 Android Development.
So I posted it once more at here:
http://forum.xda-developers.com/showthread.php?p=7694817#post7694817
Board Admin, please feel free to delete this.
Hi all,
I took so many from here. It's time for me to contribute little to the community.
The lag issue of Galaxy S bother many ppl.
I tried many different method.
Yes the lag issue was improved and Quadrant score is higher.
But there are always some weird things happen... like sudden lag/black screen.
After I upgraded to firmwre I9000ZSJH1, the lag issue is improved a lot!
But still, there are rooms for improvement.
So I wrote a cmd which will help to generate a .sh file, which will move apps data stored under /data/data/ to the internal NAND memory (/dbdata/data) for faster access.
The Galaxy S built in 1xxMB of fast access NAND memory. It is a waste if we don't utilize them.
However, it is impossible to move all apps' data to the tiny NAND memory.
So here is a tool for you to customize what app's data you want to move.
Recommand to move the core Android apps and the apps that you use frequently.
Like Dialer, Contacts, Dolphin Browser, Facebook, Astro File Explorer......
Steps :
1. open [1.app.list.xls] and edit colume A and B.
colume A should be the data folder name of the apps you want to move.
colume B is the name of the apps (optional)
2. after you've done, simply "copy & paste" everything onto a notepad and save it as [2.apps.list.txt]
3. fireup the [3.Apps2NAND.cmd]
4. within few sec, a file [App2NAND.sh] will be created.
5. use Gscript to load and run the App2NAND.sh file. (the script requires root access. so make sure you have it!)
For experienced user :
Step 1 actually is just for user to manage the apps more clearly.
A user with little cmd knowledge may know the script only requires [2.app.list.txt] to work with.
You can skip Step 1 and directly go to Step 2 to edit the file.
The format should be { app data folder name + <tab> + app name }
Remarks :
Apps that moved to NAND may not be restore with Titanium Backup.
App link will be broken by doing so.
(I also include Linpack and Quadrant to the app list to cheat higher benchmark scores . You may remove it if you don't want to.)
Apps2NAND - fast data access - choose what to move! [added support for Froyo]
update 18 Nov 10:
Found some friends here still want to use this "old school" lagfix
1st of all, thanks to your support.
When I wrote this script, it was still the golden age of Eclair (2.1). So the script is definitely not prepared for Froyo (2.2).
However, just by changing few lines can make this script survives on Froyo. So here I updated a script for Froyo (apps2nand.Froyo.zip).
I haven't tested it since I am very satisfied with the [Spike Speedy Edition v3.0 OC], which comes with more advanced lagfix options (sztupy).
(I wrote something that even myself don't use now.... So it's really suprised and appreciated~)
But this script still has it merit ~~~~~~~~~ simple!
(and battery friendly, just a feeling~ no actually statistic~)
If you are interested in antique and brave enough, try it on Froyo. And let me know if any issues. I will try my best to fix.
===================================================
update 18 Aug 10:
Now included Installation and Uninstallation for this script.
Tried several times on my i9000 and it works.
Please read and follow the readme.txt inside the zip.
One tricky part for this script : it will failed when SU permission is not allowed in time during the script is running.
I have pause the script with 10 secs for you to allow the SU on i9000.
Make sure you allowed it.
If you failed to do so, no worry. it won't change anything.
Just simply re-run the script again.
===================================================
Hi all,
I took so many from here. It's time for me to contribute little to the community.
The lag issue of Galaxy S bother many ppl.
I tried many different method.
Yes the lag issue was improved and Quadrant score is higher.
But there are always some weird things happen... like sudden lag/black screen.
After I upgraded to firmwre I9000ZSJH1, the lag issue is improved a lot!
But still, there are rooms for improvement.
So I wrote a cmd which will help to generate a .sh file, which will move apps data stored under /data/data/ to the internal NAND memory (/dbdata/data) for faster access.
The Galaxy S built in 1xxMB of fast access NAND memory. It is a waste if we don't utilize them.
However, it is impossible to move all apps' data to the tiny NAND memory.
So here is a tool for you to customize what app's data you want to move.
Recommand to move the core Android apps and the apps that you use frequently.
Like Dialer, Contacts, Dolphin Browser, Facebook, Astro File Explorer......
For experienced user :
Step 1 actually is just for user to manage the apps more clearly.
A user with little cmd knowledge may know the script only requires [2.app.list.txt] to work with.
You can skip Step 1 and directly go to Step 2 to edit the file.
The format should be { app data folder name + <tab> + app name }
Remarks :
*** Apps that moved to NAND may not be restore with Titanium Backup. App link will be broken by doing so.
*** Please make a nandroid backup before apply this!
*** I am not responsible for any damage caused by this script.
(I also include Linpack and Quadrant to the app list to cheat higher benchmark scores . You may remove it if you don't want to.)
Is NAND where devices like HTC Desire and Nexus One store their Apps?
well this is almost what paul did some days after the phone got released...
lyno said:
Is NAND where devices like HTC Desire and Nexus One store their Apps?
Click to expand...
Click to collapse
Yes, which is why they needed APPS2SD in Froyo.
So....when are you posting the script?
If you want I'll create a program that spits out the .txt file rather than do it in excel, copy paste etc.
Jonas.M said:
well this is almost what paul did some days after the phone got released...
Click to expand...
Click to collapse
yes. that's what Paul did as I mentioned in my script.
But he simply push everything to NAND which oneday, you will find out of space.
Using my script, you can decide what to move, depending on the frequency of the apps usage.
lyno said:
So....when are you posting the script?
If you want I'll create a program that spits out the .txt file rather than do it in excel, copy paste etc.
Click to expand...
Click to collapse
the script is updated and posted.
the excel is just for user to maintain their app list easily.
my script only works with the txt file.
you may skip the excel part if you like.
and thanks for your offer, lyno.
Is it possible to make a script that automatically moves smaller apps to the nand?
I mean it's not worth moving large games, but anything under 2MB should be considered.
Maybe use some intellegent calculation, if all the apps under XMB use less than 50% of free space on nand, increase X until it is efficiently used up.
Also there is HEAPS of space to be freed in NAND, delete stock ringtones, and other.
seems great
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
What happens if an app in the list is not on the phone, does it just skip it?
sturmeh said:
Is it possible to make a script that automatically moves smaller apps to the nand?
I mean it's not worth moving large games, but anything under 2MB should be considered.
Maybe use some intellegent calculation, if all the apps under XMB use less than 50% of free space on nand, increase X until it is efficiently used up.
Also there is HEAPS of space to be freed in NAND, delete stock ringtones, and other.
Click to expand...
Click to collapse
MiG123 said:
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
Click to expand...
Click to collapse
sturmeh, that requires more complex scripting skills, which is out of my knowledge...
and I think instead of choosing the apps2NAND depending on size, I think the "Frequency" of using the apps may be more appropriate.
e.g. I use TouchPal IME a lot. So I move it to the NAND.
Now when I type, TouchPal act lightening!!!
MiG123, I haven't done a serious comparison. But as I remembered, Apps2NAND gives me more "smooth" feeling.
Actually, you shouldn't compare Apps2NAND to other Apps2SD or EXT.
Since Apps2NAND only offers you around 1xxMB of app storage space. Way too far from the others experts' methods.
I suggest using this is because I am using the latest 2.1 ROM, I9000TGYJH1 (http://www.multiupload.com/UTKSZPTKCG), which the lag problem seems improved a lot. But on top of it, I don't want to waste that 1xxMB of internal RAM, so I introduce this method.
To let user choose what core apps that should be put into NAND so
- space is not wasted.
- certain apps enjoy even faster response time.
lyno said:
What happens if an app in the list is not on the phone, does it just skip it?
Click to expand...
Click to collapse
yes.
the script will skip the apps that is not in the list.
MiG123 said:
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
Click to expand...
Click to collapse
Definitely, the hardware is multitudes faster.
Where's the file? Can't seem to find it on the first page
Anyhow. Do you symlink the old location to the new location, thus being able to keep the link intact? That should sort out any problems with backup solutions such as Titanium Backup.
How do you find the app's data folder name?
mekwall said:
Where's the file? Can't seem to find it on the first page
Anyhow. Do you symlink the old location to the new location, thus being able to keep the link intact? That should sort out any problems with backup solutions such as Titanium Backup.
Click to expand...
Click to collapse
lyno said:
How do you find the app's data folder name?
Click to expand...
Click to collapse
mekwall, sorry. removed by mistake.
have uploaded back again now.
yes. it uses symlink method (from Paul's concept) :
ln -s /dbdata/data/appsname /data/data/appsname
i dunno how's Titanium Backup works but it just failed to restore any apps that has used Apps2NAND...
that's why i provide the Uninstallation method to restore it back and then run Titanium Backup to backup all apps and data.
lyno, you may try the Astro File Explorer (market).
It has a function to backup the installed apps out to /sdcard.
The name of the backuped apps will be named exactly the same as it's data folder name.
e.g. Brut's Google Map -> brut.googlemaps.apk
this whoe procedure demands root-access, right?
yes. since it involves moving folders between /dbdata and /data.
Sent from my GT-I9000 using XDA App

IHO Poo Remover rev5 - 20110824

Should work for all Optimus V GB ROMs (aosp & IHO variants)
steps to modify:
extract
edit remove.sh script*
zip
sign
*works best in a unix editor. Notepad++ & Windows notepad sometimes screw with shell scripting handles new line something-or-other. In Windows I've used another free app Jedit for editing it and it seems to not give me 'installation aborted' msgs when installing the zip.
IHO Poo Remover rev5 (link updated)
comments on Email.apk: personally, I use it because it not only connects to Exchange servers but Hotmail email/contacts/calendar syncing can be set up directly in account settings with it there. instructions
Pls extract the zip & look at the remove.sh to see what I'm removing because I have my opinions. You can comment out & zip it back up to your tastes. If you have a variant you've made go ahead & post a link to it. Nice to compare what we each prefer.
In regards to ringtones & notifications I remove all but a basic ringtone. You can either add your own into the script- just drop them in the ringtones & notification subfolders or put additional ringtones on your sdcard in a folder made and named 'ringtones'.
Other notes is it removes a bunch of languages & adds a smaller English language.
I left in CMStats because I want Cyanogenmod to know we use it.
Don't know what Pacman.apk is so I have it commented out. May remove it if I figure out what it is.
Source on safe to remove apks and their purpose on Cyanogenmod wiki
rev5-
removed the sqlite tweaks as they didn't really do much on the IHO ROM
added removal of bootsound since it's an annoying idea
That SQLlite binary patch looks interesting. Looked at the source page, and they only have the /system/lib/libsqlite.so included, while your .zip includes /system/bin/sqlite3 too. I don't see a /bin/sqlite3 currently on my phone, what is the 2nd bin for?
jawz101 said:
Don't know what Pacman.apk is so I have it commented out. May remove it if I figure out what it is.
Click to expand...
Click to collapse
Pacman is run one time only. When you first sign into the market. It offers to download all the google apps at once. i.e. Maps, Facebook, Voice, Youtube, etc. I find it useful; since I use most of what pacman offers up. Hope that helps. I'll defiantly have to try poo remover. Love that name BTW.
I guess I left that part out, Whyzor. I'm pretty sure it's useless on its own but among these tweaks is a command that will vacuum the sqlite databases contained on the phone. I guess those that use those scripts would benefit from it most. I may take that piece out since I don't think it's being added completely (maybe not chmoding) because I end up having to run the chmod by hand sometimes. I could be wrong though and it may work.
Anyways, to actually use the sqlite3 you'd need a script like this one from FranciscoFranco, adjusted by mmarz . there's a portion of this script that vacuums the phone's databases. real-world benefits? It's likely negligible at best but I just threw it in there.
If you are ever interested I'd follow anything FranciscoFranco & Ungaze do- they're Optimus One tinkerers but they're obsessed with performance. Really anything they do is applicable to Android in general. Franco's Optimus One ROM is insane (xda) (github source)
I just replaced the /system/lib/libsqlite.so from the source thread you posted, set permission to be same as the other binaries, rebooted. Ran RL Benchmark and got the same, around 93 seconds overall score (using 245-600 ondemand CPU, IHO CM7.1. Are you getting the same performance?
UPDATE: If I overlock to 806 Mhz, was able to drop the overall time to 71 seconds, went back to original libsqlite.so and at the same clock speed, takes about 81 seconds. The performance gain is negligable given the corruption risk (and according to Blarf in the IHO thread, properly written apps won't see much of a benefit anyway).
yeah I'll probably take that out. It gave a noticeable improvement when I ran aosp. May also be that I'm not applying it correctly with this zip.
on aosp the RL Benchmark went from around 80 seconds down to maybe 45 seconds for comparison.
Probably best just have this as purely a bloat remover. Regardless, having it in there isn't messing anything up so this is still safe to use.
First off I love the poo remover. However, every time i edit the script, zip the package back up again, and sign it and then try to apply it the installation keeps getting aborted with CWM.
I have followed the instructions for windows, including using Jedit, and i have even tried with my macbook using a terminal session with pico.
i do sign the zip files also.
should i not include the stock folder META-INF in the altered script?
any help is greatly appreciated
that's usually what gets me is the editor I use to edit it with. I'd assume a macbook would be fine for editing it.
I usually remove these 3 files from the meta-inf folder before resigning as they get regenerated with that signing program (cert.rsa, cert.sf, manifest.mf). I don't know if that would affect anything but I've just been doing that out of habit.
Fortunately we understand what we're trying to do and really the only thing that's hanging it up is whatever the hiccup is.
It came down to making one change at a time until I got install aborted errors to stop
thanks much i will give it a shot
may want to try just unzipping it and rezipping it to see if that works.
Make sure you're zipping up the contents of the iho zip and not the actual folder.
Try it with & w/o signing it. If it works w/o signing it I'd leave that step out just so you can concentrate on editing the remove.sh script.
Possibly use a command line editor if your mac can do that (never used a mac)
issue is with unix line endings vs. windows/mac line endings
just found something if you're using Notepad++ try going to edit- EOL Conversion & switch it to Unix
i will look for another terminal editor and try that too.
i was originally using pico in the terminal.
when i was doing the editing of the remove.sh, i wanted to install the default ringtones and notifications.
do you think the restore that runs at the end of the removal is conflicting with it? I will give everything a shot today and let you know later what happens.
I'd just take those remove lines and audio folder out, put them in that audio folder, or just have a ringtone folder on your SD card
The restore is just adding stuff back
got it working
it was my stupid mistake of zipping the IHO folder and not the contents of the folder
so when i was signing it it created the META-INF folder and a IHO folder
Everything flashed and worked great
thanks again
I was interested in looking at this, but it no longer exists on mediafire. Any chance you can put it back up?
-John
Yeah.I will put it up tomorrow. It's also good to pm on old threads like this
I've been lazy... updated the post with a new link to the file. Sorry... been really slacking lately :/
It's the same poo remover revision5 from before. again, read the stuff at the top if you want to make changes.
I've honestly not been using my script for a long time but it's nice to have around.

"Fixed" build.prop file for Kaiser (Attached tarball)

!ALWAYS make a databackup.img on your device BEFORE making any changes!
Hi all!
For the past 3 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster. (EDIT: The 3.2Mb/sec is the top of the scale, I actually averaged 2.2Mb/sec with average pings between 300-500 across 3 different radio roms).
VOGUE/POLARIS OWNERS!
Please test this file and report findings here.
IF you find you need to remove any lines, please do so before copying the file into /system. This file works well on the AT&T networks (Cingular), but may not have much effect on other networks.
If you have trouble after installing this file, please post your bootlog file.
PoX
So may I know what rom support this?
This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72**.
I can test this. Perhaps, kaiser on Android could be good for daily use?...
Thanks for sharing
PoXFreak said:
Hi all!
For the past 2 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster.
If there is interest in this, please respond to this post. If there is enough interest I will attach it to this post as a .tar file.
Click to expand...
Click to collapse
PoXFreak said:
This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72k.
Click to expand...
Click to collapse
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.
I can build with Fresh Froyo and try it, but not until April sorry.
I am currently traveling and away from a development system.
I have been slowly trying to get a reliable app2sd capability working.
I'd suggest searching old posts for power collapse to see if dzo or others long ago tried this.
It sounds promising.
muckelmaus said:
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.
Click to expand...
Click to collapse
The "install guide" I'm referring to is here...
How to replace Windows Mobile with Android (Guide)
There would be a change to the original build.prop file which exists inside the /system folder and would be installed when Android is installed on the Kaiser.
Mind you, I live in a busy city with LOTS of cell towers and, since 3g works on the principle of multi-tower usage, YMMV. If you live way out in the country with maybe 2-3 towers nearby, this may not help you.
Also, this has been tested on a NAND-installed OS, not a HaRet install. I cannot verify or guarantee this will work with a HaReT install as I have no way to test it and I think of HaReT as the "slow cousin" to a NAND install.
On a side note: My Kaiser has not had one sleep of death, hard-lock, white screen or even an FC for 9 days now. Apps running out of memory can be a slight problem but they will just close on their own as opposed to FC-ing. at worst I've had one hot reboot called by the system, and the FCs' are few, even with heavy Facebook and Maps use.
n2, if this works on all Kaisers, is there a way to push it to SF and either add it as a mod or rebuild the "system_froyo" install files and incorporate it within?
I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA
I am interested and willing to try this out!
Where is your " "Fixed" build.prop file for Kaiser "?
Tarball added to OP, please test and report back. Any problems should be reported here along with the bootlog from your phone.
Hi guys!
Problem occured when moving file to root folder. To solve I tried root explorer and z4root both. CM7 + Krazy-Killa's Kernel on tilt 8925.
Please talk what to do with it!
thanks!
Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".
n2rjt said:
I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Vogue/Polaris users solicited, although I'm not sure if this can be used on a CDMA network. Last count shows about 15-20% of the "other" phones were Vogues, the rest were Polaris users.
It would be nice to start getting good feedback since this would be my first actual "hard" mod (one that is installed with the system, not modded through some other installer/program).
PoXFreak said:
Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".
Click to expand...
Click to collapse
Can't rename. And can't change file attributions read only to read/write.
ZLodei said:
Can't rename. And can't change file attributions read only to read/write.
Click to expand...
Click to collapse
You probably need to remount /system read/write. I just wish I could remember how. Been a long time since I put my vogue down.
If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.
PoXFreak said:
If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.
Click to expand...
Click to collapse
Hi! Thank you!
What does exactly I have to do in terminal emulator?
I would hope you have superuser capability, if you don't then use another build that does have them...
Anyway, this is all I could figure out to remount the /system as RW. Type the following below into terminal emulator...
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
(Where "mtdblock2" has /system, "mtdblock3" has /data, and "mtdblock4" has /cache.)
Hope this helps...
Please correct me if i'm wrong.
I installed this new build.prop from the bootloader using androidupdate.tar.
Because i made a tar archive this way: system/build.prop
Isn't it the easiest method? No mounting and hacking in terminal emulator.
Anyway, do anybody know which ROM contains hungarian language? I gave my Kaiser to my father and it would be great if he could use it in hungarian.
I thought VaniljEclair 11 has it, and it is almost true. It has hungarian language but when i set it nothing happens. Everything is in english as before.
Thanks!
Edit:
You can download it from here:
http://mattempus.sohasenem.hu/pub/androidupdate.tar

tinynoot for glowworm

I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian

{Script} [App] CPU1 disabler while in sleep!!! 07/12/2012 Release 2.1

App Version:
CPU Sleeper
~Free to all XDA Memebers
~ Must Be Rooted to use App
What is it?
Its a fairly simple App that will put CPU 1/2/3 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1/2/3 back ONLINE.
How does it work?
Since we have Dual & Quad core CPUs, we have a CPU 0 and a CPU 1/2/3, core 0/1/2/3, while the screen is off we really only need to have 1 core active "CPU0", this App will make sure CPU 1/2/3 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
Compatibility?
Works with any Dual Core & Quad Core Devices!
~ICS
~Gingerbread
Battery Saving?
Battery savings all depends on Usage & idle times.
App Download: CPUSleep.apk
Credits:
Handlerexploit for co-creation of this wonderful App.
Script Version!
Code:
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
[B]CPU Sleeper[/B]
[QUOTE]Honestly the Script can be made to work with any Dual Core / Quad Core! The Only Problem is you need to be Rooted!
~ Currently the issue with CM9, is that the boot becomes incomplete while in init.d folder without Modification to the sysinit..
~ however, with any rooted device you can download the script & continue to use it via a script manager app on every boot.
~ With the Script Manager App, this script virtually can run on any Multi-Processor CPU
Hope that clears things Up,
~~Eugene[/QUOTE]
[U]What is it?[/U]
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
[U]How does it work?[/U]
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
[B][COLOR="red"]WARNING! READ THIS![/COLOR][/B]
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
[U][COLOR="Red"]Instructions[/COLOR][/U]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
[I]Version 1: Flashable[/I]
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
[I]Version 2: Script only[/I]
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
[U]Init.d supported kernel:[/U]
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Once done, reboot the system, and it will take effect when your system is finished rebooting.
[U]Script Manager[/U]
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
[U]What do I do if I can't boot after using this?[/U]
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
[B]Downloads[/B]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[URL="http://d-h.st/N1N"]CPU Sleeper script only[/URL]
Quad Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[url=http://www66.zippyshare.com/v/9249467/file.html]cpusleep[/url]
Thanks to [COLOR="DarkGreen"]pio_masaki[/COLOR] for rewriting the OP
Seems really cool, gonna check it out
Sent from my Sprint Samsung Galaxy S3
tarheelsmj12001 said:
Seems really cool, gonna check it out
Sent from my Sprint Samsung Galaxy S3
Click to expand...
Click to collapse
Thanks, Proof it's working!
http://forum.xda-developers.com/showthread.php?t=1739457
flashed over diet ics 6.30 build and my phone has not exploded. Hopefully you'll save us all some battery
I flashed it through CWM Recovery then i reboot and go to system/etc/ but did not see "init.d".
wings76 said:
I flashed it through CWM Recovery then i reboot and go to system/etc/ but did not see "init.d".
Click to expand...
Click to collapse
Same here :-(
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
question
Ive been testing battery life for a week now with cpu 1 stock and forced on, According to system tuner apk. cpu 1 is not even running 95% percent of the time with screen on and off /using phone, seems the kernel controls this pretty damn good, so.unless that app is not working correctly would something like this script even help at all?
What have your results/ testing been?
jiggytom said:
Same here :-(
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, did you also try the script manager method? I used the script manager to copy the file S98cpu_sleep to system/etc but it said "You cannot paste here because the file system is read-only." Any suggestions?
wings76 said:
Yeah, did you also try the script manager method? I used the script manager to copy the file S98cpu_sleep to system/etc but it said "You cannot paste here because the file system is read-only." Any suggestions?
Click to expand...
Click to collapse
I know we can do the script manager method but the init.d is cleaner.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If this is so simple why manufactureres not have this as default option?
wings76 said:
Yeah, did you also try the script manager method? I used the script manager to copy the file S98cpu_sleep to system/etc but it said "You cannot paste here because the file system is read-only." Any suggestions?
Click to expand...
Click to collapse
Use root explorer and mount system as R/W... then you can do it. Long press after to set permissions... and then mount it back as R/O
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Deleted, shouldn't have been this rude...
Please don't flash T989 /I727
I think people assumed that because you included it in the post that it would work on GS3's which is understandable.
Guessing you copied and pasted from your original thread.
y2whisper said:
I think people assumed that because you included it in the post that it would work on GS3's which is understandable.
Guessing you copied and pasted from your original thread.
Click to expand...
Click to collapse
I'm sorry, but lol if you didn't Read the OP?
Don't put this oof on me, after All I didn't invent reading & everything is laid out in the OP....
Fact is, Learn to Read!!!!
eugene373 said:
I'm sorry, but lol if you didn't Read the OP?
Don't put this oof on me, after All I didn't invent reading & everything is laid out in the OP....
Fact is, Learn to Read!!!!
Click to expand...
Click to collapse
Why would you post a link that doesn't work for the phone/forum you are posting in?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jiggytom said:
Why would you post a link that doesn't work for the phone/forum you are posting in?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I can not help but to laugh at this... Please Re-Read the OP regarding your Question and maybe you'll under stand it....
I'm happy to help in any shape / forum I can, but at the same level, people need to do the research as well..... As much as I want to help everyone at hand... What part of I727 / T989 did you not understand?????????
I'm sorry to be rude in this matter! But reading goes a long ways!!!
Also, The script works Perfect for all!! The .zip which is clearly labeled, well do the math~~
I Love android & Just want to help everyone, but at the same time people needs to learn to read & be liable for there own actions as well!
~Eugene
eugene373 said:
I can not help but to laugh at this... Please Re-Read the OP regarding your Question and maybe you'll under stand it....
I'm happy to help in any shape / forum I can, but at the same level, people need to do the research as well..... As much as I want to help everyone at hand... What part of I727 / T989 did you not understand?????????
I'm sorry to be rude in this matter! But reading goes a long ways!!!
Also, The script works Perfect for all!! The .zip which is clearly labeled, well do the math~~
I Love android & Just want to help everyone, but at the same time people needs to learn to read & be liable for there own actions as well!
~Eugene
Click to expand...
Click to collapse
I understand the label, but there are times where the flash able zips are cross device. No where in your post do you say DO NOT FLASH. again, no reason to post it or instructions for it if it doesn't work for our device. I understand you want praise and people thanking you, but don't spam it across different device forums and expect people not to be upset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Sorry not trying to spam it... Just wanted everyone to be aware of it is all.
OP has a new format now... I recommend using the App now
& removed the .zip as well to prevent any further issues.
I'm confused. I've read the whole thread (not that big yet), including the OP...and the posts about it 'not working for this device'.
Does this work on the AT&T Galaxy S III or not?
ewingr said:
I'm confused. I've read the whole thread (not that big yet), including the OP...and the posts about it 'not working for this device'.
Does this work on the AT&T Galaxy S III or not?
Click to expand...
Click to collapse
yes it works.... I recommend using the App though.

Categories

Resources