Credit goes to bhp117 for initially pointing out the awesomeness of the newest version of V6 SuperCharger and to spc_hicks for going on this adventure with me last night and answering all my questions along the way.
For the sake of brevity, I'm not going to be immensely detailed--as I am often wont to do--but I will still try to make the instructions clear. Don't be afraid to do what seems logical even if I didn't explicitly say it here (e.g. I might leave out telling you to press "okay" ). Here we go...
Before We Begin...
This guide is written for GINGERVOLT 1.3 and will guide you through removing the baked-in version, and then installing the latest version (Update 9 RC 4). Theoretically, this guide should work for anyone on any phone, but I'm not making that claim.
FULL NANDROID BACKUP! This procedure does have the risk of bootlooping your device, but I and others have done this without any issues, but I can't be held responsible...blabbity blah rabble etc etc...if you lose all your datas and throw your phone out the window, or any other unlikely but theoretically possible problem that might occur.
You'll need to download Script Manager from the Android Market. It's free.
Just to be safe, make sure you are using the latest SuperUser binaries and Busybox.
For the sake of making your life easy, if you have your screen timeout set to a low value, I suggest turning it up to 30s-1m so you're not constantly dealing with that.
As a general rule, ignore most errors you see while running this script, unless they seem to directly pertain to whatever command you just ran.
The Fun Begins...
1) Go here and download "V6_SuperCharger_for_Android-update9_RC4.sh.pdf" (last attachment) to your phone. Generating the qrcode on your computer and then scanning it with a barcode scanner app is usually the easiest way to do this. Optionally, you can download the KickAssKernelizer and DieHard Battery Calibrator scripts, but only KAK will be explained in this guide.
2) Launch Script Manager. If first launch, click "browse as root" button and allow/remember when SU popup appears. Click OK.
3) Find the V6 SuperCharger PDF file (probably in /sdcard/download), and select it.
4) A popup window will appear. On this window, tick the "Fav" and "SU" buttons near the top (adding to favorites makes it easier to access later), then click "Run" in the top left. Do NOT run this **** at boot.
5) Text will start scrolling, you can scroll up at any time if you missed something. Script will do a bunch of tests to make sure you've got busybox and all that; your phone should pass fine. When asked to choose a scroll speed, choose "Fast" by entering 1 (or this will take forever).
6) IMPORTANT: Say YES to the next two questions. You want to create the local.prop and the init.rc or your tweaks won't stick around. When asked if your home is locked in memory, say "No" unless you know for a fact that it is. Now we can get to the fun stuff.
7) You should now see the "Driver's Console"--a list of options numbered 1-31--and below that, various information on what's going on with your phone vis-a-vis SuperCharger.
8) First things first, we need to remove GV's baked-in SuperCharger. Run Option 15. Let it finish, and then restart with Option 29.
9) After restart, open Script Manager and launch the V6 script again (if you added it to your favorites, once in Script Manager, click Menu Button > Favorites). If it asks you about local.prop and init.rc again, you say YES to both again.
10) At the Driver's Console, you will need to pick one of the options listed under 512 HP (5, 6, or 7). Choosing 5 will mean more apps can run in the background, but the performance benefits will not be as great. Choosing 7 will have the greatest performance benefits, but you may end up with a lot of apps being closed behind your back. If you're not sure which one you should pick, choose 6. This is the best option for most people.
11) When whichever option you choose above finishes, you will be asked if you want to "SuperClean and Restart." And yes, you most certainly do. This wipes your dalvik cache without needing to boot into CWR.
12) When restart finishes, relaunch the script. At Driver's Console, run the following options, in order (you don't need to restart between them): 13, 20, & 18. When 18 finishes, perform another SuperClean Restart (Option 30).
13) After reboot, you should notice a considerably faster startup time, and a much snappier launcher. Lets verify everything was intalled correctly by launching the script one more time.
14) When you get to Driver's Console, look at the area below the options, you should see the following messages (you'll see others too, but these are the important ones):
Launcher is BULLETPROOF! i.e. SUPERCHARGED!
OOM Grouping Fixes ARE in effect!
Current values MATCH Prior SuperCharge!
Nitro Lag Nullifier is Installed!
15) If all those messages are there, you should be good to go! Enjoy your blazingly fast phone. I'm getting ~3550 in AnTuTu now; hard to believe that a mere few weeks ago before Blitzkrieg was released I was only scoring 2600.
NOTE: In Step #12, running Option 18 ("Engine Flush") created a .sh script in the /data/ folder. This script clears out all the RAM being used and frees it up. Supposedly, this will eliminate the need to reboot simply because the phone has been in use for awhile and has started to "lag." You can run this manually in Script Manager, or set it up to run on a weekly/daily/whatever basis.
NOTE 2: In the next few days, I'll add more detailed instructions on how to automate the "Engine Flush" script, as well as writeup a section on how to install the KickAssKernelizer (KAK) tweak. To be honest, it's really simple and you can attempt it yourself if you want. Simply launch the script via Script Manager (as SU), and say yes to installing everything. Reboot, and then create a widget that you can use to launch the .sh file created in /data/ after every boot, or set it to run at boot in Script Manager. I'm not exactly sure if this provides a significant performance boost or not, but it appears to boost my SD IO speeds. If it happens to break your phone (which it shouldn't), you can boot into CWR and flash this zip to remove KAK.
NOTE 3: I'll also add some pictures to the guide, as well as clean it up a bit and make the formatting prettier when I've got the time. Next two weeks are pretty busy (and pretty formatting takes forever), so I wanted to get this posted so other people could take advantage of this. I just walked indyred and beamer through this exact process on IRC, and they're both running smoothly. If there's something that's not clear, feel free to post your question here and myself or someone else will help you out best we can, and I'll fix the guide to eliminate the ambiguity.
Good luck!
Nice post
I was going to update my original v6 supercharger thread later tonite but you beat me to it
I'll help you post a few pics
Set as fav and run as root for supercharger script should look like this before you run the file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Options
Select option 15 to unsupercharge if you're on gingervolt then reboot
Select option 5-7
Its up to you and it'll just set launcher as die-hard
If you want bulleproof launcher you'll have to run option 13
Then you can try out option 17-20
This is how it should look if you use options 6'13'20 after a reboot to know if the settimgs sticks
There's an option for you to uninstall KAK when you run KAK
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
Its not letting me thanks! So here it is thank you!!
GINGERVOLTED!
I wouldn't run KAKA at boot in script manager. Seemed to bog it down a bit, for me anyway.
Dumb question: is a nandroid backup different than CWR cause I always do it through recovery. Does it make a difference? Don't means to thread jack.
GingerVolt powered by MTM
revo_65 said:
I wouldn't run KAKA at boot in script manager. Seemed to bog it down a bit, for me anyway.
Dumb question: is a nandroid backup different than CWR cause I always do it through recovery. Does it make a difference? Don't means to thread jack.
GingerVolt powered by MTM
Click to expand...
Click to collapse
You shouldn't run any file in /system/etc/init and /etc/init as "" run at boot "" as it'll slow down the system and boot up
"" run as root "" is ok
Nandroid is just like cwm backup
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
bhp117 said:
You shouldn't run any file in /system/etc/init and /etc/init as "" run at boot "" as it'll slow down the system and boot up
"" run as root "" is ok
Nandroid is just like cwm backup
Bulletproof 512 ledded AWD SuperCharged RC4/GV1.3 - Nullified & SIO 2048 + Ad-Shot v13 ;p
Click to expand...
Click to collapse
And it's because of you I realized that was the problem. Thank you!
GingerVolt powered by MTM
Since you can add a widget script after bulletproofing apps, does that mean it's necessary to do it every so often?
Also, when running the aggressive setting....does it just kill apps quicker? I think thats the jist of it but wasnt sure, thought I'd ask people who understand it more.
GingerVolt powered by MTM
This new supercharger works great on stock rooted gingerbread. Thanks
Sent from my VS910 4G using xda premium
Still get about a second of black screen before the lock screen comes up, nothing has helped against that
This is a real nice write up
Good going guys...
Couple of comments...
KAK is an installer just like V6.
Run KAK after boot to verify that 98kickasskernel ran and settings stick.
Most people schedule engine flush every 3 to 6 hours.
What about detailing?
The sqlite vacuum is nice... that can be done weekly.
Of course all can be run in terminal as well.
Just type su first and these should just work:
V6
Flush
VAC
SClean (superclean and reboot)
Appreciate you stopping by zeppelin! I hope to improve to write-up once I'm done with finals and all that fun stuff. Fantastic work you've done here; I can't live without V6 now, and hard to believe I once used my phone without it. Keep it up man.
zeppelinrox said:
This is a real nice write up
Good going guys...
Couple of comments...
KAK is an installer just like V6.
Run KAK after boot to verify that 98kickasskernel ran and settings stick.
Most people schedule engine flush every 3 to 6 hours.
What about detailing?
The sqlite vacuum is nice... that can be done weekly.
Of course all can be run in terminal as well.
Just type su first and these should just work:
V6
Flush
VAC
SClean (superclean and reboot)
Click to expand...
Click to collapse
Im missing something here.. Im not Linux smart, but I downloaded terminal and typed SU, got the #, and then typed these commands but terminal kicks back "Not found". What am I doing wrong?
Also a write up on how to add script widgets would be cool for this
Thanks.
Jasbo said:
Im missing something here.. Im not Linux smart, but I downloaded terminal and typed SU, got the #, and then typed these commands but terminal kicks back "Not found". What am I doing wrong?
Also a write up on how to add script widgets would be cool for this
Thanks.
Click to expand...
Click to collapse
Have you ran the Engine Cleaner (Option 18) inside the V6 script? You have to do that once to generate the .sh file inside /data/
Jasbo said:
Im missing something here.. Im not Linux smart, but I downloaded terminal and typed SU, got the #, and then typed these commands but terminal kicks back "Not found". What am I doing wrong?
Also a write up on how to add script widgets would be cool for this
Thanks.
Click to expand...
Click to collapse
To add a widget just long press on the homescreen, select Script Manager then select the script you want the widget linked to.
Sent from my VS910 4G using Tapatalk
jamRwoo said:
Have you ran the Engine Cleaner (Option 18) inside the V6 script? You have to do that once to generate the .sh file inside /data/
Click to expand...
Click to collapse
Yes same goes for superclean and detailing (VAC)
Fixed my lag! Finally!
I may not know what I'm doing but I am good at following directions. Glad I tried this out!
VS910 4G using xda premium
Cal8192 said:
Fixed my lag! Finally!
I may not know what I'm doing but I am good at following directions. Glad I tried this out!
VS910 4G using xda premium
Click to expand...
Click to collapse
As long as you can follow directions you're good lol!
Sent from my VS910 4G using Tapatalk
jamRwoo said:
Have you ran the Engine Cleaner (Option 18) inside the V6 script? You have to do that once to generate the .sh file inside /data/
Click to expand...
Click to collapse
yes I have, I got it to work but I had to "Favorate" the script first through script manager for it to show up... maybe that step was listed and I missed it.. either way I got the Engine flush and Super Clean scripts both shortcutted now
Thanks also SPC...
so i installed the new Milocker and it has some lag when waking up the phone...
Is it ok to bulletproof it since it always shows up in running services as running anyway?
would it even have an effect?
You can bulletproof any apps you like but not all will stick
I'd tried it for thumb keyboard, system tuner it works and the settings sticks
When I tried cpu tuner and superuser it won't stick
You'll have run it after every reboot so make a widget to make it easier
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
Related
UPDATE: Use Appkiller to do the same thing if you're not into the whole modding scene
Hi all.
So, I'm a new user to this part of XDA (Those HTC Hero forums have taken quite the dip lately) - received my milestone on Friday, and wow, what can I say - truly blown away from the performance I can get out of it, especially since it is getting along in it's days now too. However, I'm always hungry for as much power as possible .
Something that really shocked me though is that it doesn't seem to me that anyone has played around with the automatic internal memory killer of Android. Basically, it eliminates the need of having a task killer program running at all - allows you to have Android kill your unnecessary tasks for you. But, before I repeat an already-written informational post on this, here's the link to read up about it for yourself: How to configure Android's *internal* taskkiller.
Anyway, here's a quick guide on how to add this to your wonderful Milestone (PLEASE NOTE - THIS METHOD REQUIRES ROOT):
WARNING - Playing around with system files is always dangerous. MAKE SURE YOU DO A NANDROID BACKUP JUST IN CASE. I take no responsibility for any damage what so ever (even though there cannot really be any with this ).
This guide also requires you to know about ADB Commands - google is your best friend in this case. Right now, I'm too lazy to post a guide for that .
Well, now that the formalities are out of the way...
1) Firstly, you need to have the G.O.T Open Recovery. I'm pretty certain I don't have to go into anymore details with this step - it's posted all over the place
2) (OPTIONAL FOR SAFETY. If you don't care much for safety, you may skip this step) Start your phone up as normal (if it's off) and then run the following commands from Terminal/Command Prompt on your computer, using ADB:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return a few values that look like this:
Code:
1536,2048,4096,5120,5632,6144
TAKE NOTE OF THESE VALUES. Although it's pretty simple to remove this if it causes problems, keep these values handy somewhere. Never hurt anyone to have another back up plan
3) Mount your SD Card so that you may access it on your computer
4) Browse to OpenRecovery/GOT/bin/boot_script on your SD Card
5) Open the file "71_overclock.sh" with a text editor or something you can use to edit the shell script.
PLEASE NOTE: THIS IS USING THE OVERCLOCKING SCRIPT FROM THE G.O.T OpenRecovery. I AM USING THIS AS IT IS USUALLY RUN AT BOOT, PROVIDING YOU HAVE OVERCLOCKED YOUR PHONE TO ANY OF THE VALUES IN THE G.O.T OVERCLOCK MENU. So, long story short, you need to have selected at least one of the overclocking settings in OpenRecovery for this to work.
6) At the bottom of the file, add the following lines of code:
Code:
echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree
THIS IS FOR THE AGGRESSIVE MODE. You can read up yourself for your own desired values in the thread link I posted above, and replace them in the above line of code as desired.
7) Save the file and close. Turn off your phone. Boot into OpenRecovery (You should know how to do this by now).
8) Go back to the overclocking menu and reset your desired clock speed. If you haven't set one before, now's the time to select
9) Restart your phone. To test if your new values have worked, boot your phone as normal, and once it's booted, connect it to your computer again, and load up Terminal/Command Prompt once again. Then, as we did in the beginning, run the following commands:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return your newly set values. And voila! Your phone is ready to fly. Although I haven't tested speed differences on the Milestone as such, it really helped on my hero. So, post some feedback and let me know.
-----------------------------------------------------------------------------------------
IF YOU RUN INTO ANY PROBLEMS LIKE BOOTLOOPS/STUCK BOOTS:
Bootloops/stuck boots usually happen when the phone doesn't like the modification you've added to it I have no idea how this will react on other phones. It worked 100% for mine, but if you cannot run this mod, then you can remove it by doing the following:
1) Boot back into OpenRecovery.
2) Go to the G.O.T Modding menu, and then to the Restore Menu.
3) Select to restore the mot_boot_mode file.
4) Restart your phone - this time it should start, but you might notice a drop in speed. This is normal, as we have reset the overclocking to normal.
5) Mount your SD Card again, open the file "71_overclock.sh" again with a text editor or something you can use to edit the shell script.
6) Remove the line you added previously. Save and close. Unmount the SD Card.
7) Turn your phone off and boot back into OpenRecovery. Apply your overclocking again, and reboot your phone. It should boot up fine.
8) Breathe.
----------------------------------------------------------------------------------------
I'll be updating this guide in the near future to possibly include a way of doing this without having to use any overclocking, as well as a more noob friendly version, including ADB How-to's etc. For now, the extra boost in power isn't going to hurt anyone
Credits: androcheck for his original guide on this feature.
Happy speeding,
MrP.
Great job! I will be trying this on my Milestone shortly.
Hopefully this helps with the low amount of RAM our Milestones have.
free market app called autokiller
used for a while on agressive settings , stopped using it 2 weeks ago , I dont see any diffrences at all , great guide tho !
I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.
MrPadie said:
I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.
Click to expand...
Click to collapse
Great thread!! I was acually thinking about this a couple of days ago, I thought it wasn't possible because we need to modify the init.rc in the boot.img to initialize it... But of course we have our mot_boot_mode that can do that
Welcome to GingerSense!
Please read this entire post and the two following FIRST, ask questions you have after reading them.
ROM is based on Evolutionary Sense by RCMix Team, ported to Incredible
This is a BETA rom. This means that anyone who downloads and installs this to their phone is therefor considered a BETA TESTER.
See post 3 for rules of testing!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's inside?
Desire HD (Ace) 2.36.405.8 WWE Release
Stock kernel (2.6.35.10) from Incredible_C Gingerbread leak
HTC Sense UI version 2.1 (Android 2.3.3 Gingerbread)
Extended Power Menu (with 4 in 1 reboot)
Quick Settings tab in notifications menu (with added settings)
HTC Kingdom lockscreen with buttons (Phone, Mail, Camera, Messages)
Lockscreen widgets!
Sense 3.0 MMS/SMS application
Sense 3.0 USB Menu
Sense 3.0 Task Manager (included in Quick Settings)
Polaris Office (replaces QuickOffice)
Screen On/Off animations (like AOSP)
AOSP Gingerbread Keyboard
Click to expand...
Click to collapse
What works?
Camera and Camcorder (thanks snq-!)
Wifi
Bluetooth
Video Playback
MMS! *thanks newtoroot
Verizon apps in Market *thanks JoelZ9614
much more...
Click to expand...
Click to collapse
What doesn't work?
MMS *fixed in Beta2
EMMC mount to pc
Lockscreen buttons have no icons
Netflix won't stream (w/ stock & modded apks)
No full-screen weather animations on homescreen *fixed in Beta3
Data shows EvDo instead of 3G *fixed in Beta3
[Google Maps causes soft reboot *fixed in Beta4
still looking for more bugs...
Click to expand...
Click to collapse
Thanks/Credits
Robocik, Capychimp, and Seo from RCMix team for allowing me to use their rom. Thanks guys!
Virus for help (with apktool especially) and his updater-script I used as a template
snq- you're a beast, man.
rmk40 for his stock boot.img
911htc for the Incredible_C gingerbread leak, this wouldn't be possible without it!
HTC for a kick ass phone!
Google, for android. Duh.
TokedUp for hunting down bugs like they owed him money
newtoroot for the original MMS fix! (kudos for original lockscreen fix!)
Vernox701 for the MMS hint (build.prop edit)
JoelZ9614 for Verizon apps in market + theming help
if I missed anyone, please let me know!
Click to expand...
Click to collapse
Flashing procedure/requirements:
ClockWorkMod 3.0.0.7+ required!
1. Download ROM and VR_SUPERWIPE.zip (modded to work on CWM3)
2. Transfer ROM and VR_SUPERWIPE.zip to SD card
3. Reboot phone to recovery
4. Make a nandroid backup (not required, but helpful)
5. Flash the VR_SUPERWIPE.zip FIRST! This will wipe all partitions on your phone, including: boot, data, system, and cache.
6. Wipe data/factory reset.
7. Flash GingerSense ReMix. When the install completes, reboot phone.
8. Let the phone boot to the lockscreen. Don't unlock the phone yet!
9. This ROM needs to sit for a good 5 minutes before unlocking fr the first time. It might be tough, but just leave it on the counter and watch some XDA TV
That's it! enjoy the rom! If you have an issue, please follow the procedure for reporting a bug in the third post
NilsP said:
Navigation is working good but can be finicky so:
1) Put Maps, Navigation, and GPS settings shortcuts on the desktop
2) Toggle GPS on
3) Make sure the icon toggles on (No \) and off (\) on the notification bar
4) If GPS icon shows on then open maps
5) If maps works you are good to go with anything depending on GPS.
NOTE: If the slash does not go away on the GPS notification icon keep toggling until it goes on and off consistently
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download:
Beta1:
GingerSense_ReMix-B1-INC.zip
Click to expand...
Click to collapse
Beta2 (full wipe recommended):
GingerSense_ReMix-B2-INC.zip
Click to expand...
Click to collapse
Beta3 (full wipe recommended):
GingerSense_ReMix-B3-INC.zip
MegaUpload link
Click to expand...
Click to collapse
Beta4 (full wipe recommended):
http://www.multiupload.com/TZO1IK6QHI
MD5: 175ade1a2e8312fbe45ac398b53a4099
MegaUpload link is still uploading
Click to expand...
Click to collapse
CHANGELOG
Beta4 (5/28)
New method for lockscreen icons/caller id (no EGL changes) (snq- is a BEAST)
No more gps bug
Higher-quality weather animations for Weather 3.0 (emin3sku)
New weather sounds (baadnwz)
Maps 5.5 modded for global navigation (Ownhere)
Added back Weather LWP and a new "secret" LWP
Updated htcreader (robocik)
Undead/Phantom Call fix as init script (thanks bftb0)
Beta3 (5/26)
Sense 3.0 weather! (snq-, robocik, Krzysiec)
Working animation videos in weather app (re-encoded by emin3sku)
Full screen weather animations with sound! (robocik)
Updated TaskManager (Krzysiec)
Stock MMS app with "bubbles" and backup/restore. Uses less ram. (seo)
Refreshed libs (robocik)
3G icon instead of EvDo (thanks for the help JoelZ9614)
Removed location icon in notification bar (JoelZ9614)
DSP Manager (Cyanogenmod)
might be more...
Beta2 (5/24)
MMS FIXED! (HUGE thanks to newtoroot, Virus, and Vernox701)
Correct time format (12 hour)
Correct date format (DD/MM/YYYY)
Fahrenheit instead of Celsius
English (US) by default in setupwizard
Removed A2SD-related init scripts
Optimized more (feels smoother)
Probably more I don't remember...
Beta1
initial release
Rules for Beta Testing:
1. Please only report a bug if you have done a full wipe before flashing.
2. If possible, factory reset and re-flash rom, then see if the issue(s) still exist
3. How to report a bug/issue (please use this format):
Steps needed to re-produce the issue?
What was running at the time? BE SPECIFIC (apps, GPS, wifi/3g, etc.)
List what version of the software you are using
Describe what happens after the error (ex: hot-reboot, hard reboot, bootloops, etc.)
List ANY mods/themes/tweaks used on top of a fresh install
A logcat of the issue is GREATLY appreciated. If you need help, PM me.
Screenshots are also very much appreciated.
Post any other useful information (setup info, ideas, etc.)
________________________________________________________________
How to set up the Android SDK and ADB:
If you're on windows, you'll do the following:
1. Download the installer here: http://dl.google.com/android/installer_r11-windows.exe
2. Run the installer, and follow the steps. If it asks to install java, go ahead and install it. Then, choose where you want the SDK to be installed (I use C:\asdk for ease of use).
3. When the installer finishes, go to you're install location and open the SDK Manager.exe
4. A dialog should pop up with a list of updates. Click the "Accept All" bubble and click OK.
5. After the download is finished, check the list of installed packages, and make sure the "Google USB Driver package" is in the list.
6. Plug your device into the computer's USB port. On the phone, make sure USB debugging is on (check the notification area). If it's not on, go to Settings->Applications->Development and check USB debugging.
7. Go to you're Device Manager in windows by right-clicking "My Computer" in windows explorer, then clicking "Manage". In the application that opens, click "Device Manager" on the left side.
8. You will see something like "Android phone" under Other Devices; there should be an exclamation point next to it.
9. Right click that, and select "Update driver software" or something similar.
10. In te window that pops up, choose to browse for the driver manually. In the next window, select "Let me pick from a list of drivers on my computer"
11. Select "All Devices", then click "Have Disk". In the dialog that appears, enter the location of your downloaded driver (in my case: C:\asdk\extras\google\usb_driver). Click OK
12. A list of Android drivers should show up. Select "Android ADB Interface", then Next. Click Yes if it asks.
13. Use the Windows key + R to bring up the run dialog box. Type "cmd" (without quotes). Command prompt should pop up.
14. Type the following, pressing enter at the end of each box below:
Code:
cd C:\asdk\platform-tools
*modify this line with the path to your sdk
Code:
adb devices
*should show "HTXXXXXXXXXX device". If it does, you have adb installed correctly!
Code:
adb logcat > logcat.txt
*this starts the logcat, and ">" outputs the logcat to a file
15. Once the phone reboots, press Ctrl + C to stop logcat, if it hasn't already. Take the logcat.txt file, and upload it to pastebin.com. PM me the link
If you need more help, feel free to ask. I wrote this from memory, so I may have made an error or two. It looks pretty right to me
Click to expand...
Click to collapse
How to add ADB and other SDK tools to your PATH variable:
Adding a folder to your PATH variable makes it so you can execute adb, aapt, ddms, zipalign (and other useful development tools in your SDK) from any folder on your computer, saving you from having to type the whole path to these binaries.
I will be teaching you to do this for the folders inside your SDK, but the same procedure can also apply to any other folder on your computer, just change the path to the folder as needed.
I assume in this guide that you already went through the steps of setting up the sdk posted above...
In Windows:
1. Open up an Explorer window
2. Right-click My Computer, then click Properties
3. In the window that pops up, click "Advanced System Properties"
4. At the bottom of the box that pops up, click on the "Environment Variables" button
5. Look at the top list, look for "PATH". If you don't see "PATH", click the "New..." button. (if not, skip to step 6)
a. In the "Variable name" text box, type "PATH" (uppercase, no quotes)
b. In the "Variable value" text box, enter the path to your android sdk, followed by \tools or \platform-tools. Separate paths with a semicolon ";" (ex.: "C:\asdk\tools;C:\asdk\platform-tools" without quotes)
6. If a PATH variable exists already, simply click the "Edit..." button and use the same instructions as in steps 5a and 5b
7. When finished entering paths, click OK.
8. Click OK again to save the settings.
9. To confirm it worked, press "WINDOWS BUTTON" + R to bring up the Run prompt, and type "cmd" (without quotes). In Command Prompt, type adb, and if you get any output either than "'adb' is not recognized as an internal or external command, operable program or batch file.", you're good to go!
Click to expand...
Click to collapse
Gotta love the 3.0 lockscreen
f5 f5 f5 f5
YESSS!! Could this possibly include the Sense 3 Mail.apk? I love the exchange features...
Yeah this weekends going to be a flash fest I can see it now.
Sent from my ADR6300 using Tapatalk
I can edit and save that in notepad and itll be fine right? New to the whole inner workings of these scripts and coding in general... complete noob actually
I would flash this right now if MMS worked.
Drewsipher said:
I can edit and save that in notepad and itll be fine right? New to the whole inner workings of these scripts and coding in general... complete noob actually
Click to expand...
Click to collapse
I would suggest using a program called Notepad++, as it wont destroy the UNIX "new-line" invisible character that windows hates.
I have also found a few more errors after the one posted, so I'm updating the op with something you guys can copy/paste to make it easier.
Again, sorry for the inconvenience. I feel like such a noob right now...lol
wdfowty said:
I would suggest using a program called Notepad++, as it wont destroy the UNIX "new-line" invisible character that windows hates.
I have also found a few more errors after the one posted, so I'm updating the op with something you guys can copy/paste to make it easier.
Again, sorry for the inconvenience. I feel like such a noob right now...lol
Click to expand...
Click to collapse
your also gonna re-upload it right? >.<
it won't install. I realized MMS was not texting lol. so i tried and it no work!
This looks like the perfect median to stability and sense 3.0. I actually run 3.0 w/ little problems; the only bug I found was graphical issues in the weather app but it was laggy and heavy. The only thing I really loved in 3.0 was the task manager and the lockscreen w/ widgets but since this has it and is stable I will flash this once it's ready. Do you know if the HTC Sense 3.0 Camera (XDA Thread) will work because it works on the Kingdom port. This isn't a deal breaker just would make the rom more awesome.
Just my opinion because I haven't downloaded most of the ports are based from Sprint phones and they sometimes leave in the sprint settings could that be the issue for mms not working?
Drewsipher said:
your also gonna re-upload it right? >.<
Click to expand...
Click to collapse
Of course
I'm uploading right now to multiupload, gonna take an hour and 45 min with my crappy connection.
Vernox701 said:
Just my opinion because I haven't downloaded most of the ports are based from Sprint phones and they sometimes leave in the sprint settings could that be the issue for mms not working?
Click to expand...
Click to collapse
Quite possibly. I ported this directly from the Desire rom. I'm looking into it
Does this have Darktremor's A2SD script? if not i'm flashing in a couple days
PGleo86 said:
Does this have Darktremor's A2SD script? if not i'm flashing in a couple days
Click to expand...
Click to collapse
Yes, A2SD is built-in
wdfowty said:
Yes, A2SD is built-in
Click to expand...
Click to collapse
Does it automatically move all the Apps to the sd card or can you choose not to do it?
Sent from my Droid Incredible Running CM7
Thank you for posting and ROM and not a DUE DATE looks clean
hightech316 said:
Thank you for posting and ROM and not a DUE DATE looks clean
Click to expand...
Click to collapse
Amen brother
Sent from my Incredible using XDA App
Disclaimer: I have only tested this on my own phone. Everything should work fine, but I am not responsible for anything lost on your phone..
Here is an application based on my Bell Deodex scripts. Still a work in progress, but I am running out of things to do with it so it may be ready for public consumption. I just ran through a test of all the features, so far, so good.
Features:
Full Phone Backup and Restore (partitions 1-14, 17)
Root / Unroot
Early usb enumeration recovery mode
2nd-Init support
Odex/Deodex system files. (Bell stock, Telstra and French supported, ATT firmware support would just be a matter of creating the right system_$version.tar.gz archive and putting it in my Dropbox account.)
There are some changes compared to my scripts:
I am not using /data/local/tmp anymore, instead I am using /cache.
Instead of suspending android vis setprop tcmd.suspend 2, which obviously wouldn't be good from something running within android, I am using my early usb enumeration wedge to do it on the next boot before android loads via a script run from /cache.
Slight mods to that have been made to support this functionality, it requires shsu to be installed from my root install. So, if you have rooted using something else, you need my shsu in /system/bin.
ApplyMods is not being used, I could possibly port apktools over, but for now, the mods are baked into the deodexed system files.
I have compiled my own version of Gingerbreak, based on the source for GingerBreak_v1.2.apk. It detects our Froyo better by seeing if there is a 2.2 in the version anywhere. Also, it now takes a path argument so it's not limited to running from /data/local/tmp, and not hard baked with an android application path. Also, the app installs SuperUser.apk as a regular application, not a system one, and prompts you to unmount your internal memory and sdcard, so preserve their contents while GingerBreak is active.
Still more testing needs to be done, I have been working with stock Bell for most of development.
Bugs and feature requests welcome.
Cheers!
Credits:
ChainDD for the Gingerbreak apk, and the The Android Exploid Crew.
edgan for the 2nd-int stuff, see his thread here.
Tested:
OLYLA_U4_0.37.4: 100%
OLYEM_U4_2.1.1: 100%
Fixes:
1.0.1: debloat script fixed when deodexing, it was working but the files were getting replaced by the archive.
1.0.2: check added for shsu
1.0.2: Fixed stupid backup bug, creating directory "backup" and copying to "backup_$version"
1.0.3: Added reboot dialog popup
1.0.3: Fixed force close when no sdcard mounted. (postexecute in asynctask was assuming initialized data, not done when aborted)
1.0.3: Backup/Restore now archives data partition.
1.0.3: Multiple Backups now put up a selection dialog.
1.0.4: Added settings menu option
1.0.4: Updated early usb recovery mode, osh mount moved and replaced, using flag to avoid rerunning the same code.
1.0.4: Reboot option moved to menu. Requires root, when rooting just turn phone on and off, Superuser.apk gets installed after you reboot.
1.0.4: ATT sideloading support added. Reason for the move for Superuser.apk to next boot.
1.0.4: Recompiled 2nd-int, it's now 5KB instead of over 400KB. Have to find some working source for taskset to do that same there.
1.0.5: Added long click to backup button to force a restore operation
1.0.5: finished off settings dialog to implement internal vs external storage.
1.0.5: Misc layout updates, smaller font description text.
1.0.6: Fixed root.sh script, missing / resulting in 0 byte files. Doh!
Some attempt at docs.
Root/Unroot
I am using Gingerbreak to gain a temp root, which then runs a root.sh script with elevated privileges to remount /system and copy su and sush to /system/bin, link in /system/xbin to su, and copy su over to /osh/sbin/frozenfish. Prior to running GingerBreak, the app brings up the system settings for memory cards, so you can unmount them. This will keep you from losing the contents of your internal memory and external sdcard, the app will wait until you have unmounted both. You still have to reboot however. Be sure to click install or replace for Superuser.apk when your phone reboots, around 10 seconds after you see the home screen again.
Unroot just uninstalls Superuser.apk and and deletes the files copied above.
Early USB enumeration:
How to enter:
Hold down volume down when you first turn the phone on, it will say fast boot.
Click volume down until it says early usb enumeration mode.
Press up volume to select.
What it is:
All this boot mode does is enable the usb port so it is available for adb access.
App_Process:
What this is:
It's what starts all the androidish things happening, otherwise you have just linux running on your phone. It is located in /system/bin and is called by init in init.rc. It invokes pre-zygote, zygote, and post-zygote classes (sets of functionality related to getting all the phone services running).
Early usb mode recovery:
What this is:
This is a script in /system/bin replacing app_process. This gets activated when there is an update.sh in /cache OR if you are in early usb enumeration mode and the usb cord is plugged in. In either case, the system partition is moved to /old_system and a copy of it is running from ram, system and root are in read write mode, both sdcards are manually mounted.
So long as you are booted into early usb enumeration mode and the usb cord is plugged into your PC, the phone will wait for the plug to come out, halting the boot process. You can fix your framework-res.apk files, do whatever, and the phone won't crash. When you are done you can pull the plug and the phone will continue where it left off. The system partition is remounted read only and put back as /system, the sdcards are synced and unmounted for vold to find later on.
(Your pc will beep saying usb is disconnected, that is the script turning off usb while it is copying the system partition, it will beep again when it reconnects usb. This is to avoid being in an adb shell and things are still in the works.)
If you have an update.sh script in /cache, regardless of whether you are in early usb enumeration mode, it will go through the same process above, the script will do it's thing while the real system partition is out of the loop, and continue on automatically.
2nd-Init:
This is implemented by adding (not replacing) mount_ext3.sh in /system/bin.
This script changes the affinity of init to be single core, and hacks into it to restart init. Everything already done up to the point in init.rc where mount_ext3.sh is located is not undone, there is a replacement init.rc stored in /system/etc/rootfs that leaves out the bits that were already done and disables some reboot detection. In my implementation of this, I make the phone insecure by replacing the root default.prop file, it gives root access to adb, and causes eclipse to freak out in it's console tab.
Deodex/Odex:
This app attempts to download a file to internal mem from my dropbox account named system_$version.tar.gz, where $version is the contents of your ro.build.id. This file contains the deodexed app and framework files, as well as some tweaks for build.prop in /system. It may also contain a bootanimation and apns list if you are running on Bell and have a foreign firmware loaded. A backup of the odexed files is also created in internal mem, as well as contents of any modified folders. The downloading is done right away, the deodexing is done via update.sh script on the next boot. Same process applies for reversing things.
Full Phone Backup/Restore:
This has nothing to do with nandroid or backing up personal settings.
The contents of /dev/block/mmcblk0p1 though mmcblk0p14, and mmcblk0p17 are dumped to internal mem in a folder called backup_$version, where $version is your ro.build.id. The data partition (mmcblk0p16) is 2GB, I create a tarball of that instead of a straight dump, you can do a factory reset to get that back to stock if anything goes wrong. The cache partition (mmcblk0p15) is just temp space, I leave that out.
To restore the process is reversed, it is implemented as update.sh in /cache for next boot. In this case the script reboots the phone and deletes itself. You can't replace the contents of system by essentially flashing it, and keep it's mount going.
Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)
Nfhimself,
This looks really great! Three quick questions though. What do you need for this to work with an att atrix? Will this tool root a fresh sbf install? How should sideloading be enabled first to install?
Thanks
eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!
Will the rest of the features (other than odex/deodex) work on an AT&T Atrix? I was a bit confused about this and wanted to clarify.
Yes, it should, no reason why not.
Cheers!
This is awesome thank you!
Sent from my MB860 using XDA Premium App
NFHimself said:
eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!
Click to expand...
Click to collapse
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.
eval- said:
Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)
Click to expand...
Click to collapse
NFHimself, what exactly does Early USB Enumeration do?
airbillion said:
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.
Click to expand...
Click to collapse
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App
n1ckr0th said:
NFHimself, what exactly does Early USB Enumeration do?
Click to expand...
Click to collapse
It's for using adb in early usb enumeration mode and for running scripts prior to android booting. Without it, android continues to boot and if there are any issues it auto reboots. That's the gist of it.
Cheers!
Sent from my MB860 using XDA Premium App
NFHimself said:
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thanks nfhimself! Any plans on making one?
Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha
marko! said:
Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha
Click to expand...
Click to collapse
Cool, also downloads fine from xda app.
Cheers!
Sent from my MB860 using XDA Premium App
airbillion said:
Thanks nfhimself! Any plans on making one?
Click to expand...
Click to collapse
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App
NFHimself said:
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thats great if you can do this for the att users! Yes 1.83 is the most recent and most used on att. Im not too sure about any differences on the att webtop compared to bell or the others, but if you need anything just ask.
Thanks
Sent from my Dell Streak using XDA Premium App
many many many thanks!!! ))))))
Btw how do we enter early usb enum?
About sideloadind and att, it will be on gingerbread enabled..
Until then if u can try install this app using adb, and then threw this app install modified gingerbreak.. Don't know for sure if it works..
Sent from my MB860 using XDA App
Can't get the deodex to work on stock bell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: what size is the deodex file?
Edit#2 : now it says everything works but after reboot still showing odex files I. System/app
i've the same probleme
can donwload deodex files for at&t 1.8.3
Greetings,
This is a rooted Rom for the Lenovo Ideapad K1. It also includes CWM version 5.5.0.4.
Original Thread at Rootz
-Already rooted with the latest version of Superuser.apk
-Google Apps
-build.prop changes to spoof Motorola Xoom (Was missing many apps from the market before, i.e. GTA III)
-Lenovo Market Removed
-Based off the 14_14_120109 US update
-Android Terminal Emulator
-OI File Manager
-Reboot to Recovery Widget/App
-init.d support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flash at your own risk. I am in no way responsible for any damage done to your device. This will wipe your entire device except the EXTERNAL sdcard.
If you are using Windows make sure you have installed the APX drivers before continuing.
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode. If using Windows make sure the drivers are installed
Instructions
Windows
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Double click the "flash-windows.bat" file
Linux
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Open a terminal and cd into the extracted directory
3. Copy and paste the following command
Code:
chmod a+x ./flash-linux.sh && chmod a+x ./files/nvflash
4. Run either
Code:
sudo ./flash-linux.sh
or from a root prompt
Code:
./flash-linux.sh
CWM Controls
Power = Back (Any submenu), Toggle Display (Main Menu),
Vol+ = Highlight Up
Vol- = Highlight Down
Home = Select
To boot into recovery
You can now use the built in app or widget to reboot to recovery
**Superuser may crash during the first couple of reboots to recovery. Dont worry
Or run 'k1recovery' from the terminal or adb
Notes
If you try to flash any of the OTA update.zip's, it will probably work, but you will be shut out of CWM and will not be able to get back in unless you reflash everything via nvflash
Downloads
K1_CWM_120109_Rooted_nvflash_R2.zip
md5: dc5264c761e96f9fb9f240924cf60217
K1_CWM_120109_M_GE_Rooted.zip
md5: 280e18ecf837bf030f0a0fe83ec3e824
updater_120109_R2.zip
md5: 48cb5fefac3dcfcb89cddde501ac3e27
updater_120109_M_GE_R2.zip
md5: ef45437e57d257e54054cf9b70a0fcd8
Honeycomb_statusbar_120109.zip - Idea by Shaztech
md5: df290cfd0125f1dde2255a8518cd493f
Restores the default Honeycomb Status Bar, with the favorites button hidden.
To Install:
1. Put the Honeycomb_statusbar_120109.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose Honeycomb_statusbar_120109.zip and flash.
ThirdPartyAppsRestore.zip - People report loosing market apps after using this. Removing link until I have time to test
md5: dd3ed7584c4c4813277ec96f55e4023a
Restores all the third party apps that came with the stock Rom.
To install:
1. Put the ThirdPartyAppsRestore.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose ThirdPartyAppsRestore.zip and flash.
If you want to remove any of the third party apps you can remove the apk from /data/app/temp
The device tree used to port CWM is posted in my github.
http://github.com/khanning
I will be in Freenode IRC room #ideapad-k1 if anyone wants to discuss development and to answer any questions.
Flashing this ROM. Finally taking a plunge to root the device - can't wait!
So far, the process has been simple and sweet - hope the entire flashing and post flashing process experience is sweet too!!
Thanks Khanning for such a quick turn-around to my request
---------- Post added at 02:59 AM ---------- Previous post was at 02:45 AM ----------
Ok, it really was extremely simple. I'm rooted with a 14_14 and EXTREMELY happy! This opens multiple doors for me with this device now. Thanks again Khanning - you'r the man!!
Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks
Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(
twe69 said:
Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks
Click to expand...
Click to collapse
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision
Adrixan said:
Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(
Click to expand...
Click to collapse
That's because on this ROM, the tablet is cloaked to work as a Xoom tablet for full app compatibility on the market. If you can change that on the build.prop (I think that's where it is) manually, it should accept it.
Although like I was told the OTA aren't full version of the ROMS, you might want to find and use the full version? Just a thought - more experienced users can give better suggestions.
Sent from my HTC Vision
rezapatel said:
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision
Click to expand...
Click to collapse
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....
twe69 said:
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....
Click to expand...
Click to collapse
Try disabling the Geolocation option, you should find that under -
Settings -> Location and Security -> "Use location for Google Search" and "Use GPS Satellites" (try disabling these option).
Super easy to flash and runs great and the status bar rocks.. that original was horrid
Sent from my Xoom using xda premium
Awesome
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?
dc52317 said:
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?
Click to expand...
Click to collapse
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision
I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
rezapatel said:
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision
Click to expand...
Click to collapse
dc52317 said:
I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
Click to expand...
Click to collapse
Haven't used rom toolbox to make any custom adjustments to the build.prop, but technically if it makes changes to the build.prop file, its pretty much the same risk of a bootloop as trying out v6. Just that it can be controlled by inducing one tweak / value at a time. You can also take a backup of the files and push the originals using adb.
I really wouldn't all that effort unless I find lots of free time soon
But pls do share your experience, most specifically modifying the build.prop and deleting the dalvik cache (and having it rebuild on startup). If this works, I will plunge in and try out other stuff.
P.S. I am now using RAM Manager Pro and feel, this has made the device much snappier. Experiencing the same snappiness on my HTC Vision too. So far, I feel its performing much better than v6 or akmo.
Sent from my HTC Vision
Installed the rom and its nice and snappy....
Can someone give a break down to wipe the dalvik cache please?
Got the can't install app from market problem to and I guess that is the way to fix it, to delete it?
Thanks.
ANY idea why I can't boot recovery to sdcard? Just dcim, android, and data folders
no usb connection to xp
I loaded rom and Honeycomb status bar fix. The speed and root is nice. But i just noticed I can not get a usb connection to be recognized by my windows machine, so I can copy over backup'd files.
Anybody know what needs to be done to restore USB connection? Is it because the device is no longer K1 and is now Xoom that it wont work wth lenovo usb drivers?
Please help. Thanx.
Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.
Twist79 said:
Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.
Click to expand...
Click to collapse
Yup yup
Can someone with the M_GE edition hop into freenode irc #ideapad-k1 with me to test it. If you don't have an irc client you can just go to http://webchat.freenode.net/?channels=ideapad-k1
[Edit]
Updated the first post with a link to K1_CWM_120109_M_GE_Rooted.zip for my mobile friends in Austria
thanks to isime13 for testing
Thanks I will try it ASAP. And this comes from Austria and not Germany.
Feedback for the DE Version.
look like rooted on the first look.
Superuser app installs fine.
BUT: Apps don't get super user rights. superuser cant update itself and busybox pro complains it cant install because it does not get superuser rights.
So on the second look...no it does not work right.
Okay if you do some work to make your Dell Streak 7 work right with the AOKP 4.2.2 here.
Everything you needed is linked in this post to get you up and running with 4.2.2.
Now for the stuff you need to do to make your 7 run big apps like this Rich! Free Casino Slots okay.
First once you have setup you install of 4.2.2 goto system settings. from there goto Developer options.
Once there goto Force GPU rendering and check that.
Now go get Memory Manager from the play store.
Now once you have that running set it's presets to Aggressive.
Once that is done check the Apply at boot.
Now head over to get Trickster MOD Kernel Settings from the store.
Now that you have that start it up and goto General tab.
In there set the I/O Control Scheduler to noop.
Then goto in the same tab, CPU Governor Control and set the Governor to smartassV2.
Now you can try playing around with overclocking the CPU, but I have found most of the 7's don't like anything over 1 GHz top end due to voltages.
But try at your own rick.
Anyway once you have those set then click the first app setting in the upper right and of the app.
Once in there set all of the On Boot setting to on i.e. check them all.
Now you can play with the delays but I have found if they are set to 0 it works better, don't ask why.
Now that we are done with that app the next app to get is Zram Settings Free.
Now once you have that installed.
open it up and check all the check marks you can. DON'T REBOOT THE SYSTEM YET.
Now close that out.
Now get Root Browser.
The reason for this app over others is because this one when it opens and edits files or makes new files or folders will make them so that Android will like them.
Because the next part is only for the brave of hart and mind. LOL
Okay open up Root Browser and get it setup.
Next head to /etc/sysctl.conf file. Open it up and add this to the last of the file.
vm.swappiness = 90
Click to expand...
Click to collapse
or what ever you like from 1 - 100. I set it to 90 so that my system will load most big apps. With out to much lag.
Now that is done and the file saved.
here come the real fun part.
Next head over to Terminal and open it up.
Now in here we put.
su
mount -o rw,remount /dev/block/platform/sdhici-tegra.3/by-name/APP /system
TARG=/system/.swapfile
dd if=/dev/zero of=$TARG bs=$((1024*1024)) count=400
Click to expand...
Click to collapse
The count=400 part is the size of the swap file we are setting up in the /system folder. So if you want something bigger then that put it in as a MB at the count part.
mkswap $TARG
chmod 600 $TARG
Click to expand...
Click to collapse
The last part sets the new swap file to root only keeps it from being deleted.
swapon $TARG
free -m
Click to expand...
Click to collapse
The last two things do this.
1: it tells Android to use the new file as swap.
2: should show you a 400MB size swap file being used.
Now to get this all to restore it's self after a reboot we are going to need to do a bit more, but it's fast should be the end of this.
Okay before we try a reboot head back over to the Play Store one more time and get yourself.
Script Manager - SManager
Now once you get this app setup we are going to make a .sh file.
A .sh file is a shell script file for *inux based systems. Yes that's OS X no matter what apple wants you to think other wise.
Okay to make this file open SManager
Then hit the menu key, then tap new script.
Name it what ever you would like. I called mine swap.sh
Next use the TB editor.
It should have this in the window to start with if not put it in.
#!/system/bin/sh
Click to expand...
Click to collapse
Now the next part to make this all work right.
TARG2=/system/.swapfile
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/APP /system
swapon $TARG2
Click to expand...
Click to collapse
Now once that is saved in your internal SDCard then tap it and then tap the root icon and the boot icon.
Now when you reset the tab it can take up to 2 minutes to fully load out but now swap will be running and the tab will be fast and big apps like games and Netflix should load and work. Now I have only tested this on game like Hit It Rich or Fast 6. I have yet to try it with Netflix so don't blame me if it still don't work.
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
giveen said:
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
Click to expand...
Click to collapse
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is reading from ZRam Setting app.
And here is some more info for you to look at.
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
michaelcrossland said:
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
View attachment 2901112
Here is reading from ZRam Setting app.
View attachment 2901113
View attachment 2901114
And here is some more info for you to look at.
View attachment 2901115
View attachment 2901116
View attachment 2901117
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
Click to expand...
Click to collapse
Tutorial [Guide] [Dec.15] How to Tweak and Mod Android Using Init.d Scripts
and, in the jb defconfig,
CONFIG_SWAP=y
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
michaelcrossland said:
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
Click to expand...
Click to collapse
I though all init.d scripts ran as root. Why not try it and see?
the second part, is from giveen's github kernel source, and unless the one built into your ROM uses another defconfig, you do have swap enabled.
in terminal, as su, zcat /proc/config.gz > /sdcard/config.txt
then you can look for SWAP in the text file and see what it's currently set to. You can't change whether swap is enabled or not without rebuilding the kernel.
This is after attempting to flash the test kernel.
ElfinJNoty said:
This is after attempting to flash the test kernel.
Click to expand...
Click to collapse
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
ElfinJNoty said:
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
Click to expand...
Click to collapse
I built from that repo with that defconfig.
Not surprising that's what's in the ROM already.
Just couldn't recombine the boot.img in a way that the streak would accept.
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
giveen said:
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
Click to expand...
Click to collapse
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
I just put my streak on the charger.... Just in case
bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
CM11 is a whole 'nother animal, as CM changed a lot of things with the bootup files and how the disks are partitioned/mounted.
DJ Steve and I have an updated kernel for the cm10.1(really an aokp 10.1) ROM by Giveen that is optimized and increases available memory by about 70mb. Amazing how much improvement off of more available ram. Continuing to test and implement changes and add in features. Also working to convert for bootable lollipop ROM.... Stay tuned:
http://forum.xda-developers.com/showthread.php?t=3330564
I think its awesome that you guys are progressing so quickly! Picking up the torch and finishing the race!