I made it. Used the Xoom and looked at it side by side with the one I made with the olympus device mod added to my earlier market fix.
You can see Samurai II, Adobe Flash, the Tablet versions of USA today and the NY times. Probably everything works. Back up your current build.prop and reboot. That's it.
USA Today Tablet edition crashes, even with adjusting heap size. Looks like it's mising code though according to the crash report, so not a simple fix. No surprise there.
Played briefly with the NY Times Tablet edition but it didn't look much different to me. Installed it alongside the phone version.
Have fun.
Someone tell me what it's useful for, i.e. being able to fake the Xoom. Seems of limited use ATM.
Donate a quarter.
#hacked together by rob at theroblog.com Will let you use NY Times Tablet but USA Today Tablet closes soon after run
# left out the stuff about phones and sims and such.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HRI39
ro.build.display.id=HRI39
ro.build.version.incremental=101999
ro.build.version.sdk=11
ro.build.version.codename=REL
ro.build.version.release=3.0
ro.build.date=Tue Feb 8 01:57:46 PST 2011
ro.build.date.utc=1297159066
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-19.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
# ro.product.device=olympus
ro.product.device=stingray
#ro.product.device=passion
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=stingray
# Do not try to parse ro.build.description or .fingerprint
# ro.build.description=trygon-user 3.0 HRI39 101999 release-keys
ro.build.description=trygon-user 3.0 HRI39 101999 release-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=verizon/trygon/stingray:3.0/HRI39/101999:user/release-keys
ro.build.characteristics=tablet
# originally was ro.build.characteristics=tablet,nosdcard for xoom but gTablet has SD so I took it out.
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-verizon
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.browser.useragent=1
persist.service.mount.umsauto=1
# ** Xoom has 1 gig RAM, using the uncommented settings didn't make USA Today Tablet work, commented are for 5.1.1 Vegantab
dalvik.vm.minheapsize=5m
# 4m for VeganTab 5.1.1
dalvik.vm.heapsize=256m
# 64M for VeganTab 5.1.1
EXTERNAL_STORAGE_MOUNT=/mnt/sdcard
persist.tegra.dpy5.mode.width=1920
persist.tegra.dpy5.mode.height=1080
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# VEGANTAB additional
#
persist.service.adb.enable=1
ro.setupwizard.mode=DISABLED
dalvik.vm.checkjni=false
ro.kernel.android.checkjni=false
windowsmgr.max_events_per_sec=60
ro.opengles.version=131072
I applied this to Calkulin's ROM, and it does indeed show the tablet apps (Tegra apps, CNN for Android, NYT ...). For some reason the USA Today app doesn't show. I actually downloaded Google Body, but it just force close, though I didn't really expect it to work. CNN app also force closes.
i used this, forced the stop, cleared cache and everything but still cant see launcher pro or anything.
am i missing something?
I don't see LP either, just the unlocker. If you're looking to install it, have you tried navigating to http://www.launcherpro.com/ from your gTab and downloading the apk from there (there is a link in the latest blog post)?
My method may have been overkill, but I basically followed one of the other market fix posts after pushing the build.prop:
Force Stopped market, cleared cache and data
Force Stopped Google Services Framework, cleared cache and data
Wiped data for Google Services Framework in TB
Tried to open Market to verify the error, and then rebooted
After that I was able to see the tablet apps.
Edit: Took about 2 hours, but now the web market shows my gTab as a Xoom, and I'm able to select apps that I couldn't before.
I don't know if my experience is the norm but I already saw those apps and have been playing Samurai II for over a month now running VEGAn 5.1 with the 5.1.1 supplemental and I didn't have to do anything at all to see them in the Market.
I've got Launcher Pro, i just thought that was the test as to whether I had full market access. The web market shows my device as a Xoom though, so am I good to go?
what "tablet apps"? Is it a seperate category or what
If you go to the Android web market, you'll see a section for "Featured Tablet Apps" -- if you made the change in this thread, you should now see your tablet listed as a Xoom when you choose to install something, so you can now install those apps. It appears most of the "tablet apps" just utilize the increased screen real estate (like the NYT app, though as the OP said, I don't see much difference), but some are built just for Honeycomb (like Google Body), and those won't run.
There are APIs that are only available in Honeycomb so those Apps probably won't have the extra columns on Froyo.
Sent from my VEGAn-TAB using Tapatalk
dfin13 said:
(like the NYT app, though as the OP said, I don't see much difference)
Click to expand...
Click to collapse
The Tina Fey article today had bigger and more graphics. Might as well keep the tab version so I deleted the phone version.
I got the NYT tablet app, so I guess this is working for me.
I don't have the Tablets section in the market, however. <shrug>
DroidHam said:
i used this, forced the stop, cleared cache and everything but still cant see launcher pro or anything.
am i missing something?
Click to expand...
Click to collapse
Launcher Pro actually doesn't show up in the Market on a real Xoom. So, you seem to gain AND lose at the same time. Just something to keep in mind.
Roe would you recommend this? and if so anyone out there able to do instructions for us less code friendly gtabbers?
I can get the Tegra apps but I can't see the USA Today or NY Times..I'm using caulkins rom..I made build.prop changes olympus and that long string
featured tablet apps are merged with other apps. Only app I found with this setting is CNN for tablet, but with it I lost lot of other tablet apps which I can download with my original phone setting like open table, sony pictures etc.
So after discontinuing tablet section on market, i think you can install these apps on any tablet depending on screen resolution and region and rom.
biggggant said:
I can get the Tegra apps but I can't see the USA Today or NY Times..I'm using caulkins rom..I made build.prop changes olympus and that long string
Click to expand...
Click to collapse
Can someone share how to make the changes? PC via usb, app, or some other way. Sorry, learning as fast as I can.
There is likely a tutorial in the forums on how to use adb, a lot better than I could likely type up, so read up on that. Once you're able to connect to your tab via adb, here's what you do:
In the command window, type:
adb pull system/build.prop
That will bring the file over to your PC. BE SURE to make a copy of that file! Open it in Notepad and then delete all of the text and then paste the text from the first post of this thread. Save.
Go back to your command window, and type:
adb shell
At the # prompt, type:
mount -o remount,rw /system /system
That will allow you to push the file back into the system folder by changing permissions to read/write.
Type Exit and hit Enter to get back to your command window. Then push the file:
adb push build.prop /system
It should give you a file size and execution time if it was successful. Then in the command window type:
adb shell
You need to set permissions back to read-only. At the # prompt, type:
mount -o remount,ro /system /system
Hope that helps. It looks too easy, but really ... it is too easy I am doing this from memory (except the mount stuff, had to copy and paste that), so if anyone can chime in with an easier method, feel free!
I used Root Explorer to do mine.
However, most of my changes have been made by mounting the GTablet as a USB device on a Linux box. Then, as local root on the linux machine, you can modify files on the Gtablet.
Cheaper solution than buying programs, and apparently easier than configuring and using ADB if you aren't a developer.
Just my two cents.
Root Explorer is easiest
I'd have to agree that Root Explorer is easier. Just remember to make a backup copy of the original file and keep it handy just in case!
Related
I modified my build.prop this morning, and my D2 is way snappier, no catching in long lists, and more
EDIT: Pasting someone elses build.prop can mess things up it seems, heres the changes I made
http://forum.xda-developers.com/showthread.php?t=771232
Sent from my DROID2 using XDA App
Will this work for those with 2.2.20?
This is kind of specific to your phone. Can you tell us what you changed?
I would not blindly copy someones build.prop. One thing I noticed, his is for 2.2.19. I diffed his with mine to see actual changes that would make a difference. Mine is 2.2.20
Code:
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=60
# This defines the min duration between two pointer event
ro.min_pointer_dur=8
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 75
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
#Proximity sensor debounce time
mot.proximity.delay=200
# disable touch below 60 pixels
mot.proximity.distance=45
The problem is some of my setting may differ because mine is stock 2.2.20 and his is 2.2.19, so I am not sure what he changed and what changed because of the update. I would like to hear exactly what he changed and his reasoning behind it (why he thinks it would give better performace). You can read the comments to at least see what the different items do to get an idea if you want to do a similar change, but that doesn't tell you if its different because of the 2.2.20 update, or because he changed it.
Update: I see he snagged these changes form the Droid X forums. Check here to see an explanation of what the settings do. http://forum.xda-developers.com/showthread.php?t=771232
I didn't think it was specific, but I guess so. Yeah, that's what I changed. And just testing after changes seem a lot faster
Sent from my DROID2 using XDA App
This is what I noticed after copying the file to my d2...
1. Can't make phone calls...when I press the phone icon to make the call, it kicks me to the homescreen and the top notification area tells me I have no signal....maybe the instant outgoing call changes is causing this.
2. When the phone turns the screen off...I noticed that the screen is black/blank but the back light is still on...so the screen is still on...
Other than these issues, I love how snappier the phone felt and the high density combined with launcherpro 5 rows is awesome. Too bad the issues makes my phone unusable...
facelessuser said:
I would not blindly copy someones build.prop.
Click to expand...
Click to collapse
Agreed, no one should copy this directly.
Code:
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=60
I did this change manually and it does seem to have improved graphical performance in menus.
Anybody trying to mod their Build.prop using adb here's how I did it:
Disclaimer: I'm not responsible for messing up your phone a build.prop is an important file. (I copied the files off so the file should never leave your phone it should only be copied over after we edit it, so nothing bad /Should/ happen)
(set USB connection to Charge Only)
adb devices
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cd /system
ls (only for seeing directory contents)
cp /system/build.prop /sdcard/build.prop
Now that you have the build.prop on the card you need to access it
Switch the USB connections to USB Mass Storage
Now go to the new usb device on your computer
The build.prop won't be editable yet
right-click->properties on the build.prop
now edit the name from build.prop to build.txt
click ok and/or apply
click yes to the box saying the file may not be usable (it will after we name it back)
now edit the build.prop (I used Wordpad and added comments that included the original values just for reference)
(make sure to save changes)
Now, go to the folder the 'build' is in at the top click on Tools->Folder options then uncheck the box for "hide extensions for known filetypes"
Rename the file from 'build.txt' back to 'build.prop'
Set the USB connections back to Charge Only
the cmd prompt should be back to the folder with adb in it so:
adb devices (just to make sure)
su
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
That should do it just reboot your Droid 2 and it should run better/faster
My first benchmark from quadrant was about 1500 this came from around 1350-1430.
Hope this helps
On the last command I think you typed the command incorrectly, ro,remount does not work so I used -o,remount..not too familiar with adb but I think that worked and I changed some of the build.prop and the results are pretty noticeable..with no animations set the phone is amazingly snappy and responsive .I used some of the specs they used for droid x but im hoping someone can write all the droid 2 specs because this way we know if these limitations are for our phone not the X. Thanks
Sent from my DROID2 using XDA App
Just an fyi quadrant is 1369...never preformed one before..is this better than stock droid..I would assume so......phone is really working fantastic
Sent from my DROID2 using XDA App
Just did another 1417
Sent from my DROID2 using XDA App
I get 1450 average with my build.prop mods and deodexing
Sent from my DROID2 using XDA App
Noticed no improvement in speed after editing build.prop and rebooting.
The touch screen seems a bit more responsive.
Quadrant scores before and after are around 1400.
Still no idea why the D2 feels so sluggish when scrolling in any app, compared to my DInc, which gets only 1160. Build.prop edits did not fix this for me.
Says My Phone is a Droid X
I added the build, and now my phone:
A. wont alternate from landscape to long way.
B. SScreen light is on all the time.
Can someone please upload the stock build so I can go back. Thanks. My score was 1455, btw.
Thanks.
I did
karnovaran said:
Agreed, no one should copy this directly.
Code:
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=60
I did this change manually and it does seem to have improved graphical performance in menus.
Click to expand...
Click to collapse
Please help me. I am an idiot, and did copy it. Please help me. I cant make calls etc. Cant find the droid 2 stock build. Please email it to me. !!!!! Buggin out...
here is the build.prop...obviously you will need to rename it to that but thats the original. yeah if you didnt read ANY of the previous posts it specifically said not to copy it..lol..sorry i think thats funny...
Fixed
JonandRoid said:
here is the build.prop...obviously you will need to rename it to that but thats the original. yeah if you didnt read ANY of the previous posts it specifically said not to copy it..lol..sorry i think thats funny...
Click to expand...
Click to collapse
Actually, I did read them. Not all though. Still funny though. Less so on y mend. Fixed it, thanks.
kageurufu said:
I modified my build.prop this morning, and my D2 is way snappier, no catching in long lists, and more
EDIT: Pasting someone elses build.prop can mess things up it seems, heres the changes I made
http://forum.xda-developers.com/showthread.php?t=771232
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
You mean those are the changes I made. haha glad to see it worked for you guys too.
newk8600 said:
Anybody trying to mod their Build.prop using adb here's how I did it:
Disclaimer: I'm not responsible for messing up your phone a build.prop is an important file. (I copied the files off so the file should never leave your phone it should only be copied over after we edit it, so nothing bad /Should/ happen)
(set USB connection to Charge Only)
adb devices
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cd /system
ls (only for seeing directory contents)
cp /system/build.prop /sdcard/build.prop
Now that you have the build.prop on the card you need to access it
Switch the USB connections to USB Mass Storage
Now go to the new usb device on your computer
The build.prop won't be editable yet
right-click->properties on the build.prop
now edit the name from build.prop to build.txt
click ok and/or apply
click yes to the box saying the file may not be usable (it will after we name it back)
now edit the build.prop (I used Wordpad and added comments that included the original values just for reference)
(make sure to save changes)
Now, go to the folder the 'build' is in at the top click on Tools->Folder options then uncheck the box for "hide extensions for known filetypes"
Rename the file from 'build.txt' back to 'build.prop'
Set the USB connections back to Charge Only
the cmd prompt should be back to the folder with adb in it so:
adb devices (just to make sure)
adb shell
su
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
That should do it just reboot your Droid 2 and it should run better/faster
My first benchmark from quadrant was about 1500 this came from around 1350-1430.
Hope this helps
Click to expand...
Click to collapse
think you forgot one thing...or at least I had to do this step....
thanks for the infos though, very helpful.
the bad news--this actually reduced my quadrant score. I was getting ~1350-1400 and now more like ~1275-1350
FWIW I'm running Epic Unleashed 2.5
Using epic unleashed 2.5 I'm constantly hitting near 1500 on quadrant and one time I hit 1520
Sent from my DROID2 using Tapatalk
In addition to the standard Market Fix to get protected applications working (clearing cache/data), we also need to trick Google to think we have a Tegra 2 device.
We simply need to change the following line in /system/build.prop
ro.product.device=olympus
This tells Google Market we are using a Motorola Atrix 4G and will give us the missing Tegra 2 apps when applying our market fix.
However, since we are mimicking a phone, Tablet specific apps will not show up (NYTimes app for Tablets is an example)
Cheers!
Edit:
It is well known that the Google Web Market is hit and miss on our GTablets. This thread indicates it may take a few days for our tablet's to show up on the web interface. However, what this fix does is allow you to download most of the Froyo + Tegra2 apps via the Market Application within our tablets. There will be applications that will refuse to install through the web market interface (if your tablet can actually show up on the darn thing) because of missing capabilities, but will install just fine via the Market app.
If you want to install apps using a web browser from your Desktop computer, I recommend the use of Appbrain to generate your list of desired apps and then syncing your list on the tablet to install.
Hi,
SUPER!!
This build.prop change, just by itself, on stock 3588, allows me to see a bunch of apps I haven't been able to see before, including Firefox, Flash, Tank Hero, etc. Didn't have to do anything else, no fingerprint changes, etc.
Thanks!
Jim
AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market. But YES -- Laucher Pro, Saumari, Silver Creek games, Flash 10.2, tv.com, both opera browsers, dolphin HD -- all there. FANTASTIC. THANK YOU!
Even Vlingo shows up which was never found before. Truth is I don't even want it but it was one of my indicators.
wd5gnr said:
AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market.
Click to expand...
Click to collapse
Are you looking for MessagEase?
https://market.android.com/details?id=com.exideas.mekb
Whoops! Helps if you spell it right. I always think that should be a faster keyboard but then I give up and go back to BetterKeyboard or the word predicting one which is great until you need to do Linux command lines and such.
Sorry for the confusion. I even found Astro Bluetooth Module another I used to have to switch for. Very cool.
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
How do we request this be made a sticky?
I know I've tried just about every market tweak for the last 3+ months and this is the only 1 that made a huge diff.
Jim
I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse
Yeah I tried logging out of the web site and back in. I've tried forcing a google account sync. And I've tried making sure Talk is running (apparently the website uses talk to send things to your device.).
Just for fun I put my ro.product.name/device/board back to Vega and with no reboot or anything the web site immediately found the device.... curious....
Well now that I'm back on the web site, my market is back to how it was even after I put the olympus line in. Getting too late. Will look at it tomorrow :-(
Hachi2Go said:
I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
Click to expand...
Click to collapse
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim
wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse
You're right that having market work on the device beats the website! The web market issues may be a whole separate battle.
Jim
jimcpl said:
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim
Click to expand...
Click to collapse
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Not sure if you meant to type ifileManger, but it will not get you write permissions. Root explorer will allow you to write. It looks as though you may have to
open a terminal up as discussed above, to change the build prop.
Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse
Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse
Hi,
If you don't have root explorer, there's a free app on market called something like "system mount r/w" that is free that will mount /system as r/w for you. Or, I think that you can do it using a terminal and a mount command (something like mount -remount....).
Normal file explorers won't do the remount.
Jim
mount -o remount,rw /system /system
Watch out for the spaces and you need to be root so do an su command first.
When done, repear the mount command but use ro instead of rw. You can do this with a terminal program or the adb.
Root Explorer is what, $3.99? Worth it for the time savings. I bought the Ti Pro too. $300+ on a tablet...spend $9 on some software to make life easier.
iam a noob. i have stock rom 3588. how do i get market working?
By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
For the new guys.
1) This appears like it MAY break your connection with the market web site [Update: Wait a few hours and it appears to catch up with you]. It may have other unknown effects. If you are not comfortable with making mods you might wait until more people have reported success or failure with this. For the record I did NOT find this fix (thanks Isira -- see OP of this thread). Just writing up my take on what you need to do. This applies to VEGAn 5.1.1 with supplement. It has been noted that with a stock rom you may need to put "busybox" before commands like cp (which you don't need to use if you have Root Explorer, by the way). If you get this to work (or not) on a different ROM, report it in this thread.
2) That being said, you need a file explorer that will look at / and edit text files, an su utility (comes with your root kit; as far as I know all the custom ROMs are pre rooted) and a command shell/terminal. Or you could spring a few bucks and get Root Explorer which is well worth it and does all of these things. Others have suggested Absolute Root tools which I do not know about. You could also use adb for all of it (which is what I did) but if you know how to do that, you probably don't need me to tell you what to do. We will be changing your build.prop file in the /system directory.
IF YOU ARE NOT USING ROOT EXPLORER GO DOWN TO STEP 3B. IF YOU ARE, GO TO STEP 3A.
3A) Open root explorer. Find /system and press the "Mount R/W" button.
4A) Long press on build.prop and select Copy. Then navigate somewhere like /mnt/sdcard and press the paste button at the bottom of the screen. This is your backup. Please backup.
5A) Go back to /system
6A) Long press on build.prop again. The menu is scrollable. You want Open in Text Editor.
7A) Find the line that says ro.product.device=XXXX (where XXXX is probably Vega). Make it read:
ro.product.device=olympus
Don't change anything else.
8A) Save the file by pressing the menu key and selecting Save & Exit.
9A) Scroll to the top of the /system directory and press the Mount R/O button.
10A) Reboot your tablet. Wait for things to settle down on restart. Open Market. Look for Saumari 2. Look for LauncherPro, Opera Mobile, etc. It will all be there.
If you don't have root explorer:
3B) Open the terminal. At the prompt, enter (spaces and lower case matter):
su
mount -o remount,rw /system /system
HINT: If you think you will do this a lot grab Script Manager off of the market. You can put the mount line in a script, tell it to execute as root (which is the same as su) and then you can run the script when you want to make changes.
4B) Start your file manager and find the /system directory. Your file manager probably starts in /sdcard or /mnt/sdcard. You'll need to go "up" a directory or two to root and then back down. Either way, when you find it, make a backup copy of build.prop somewhere you can write to. Seriously. Do not skip this step. Make the copy.
5B) Edit build.prop. You are looking for a line that sys ro.product.device=XXXX (probably Vega; I don't know about other ROMs and if this works for other ROMs but for VEGAn 5.1.1 its Vega). Carefully replace whatever you have as XXXX to olympus. So the line should read:
ro.product.device=olympus
Note: Some of us had other changes to build.prop. Not clear if these had any effect or not.
6B) Save your changes. If your file explorer is not root, you probably need to save the file to where you can write (your sdcard for example) and the copy from a terminal, such as:
su
cp /mnt/sdcard/new-buildprop.txt /system/build.prop
or
su
busybox cp /mnt/sdcard/new-buildprop.txt /system/build.prop
7B) Open your terminal and enter:
su
mount -o remount,ro /system /system
Remember spaces and case count! Also if you are in the same terminal window as before you don't have to keep entering su since you stay root.
NOTES FOR BOTH SETS OF INSTRUCTIONS
I did the original market fix after saving the file, but some people say it is not necessary. But at least a few people have said they don't see much or anything in market until the redo the fix (the one where you delete the market cache and the google services framework data and reboot).
Things that appear to work:
1) Installing free programs
2) Updating existing programs
3) Amazon market web site oddly enough
4) The official market Web site AFTER WAITING SEVERAL HOURS
5) Buying an app off the build in application
Some of us had other changes to build.prop but I don't think any of them were significant. If you have trouble you might apply it (shouldn't hurt). Also, if your "my apps" only shows your paid apps (or nothing if you have no paid apps), try downloading anything off the market and that will usually restore it. There is also an update local cache key that might do the trick, but loading some freebie off the market is easier. Also check to make sure gtalk is logged in. You can try forcing a resync on your Google accounts (in the main menu under Accounts).
Hope that helps someone. Its early so I probably made mistakes and will edit any that are found.
wd5gnr,
I don't know how "unusual" it is, but on my Gtab, where I had 3452 for awhile, then now 3588, I've always noted that I don't have a "cp" command, so I have to use "busybox cp".
Just FYI, in case anyone encounters this when they try your instructions.
Jim
wd5gnr said:
By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
Click to expand...
Click to collapse
Based on this thread ( http://forum.xda-developers.com/showthread.php?t=941205 ), it seems it may take a few days for the tablets to register on the market.
I have 3 tablets and I'm trying to change the identifier for each tablet through the ro.product.model and seeing if each of the tablets will show up on the market. So far, only one tablet is showing on the web market, but it's still using the old ro.product.model identifier (GTablet-TnT-Lite).
However, the web market is still pretty wonky. Certain apps may refuse to install through the web market because of missing capabilities on our tablets, but will install just fine through the market app.
Recently I've been looking into the build.prop file in the /system/ directory, and after making a few modifications I feel that I have gained a little performance not only from the network, but my phone overall.
***************************
I DON'T RECOMMEND DOING THIS IF YOU DON'T KNOW WHAT YOU ARE DOING.
MODIFYING THESE VALUES MAY EVEN REDUCE PERFORMANCE.
***************************
To use these values you must have an app like root explorer installed.
1. Open your explorer of choice.
2. Navigate to the /system/ directory, and mount it as r/w.
3. Make a copy of build.prop as build.prop.bak, so you can revert back to the original should you suffer any complications.
4. Open build.prop in text editor and at the bottom of the file make two lines space before adding these values so you can distinguish between these values and the normal values.
# Make UI more responsive (sweet spot is between 200 - 300)
windowsmgr.max_events_per_sec=300
# Dial out delay
ro.telephony.call_ring.delay=0
# Disable usb debugging icon (no more exclamation mark when connected to USB)
persist.adb.notify=0
# Enable hardware acceleration
debug.sf.hw=1
# Unknown
debug.performance.tuning=1
# Unknown (won't produce error log files due to apps or system if I remember right)
logcat.live=disable
# Unknown (render graphics using hardware)
video.accelerate.hw=1
# Unknown (disables graphics dithering)
persist.sys.use_dithering=0
# Unknown (deletes unnecessary cache)
persist.sys.purgeable_assets=1
# Force launcher into memory
ro.HOME_APP_ADJ=1
# WiFi scanning intervals (currently set at every 3 minutes)
wifi.supplicant_scan_interval=180
These are a few that I am using personally, but once again use these with care as you may recieve results different to what I get.
# Increase the memory of the Dalvik virtual machine
dalvik.vm.heapsize=64m
# Disable boot animation
debug.sf.nobootanimation=1
I do have a few more, but the ones I'm looking at currently could go bad depending on the user/ROM, but they aren't anything too amazing, so no ones missing anything big ;-).
Also network settings to add.
These were taken from the build.prop file on the Telstra HTC Desire S RUU ROM file, and I'm finding performance a lot better than what I was getting from any of the custom ROMs, not trying to bad mouth them in saying this though.
ro.ril.oem.ecclist=112,000,911
ro.ril.enable.a52=0
ro.ril.enable.a53=0
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.fast.dormancy.rule=0
ro.ril.disable.mcc.filter=1
ro.ril.emc.mode=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.oem.show.act=1
ro.ril.enable.amr.wideband=1
ro.ril.vmail.50501=+61101
ro.ril.gprsclass=12
# Default network type WCDMA
ro.telephony.default_network=0
Once again these values work rather well on the Telstra network in Australia.
Nice post man, keep 'em coming.
Peace
Sent from my phone using my fingers
Thanks for sharing this is great - although should it possibly be in the Dev section, even though you have provided a decent warning, it still has the potential to seriously destroy devices?
Also slightly concerned with the number of tweaks that are marked or commented as UNKNOWN.....I'd really like to know what these things are or at least what they're supposed to do before I attempt to implement them for my self on my device.
Although don't take this as a criticism., this is certainly the sort of stuff that I'd like to understand more.
Sorry, most of the ones marked as unknown, are mostly graphics which are normally processed by the software being moved to primarily being processed by the hardware.
I'll quickly edit now.
Added the dalvik and boot animation tweaks. Modified the post a little as well ;-).
Believe it or not, this netbook comes already rooted, but how to access it is hidden. The original adventure is posted below if you're interested,but I'll put the tl;dr up top.
You'll need to side load the app USB Debug by tatibana. This will shortcut to the hidden developer options. Slide the developer options on. You may or may not need to reboot, I was too focused on USB Debug to notice the SuperUser Options... The default is Always Deny. Set to Always Allow, then you can replace with your choice su manager (I installed Chainfire's SuperSU).
That's it. The rest below is my original posts up to this point, including getting a Linux working prior to figuring out root. Enjoy the read.
Edit 2: You can pick up new posts from this point by going directly to post #11.
Original Post:
---
Okay, this one is a bit puzzling and I haven't found any good info in searches. This is an Android netbook with Jellybean. Pointer control is a single point touch pad which makes zooming out on several apps impossible; I wish to attain root so I can install desktop Linux in parallel and use some desktop apps in place of some Android apps. I know I could use something like qemu but I'd rather install root and use arm binaries than take a performance hit using non-root methods.
This netbook comes with an installed su binary and busybox 1.19.4 but trying to invoke su results in
su: uid 10084 not allowed to su
Settings is also a bit crippled; no Developer Options section means no option to invoke USB Debugging. Anyone have any good ideas?
---
Sent from my C5155 using XDA Free mobile app
addendum
There also is no physical volume or photo buttons, and no obvious way to get into fastboot mode. My guess is that the original OS image was made in root mode, then the CV dev created a default user with almost no permissions, then backed it out effectively locking it out of root forever. I have also discovered that the busybox doesn't have access to the network as this user 10084, negating half its usability. No Play Store either (using Amazon instead), though I can (and have) install to my phone and copy to this if necessary.
This has a cool little form factor and I think has so much potential for a cheap device if I could just bust this major barrier. Does anyone know any sh or setuid tricks that might fake this thing into a root mode, or at least manage to give me enough permissions to edit /system files?
system seems to be owned by user 1003 and group 120, if that helps.
---
Mmmmmm, tasty foot...
So apparently this is normal behavior for the stock android su (see guys, I'm learning >P ); only the user shell (and root) can use su. This thing using a shared uid for apps might or might not have an effect, don't know yet. The normal way around it is to adb shell and su in, then overwrite with a custom su binary such as ChainsDD. I don't know if I have that option since there's no USB Debugging option, and I'm too tired to find out tonight. I will update this adventure later.
USB failed, but not anything to do with adb, didn't even get that far. The netbook failed to even register to the desktop (Linux)... lsusb didn't show anything. I don't know if it's a cable thing (tried direct A-A patch and the MiniUSB charge port- charge port predictably didn't support data and neither standard port showed any reaction) or a hardware limitation.
I also took a crack at adb over wifi but as usual it was the catch 22 of needing root to invoke adbd into tcpip to attain root.
Still open to suggestions... please?
---
Sent from my C5155 using XDA Free mobile app
Developer Options?
This is driving me up a new wall. Based on what I have been reading all day, Developer Options are a core function and cannot be removed, only hidden. This thing has not been giving me much confidence in that statement, however. I have been through the settings over and over again with a fine tooth comb and the whole thing eludes me.
This is Android 4.1.1. The 4.2+ trick (7 clicks on Build Number) doesn't work, and it's not in the App settings either, nor is there any sections renamed "Advanced" or the like. It may not be an end-all but I feel it would at least be a step in the right direction. I might be able to use an exploit such as Poot or Framearoot, which are currently ineffective.
I also haven't had any luck with getting into a recovery boot mode, not sure it's possible with this keyboard (I suspect it's soft driven; inactive until the kernel and modules are loaded). This seems to be just one shut down after another. I need more ideas, pointers, whatever. Don't forget, it can also help the next sap stuck with this model...
I decided to not lose sight of my original reasoning and move forward anyway with an app that claims to install Linux without root. I installed Gnuroot Wheezy which taught me some more f'd up things about this netbook but it at least in concept is working. What more things I have learned...
One of the issues with running Linux without root is the inability to use the external SD-card, at least native, because you can't mount an external partition/file that hasn't already been set up in the mount scripts outside of userspace. Gnuroot uses a chroot off the secure asec in /data. With about 3G user space available on this netbook, you'd think that wouldn't be a problem... but it is, because of another setup issue with this netbook...
See, while the external SD card does mount to /sdcard,/mnt/sdcard, that is NOT where Android app setup calls SDcard... there is a so called internal SDcard that is really a fake vfat via fuse mount off /data mounted to /mnt/local. This means it does no good to move my plethora of other apps to the "SD Card," actually, it makes the problem worse on this device. I imagine it was done so you could swap SD cards without affecting your apps, good move for flexibility but poor for expandability.
For those who would try it, that's also a big hint for getting it working. This device does not have access to the Play market*, so you will have to move helper apps from another Android device over. Don't bother with 3rd party repositories, you will not get everything you need. The biggest issue is the WheezyX obb file. It on install ONLY from the Play store will be located in /sdcard/Android/obb/champion.gnuroot.wheezyx/main.2.champion.gnuroot.wheezyx.obb , on this netbook the file must be moved to /mnt/local/Android/obb/champion.gnuroot.wheezyx or it will not be recognized, and because of the play store issue, can't be downloaded and gnuroot will exit with error.
Anyway, so now WheezyX is actually running and I am attempting to install an Openbox/LXDE desktop... the problem I am hitting now is the space limitation... It said it needed about 330 MB space and I had 360MB available on start... I'm now about 1/4 through and the netbook has come to a dead crawl due to... yep, very little space left (about 55 MB free on /data)... WTF! I feel like I am just not meant to win at like anything...
---
*Edit: Once rooted, the play store can be installed to the system partition and does work pretty good.
---
Sent from my C5155 using XDA Free mobile app
Some success with Linux
Well, it took quite a bit of monkeying and persistence but I do have desktop Linux running via the above described method. I found Synaptic was useful for finding packages but as the GNURoot author warned, for the love of all that's holy, use apt-get to actually install the packages. It seems trying to install a desktop environment via Synaptic totally overthrew the system. Also try installing only a few packages at a time and clean up after each one, especially where space is a premium.
What's left now is experimenting with vnc viewers a/o X11 environments. I'm presently using PocketCloud but it doesn't seem to like this keyboard (right shift = 6, no down arrow, Ctrl is sticky- forget combo keys; at least the included soft-keyboard does work, just a productivity killer) and getting a right mouse click is almost impossible, so I want to see if I can do better.
The environment is OpenBox with lxpanel and the background is set with qiv. I am confident now that providing space wasn't such an issue I could run pretty much any basic Linux program I want. I have not tested audio and I already know just being vncserver that motion video is a bad idea; this was mostly proof of concept until I can open up some space. I may now see how far I can take this (e.g. link large trees to the SD card, such as bin directories; since it's already running fake-root, I'm not too worried about user permissions. I may also experiment with fuse).
Edit:
This does not mean I don't still want to get a true root. If nothing else, even if I can't take Linux off the internal storage, root will allow me to force Android apps on to the external SD; either solves the current space issue and thus is still desirable. I'm just not as stuck in the mud now. Ideas still very much appreciated.
Done and done.
Just a quick update to say the project isn't dead, just dormant. I have successfully turned on USB debugging thanks to a shortcut app called "USB Debug" by Tatibana. Thank you
---
Sent from my C5155 using XDA Free mobile app
Framaroot, Universal Androot, and Poot have all failed.
:banghead:
Have yet to see if physical USB will now work... I don't exactly live alone.
---
Sent from my C5155 using XDA Free mobile app
SUCCESS!!!!!
IDFBT! I must have not been paying enough attention before or something, or maybe it was one of the half dozen greyed out options before... not sure, but after I was again unable to connect via direct USB, I decided to double check the developer options to make sure noting was reset by the last reboot.... and there in bright white last in the top section... Superuser Options (set to Always Deny)! I set it to Ask and tested, but it promptly rebooted as soon as I tried to su, and again on that boot, so I had to set to Always Allow. Amazon doesn't have SuperSU and last I knew ChainsDD Superuser is still adrift in the doldrums, so I'll have to sideload (as usual), but, I just wanted to share. This netbook does come rooted, you just need to turn on the hidden developer options, reboot, and go back and allow SuperUser.
Will report more as I progress. Banzai!!!
Adventures in Linux land
Well, I had mentioned before how space was an issue. Thanks in part to Link2SD, I managed to curb that problem.
Problem still though was my base graphical Linux install was taking 1G of my /data space. Since I made 2G available on the Link2SD ext4 (/data/sdext2) partition, I found I had about 1.3G available after moving most apps over, I decided I'd try a manual data move. I was slow with this since I didn't know how Link2SD or the system was going to handle it. That turned out to be a good thing.
When using Link2SD, one thing that should be obvious is to never move essential apps off the internal storage. These would be things like Link2SD itself, a Terminal emulator, and your superuser manager (e.g. SuperSU); basically, things you absolutely cannot lose access to even temporarily.
Okay, so, to test the behavior, I went into the emulator..
su
cd /data/sdext2
mkdir Linux
That's all. I then did a normal power off and restart. When rebooting, an "Android is Updating..." box came up and went away in a few seconds. The launcher came up and I waited for everything to load normally. Then I started getting a rash of "App is not installed" messages... uh oh. The only reason this turned out to not be a big deal is Link2SD and SuperSU were still on internal storage, and Link2SD is designed to deal with this problem. I simply launched Link2SD, clicked the tab bar on the upper left, and selected "Relink all application files," after which it requested a reboot, and I complied.
With a semi-disaster averted, I went back into /data/sdext2 to see if the Linux directory was still there. Hallelujah it was. Next was finding the GNURoot wheezyx root. This turned out to be fairly easy:
/data/data/champion.gnuroot/app_install/roots/wheezyx . I decided for potential future expansion to move the whole roots directory. Being cautious as I try, I do a copy.
su
cd /data/data/champion.gnuroot/app_install
cp -a roots /data/sdext2/Linux/
(... go make a sammich ...)
rm -R roots
(... go make and eat dinner ...)
ln -s /data/sdext2/Linux/roots roots
This appeared to work at first, until I tried to install something (abiword). I discovered that the permissions were not copied to the lib directories (android security quirk?). This would probably not be an issue if this were a true root install but being a fake root app install, it effectively prevented the installation of libraries. This was fixed simply by doing a chown and chmod on the lib directories.
Contined from above:
cd roots/wheezyx
chown 10102.10102 lib
chmod 771 lib
chown 10102.10102 usr/lib
chmod 771 usr/lib
*note: the app id number may be different on your copy. This will be fairly obvious with a simple ls -lh .
After that, the install completed and this thing is running pretty good. I am now considering this a complete success. While technically solved, I'll keep this thread open for questions or updates (for as long as the mods don't mind).
---
Sent from my C5155 using XDA Free mobile app
Screencap op
Assuming the uploads work this time, attached are some screencaps. Enjoy.
I have an old device, a nexus 10....yes there are some of us still using these
I am currently using a Lineage 16 ROM which is having security updates regularlly released. This is a big plus, but comes with drawbacks, namely a lot of hardware stuff doesnt work, the tablet runs hot doing basic tasks and performance is very slow. I would like to run an older ROM more suited to the hardware, but the security patch on some of these goes back to 2015 and rings alarm bells!
My use case is simple, browse and view YouTube videos via Adblock browser (gets rid of annoying adverts), run some games and apps from the play store. Some minimal web browsing.
Simply, what is the risk of using older ROMS? Can you mitigate the risk by 'not browsing'? is being online in itself an issue? Do you avoid having root access if your on an old device? I know next to nothing on this area so would appreciate advice.
Thanks
Graham
IMO any browser, especially its extensions, can be thought of as suspicious software.
jwoegerbauer said:
IMO any browser, especially its extensions, can be thought of as suspicious software.
Click to expand...
Click to collapse
Thanks for the answer...so in short its a bad idea to run the older ROMS from a security perspective, regardless of use case.
Well, it depends on what you use the phone/tablet, if you use it for the simple things (calls, videos, music, etc.) you can use older android version roms, alternatively you can use build.prop tweaks and scripts like v6 supercharger for android, you can try these build.prop tweaks i use on an HTC One M8 (2 GB RAM) and an Moto G 2014 (Titan, 1 GB RAM)
Code:
# GALACTIC DeepSleep Ultimate Mod By PawanRockz
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
wifi.supplicant_scan_interval=180
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
ro.config.hw_power_saving=true
ro.max.fling_velocity=20000
ro.min.fling_velocity=18000
debug.performance.tuning=1
debug.kill_allocating_task=0
debug.overlayui.enable=1
ro.config.disable.hw_accel=false
persist.radio.add_power_save=1
settings.display.autobacklight=1
ro.ril.sensor.sleep.control=1
# More RAM
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
profiler.force_disable_ulog=true
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
profiler.force_disable_err_rpt=true
profiler.hung.dumpdobugreport=false
debugtool.anrhistory=0
debug.mdpcomp.logs=0
profiler.debugmonitor=false
profiler.launch=false
# Better RAM management
ro.HOME_APP_ADJ=1
chuy19312 said:
Well, it depends on what you use the phone/tablet, if you use it for the simple things (calls, videos, music, etc.) you can use older android version roms, alternatively you can use build.prop tweaks and scripts like v6 supercharger for android, you can try these build.prop tweaks i use on an HTC One M8 (2 GB RAM) and an Moto G 2014 (Titan, 1 GB RAM)
Code:
# GALACTIC DeepSleep Ultimate Mod By PawanRockz
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
wifi.supplicant_scan_interval=180
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
ro.config.hw_power_saving=true
ro.max.fling_velocity=20000
ro.min.fling_velocity=18000
debug.performance.tuning=1
debug.kill_allocating_task=0
debug.overlayui.enable=1
ro.config.disable.hw_accel=false
persist.radio.add_power_save=1
settings.display.autobacklight=1
ro.ril.sensor.sleep.control=1
# More RAM
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
profiler.force_disable_ulog=true
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
profiler.force_disable_err_rpt=true
profiler.hung.dumpdobugreport=false
debugtool.anrhistory=0
debug.mdpcomp.logs=0
profiler.debugmonitor=false
profiler.launch=false
# Better RAM management
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
I think my useage will be as far as watching YouTube videos and adjusting my fantast league team through the Ad block browser. Probably some games i own as well.
Build prop tweeks? this is a new term to me, given the hardware you are using and some of the things im reading in the script this this will help with running newer ROMS on the older hardware by tweaking th install (i know thats gotta be the wrong word, im basically noob lol!)
I've used old unpatched Android OSs for years on devices without root with only minor issues.
No forced reloads due to infections.
A malware jpeg gave me trouble once but caught it at the get go; it did some damage to the files of the folder it was in but was contained.
Keep a close lookout for abnormal behavior and act quickly if found.
A good firewall is a very useful tool; been using Karma Firewall, which uses very little battery and runs well.
Had a Malwarebytes scan pick off a nasty trojan preloader that auto downloaded it's self too. The free Malwarebytes can occasionally be a useful app.
Always keep email in the cloud, be wary of all downloads, especially of side loading apks and know the OS's vulnerabilities/lock it down as much as possible.
Just be ready to do a no warning reload if things go south*... and no big deal. Keep time staggered backups on multiple physically isolated hdds.
*pre Pie OSs may get a rootkit that will force you to reflash the firmware to eradicate it. So there's that.
graham_uk said:
I think my useage will be as far as watching YouTube videos and adjusting my fantast league team through the Ad block browser. Probably some games i own as well.
Build prop tweeks? this is a new term to me, given the hardware you are using and some of the things im reading in the script this this will help with running newer ROMS on the older hardware by tweaking th install (i know thats gotta be the wrong word, im basically noob lol!)
Click to expand...
Click to collapse
Build.prop tweaks are some tweaks like the ones that i put on my comment to improve performance, battery or modify things,build.prop is an file located on /system (/system/system on android 10 or higher when using TWRP), i will give you instructions to modify it on pc with notepad++
1. Go to system folder using TWRP or apps like root explorer, then copy build.prop to your sd card or internal storage
2. Connect your phone to your computer, and put your build.prop file to any place, i recommend to documents, then download and install notepad++
3. Edit build.prop file using notepad++, add tweaks i gave to you at the end of your build.prop file, add an empty line at the end of the file if there is no one to prevent errors
4. Save it
5. Put it again in your phone
6. Rename your build.prop file on system to build.bak, so you will have an backup in case things go bad or you get in an bootloop
7. Paste your modified build.prop file on system
On root explorer, you only paste your file on system and give permissions like this
RR
R
R
and restart your phone
On TWRP, after putting it into system, go to system and press on build.prop file, press on chmod and on value put 0644, then reboot your phone
So firstly, to @jwoegerbauer @chuy19312 @blackhawk
Thankyou for responsing to my question. I am in every way new to working with modified ROMS and having these working with old but still viable hardware. It gives confidence knowing that it is not a complete loss if i am running old hardware and thus ROMs on them. I am going to give the prop.tweak a go and see how i get on (really appreciate the detailed instructions Chuy19312) , at least i have a fall back position of using an older ROM given Blackhawks experiences.
Graham