Related
12/23/10- V6
- Easy root. You only need to install Superuser app from Market.
V5
- Wifi semi-working (tend to crash the phone on Wifi sleep timeout)
- Calls working but no DATA for me (coolya had data, which means: erratic) - voice not tested.
- kind of laggy, but there is a lot of headroom.
- GPS working only by Wifi/Triangulation networking - No satellites.
Fantastic job by coolya who did most of the advancement, for Wifi, baseband and also OneDRAM partitions configuration. Really really awesome work.
We were so lucky the snow forced him to stay at home instead of going to work
This time you can really start to play with the phone, install apps, surf on the Internet all this with Gingerbread! kind of cool
12/22/10- V4
-Buttons fixed thanks to the contributions of xcaliburhands, pawitp, fenfir*
-No need to create some directories manually anymore.
-Kernel available as ClockWorkMod recovery update.zip - be sure you have access to 3 buttons !
*I havent tested this beta so im assuming the buttons are remapped properly for only i9000 using that kernel he posted. but if i read on twitter correctly, all phones have proper keymapping, not sure.
12/19/10 - V3
- SDcard now works
- As internal storage
- As USB storage
12/19/10 - V2
improved pre-init script and mounts:
no more insufficient space
improved dual-boot solution
faster boot
faster disk I/O
12-18-10 - V1
initial
----------------------------------------------------------
READ EVERY WORD IN THIS LINK AND IN THE LINKED POST BEFORE FLASHING, I TAKE NO RESPONSIBILITY FOR YOUR CHOICE TO FLASH THIS AND ANY BRICKS OR UNPLEASANT OCCURRENCES THAT MAY FOLLOW - CLICK ME FOR THE ROM AND INFO
Make sure you have voodoo preinstalled and NOT disabled before flashing
Warning! Be careful ADB might not work for you. Im on Windows 7 64 bit and lost ADB access, you might need to go into download mode and ODIN!
^Update to this, make sure you have the latest usb drivers from the Android SDK. Still gonna leave this warning up though because it doesnt work for me after updating the drivers.
----------------------------------------------------------
References/Guides
kennethpenn posted a detailed n00b friendly guide to flashing this here
Vibrant Voodoo Kernels can be found here
----------------------------------------------------------
Enjoy the early taste of gingerbread, thanks to supercurio and the #NSdev channel!
Link please
Sent from my SGH-T959 using XDA App
its the first line in all caps lol, i wanted people to read it before clicking
Stuff like this that makes me wish i had bought an i9000 instead of the vibrant
ozmulti said:
Stuff like this that makes me wish i had bought an i9000 instead of the vibrant
Click to expand...
Click to collapse
its no biggie dude, ports from the i9000 are getting easier to do it seems (im not dev myself but thats what it seems like lol)
also cool thing about this is that its actually dual booting gingerbread on your phone
ozmulti said:
Stuff like this that makes me wish i had bought an i9000 instead of the vibrant
Click to expand...
Click to collapse
be patient and you'll see that its going to get way better.
and so it has begun....
all the galaxy s variants exept maybe the epic are near identical minus a few things. so when the i9000 get it, the vibrant nomrally gets it. no worries.
woot!!
Links broken
Sent from my SGH-T959 using XDA App
This may sound like trolling. But this voice inside my head just keeps on saying that i am getting the port of a port. Wish supercurio would develop for vibrant. ANd THAT would be ported to the i9000 ... take that Stock GALAXY S BEEEAACH
DEFINITIONOFREAL said:
Links broken
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
try it now
True, when the i9000 gets something we basically get it also.
Sent from the speed demon
I wrote up some more detailed instructions here for noobies. Although this is an alpha build... so be careful.
kennethpenn said:
I wrote up some more detailed instructions here for noobies. Although this is an alpha build... so be careful.
Click to expand...
Click to collapse
I'll add the link to the OP
Is this real?
Sent from my Nexus S using XDA App
jalyn02 said:
Is this real?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Wow.
Sent from my SGH-T959 using XDA App
jalyn02 said:
Is this real?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes it is reallll
jalyn02 said:
Is this real?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
its a few months too early for April Fools
checked the Nexus out
checked the Nexus out and what I thought was correct. It seemed like a vibrant hopped up on 2.3 and the rest wasn't much different hardware-wise.... Now super-curio has proven this assumption to be correct
....congrats and excellent !!!
I'm not sure if anyone mentioned it in the other thread,I don't feel like reading through 39 pages when its already almost midnight and I need to wake up at 7am,but as a temporary solution until we get buttons working,as long as they didnt change anything major in the filesystem,you should be able to change the keylayouts file to make vol up and down remapped to home and back (or menu,search,... whatever you want.) I haven't flashed this yet,so someone please let me know if this works. If I remember correctly keylayouts are in /usr/keylayout/ and there should be a few files in there,one of which is the hardware button mapping,open it in a text editor,there will be a bunch of buttons on the left and their names on the right,find vol up and change it to say HOME,find vol down and change it to BACK. save the file and reboot,that should make them work as what you assigned them to.
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
Hello everybody!
Yesterday I was thinking about a new app for Android, and this app would be able to comunicate with the recovery to schedule things like backup and restore. In 2011 I released "ROM Updater" (not that big success though) which used extendedcommands, an extension to the recoveries made by the team of CyanogenMod (it was indeed created to let the CM updater work).
ClockworkMod Recovery adopted this system, but the author probably didn't want the competition, so started to release the ClockworkMod recovery with encrypted extendedcommands. You can still recompile CWM and redistribute with the unencrypted commands, though I decided to opt for something less rouge-ish (why the hell should I recompile something that already "works"?).
Team Win Recovery Project is a 100% open-source recovery with a new scripting language, called "OpenRecoveryScript". It's just like extendedcommands, but without all the implications of "Premium"* or in any case limited API.
Well, TWRP is not only that, it's a full-multitouch recovery, easy to use. It's being built for a list of devices, and this list will be updated every time someone will compile the recovery for his own device. I decided to compile it for the P7500, hoping it will be added soon to the official list. In the mean while, I'll release the builds right here.
I've built and tested the recovery image for the P7500 (WiFi+GSM) and it's been confirmed that it works on the P7510 device too (WiFi only).
Goo.im GT-P7500 TWRP repository
TechErrata GT-P7500 TWRP repository
TWRP 2.2.1.5 - GT-P7500
openrecovery-twrp-2.2.1.5-gt-p7500.img (on Goo.im)
openrecovery-twrp-2.2.1.5-gt-p7500.img (on TechErrata.com)
TWRP 2.2.2.0 - GT-P7510 (thanks to MapleSyrup)
openrecovery-twrp-2.2.2.0-gt-p7510.img
How to flash:
- Copy the recovery into the storage partition (alias /sdcard)
- In adb, as root, execute dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p2
Cheers
*I personally think that Koushik Dutta (the ClockworkMod guy), encrypting the commands with his distributions, played hard: ROM Manager is the "official" CyanogenMod updater (it's distributed along with any CM release even if it's not opensource (and the CM guys worked hard to take the closed-source apps out of their release)), de-facto everybody install the CWM recovery just 'cause it's already there (déjà vu Internet Explorer?). I think this is called "monopoly" and should be fought in any possible way.
I'm all for true open source development, and will be watching your progress on this. Kudos and a thanks to you!
Sent from my GT-P7510 using XDA Premium HD app
I'd be willing to test for the p4vzw. If you build an image for it.
Sent from my Galaxy Nexus using Tapatalk 2
This appears to work on my Wifi Galaxy Tab 10.1 (p7510). Although the log says "E: Unable to mount /sdcard" I can access the sdcard just fine. I tried updating to the latest droidbasement.com kernel and it flashed perfectly.
Oh, and thanks for the quick and easy non-odin way of flashing recoveries.
The recovery is already in the goo.im repository
http://goo.im/devs/OpenRecovery/gt-p7500
The dropbox image is already update to fix the /sdcard "problem" ^^
Would this work on a Galaxy Tab 10.1 wifi (p4wifi)?
Sent from my Nexus One
According to AAccount yes. Please confirm this, so that I'll tell the TWRP guys to add the repo for that device too and I'll update the title of the conversation here.
I can say without a doubt that this is the best recovery I have used on any device in my 3 years with android phones. Wow! Graphics a bit grainy on the p7500, but functionality is fantastic! Thanks!
Very nice recovery system, good to see other options. HTC users had several choices such as AmonRa and 4ext.
Can confirm that it works on the WiFi only version. Thanks for the options , friend. Been running TWRP on my One X since the boot loader was unlocked, and I was missing it.
Sent from my GT-P7510 using Tapatalk 2
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
You don't actually need to use adb. Any terminal app should do it. Just tyope "su" before issuing the dd command. I used this app https://play.google.com/store/apps/details?id=jackpal.androidterm&feature=nav_result. I suppose a word of caution would be to make sure you have the command correctly. Don't make a typo like mmcblk0p3 or you could be in a nasty situation.
Adb can be found in the android sdk. Google "android sdk" and download the appropriate one. After that have the sdk download platform tools.
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
An easy and safe way if you have the SDK installed is to run adb shell
Then type su
paste in the dd command posted earlier
Thanks....I went on google and am now learning about Android SDK. Interesting stuff. I know how I will be spending my weekend!
EDIT: In the meantime, I went ahead and used terminal emulator for the commands. I definitely like the touch interface...and it looks nicer than cwm for sure! It is a little slow graphically, but I think that can be forgiven based on the look of the interface.
Confirmed working on the p7510 wifi
Sent from my GT-P7510 using XDA Premium HD app
Hi
It works like a charm on my 7500.
Thanks for that. Maybe some one could make the install more user friendly, a recovery zip?
Sent from my GT-P7500 using XDA Premium HD app
I could create an update zip... if only I could remember where I left the signing tool...
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
elegos said:
The dropbox image is already update to fix the /sdcard "problem" ^^
Click to expand...
Click to collapse
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
That is a nice one, thank you very much for this project.
MapleSyrup said:
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/gt-p7500/openrecovery-twrp-gt-p7500-2.1.8.img
^-- this works for the 7510 too
BTW it's just a line in recovery.fstab in the device sources: comment the /sdcard one.
Works great for me although it's a bit slow to boot into compared to CWM or even to TWRP on my brother's HP Touchpad. Also text is a bit pixelated. Other than that though it seems to work well. I use 4ext on my Nexus One so it's really nice to finally get a touch recovery on my tab too
Sent from my GT-P7510 using Tapatalk
Hey all, i have been asked a few times lately how to install the v6 supercharger
So I have decided to finally make a tutorial thread
* Almost project butter build.prop tweaks are in post 3:
http://forum.xda-developers.com/showthread.php?p=3015977 *
-=The V6 SuperCharger=- brought to you by zepplinrox
Original thread: http://forum.xda-developers.com/showthread.php?t=991276
If you're thinking whether or not to install the script, areas all the positive comments in the thread
This will work on *almost* every ROM with a init.d folder in /system/etc/init.d
I haven't tested this on ROMs without one!
but its tested on nearly every incredible s ROM and on about 5 nexus 7 ROMs. You can use this guide on nearly every device, its universal as long as you meet the requirements
The last version I tested is U9RC11T6, on UKB II 1.3 and it works 100%
*Known to cause root problems sometimes with Nik's Project X 4.x* (Thanks to everyone who reported that)
Pretty sure its the busybox installed with the starter kit, maybe if you don't install the starter kit it will not have problems. If you test this, please report
Disclaimer: I, or zepplinrox or anyone here am not responsible for any damage caused to your phone. No one is forcing you to do this.
I did not impregnate your daughter or son
That said, its easy if you know what you are doing.
So, how to install on GB, ICS and JB
note: gingerbread does not need the patched services.jar so ignore that part if you are using a gingerbread ROM
UKB II and ARHD 3.0.x have the patched services.jar in them already, so don't panic if it doesn't ask you. Thanks to the devs for making supercharger installation easier
If you're having troubles on JellyBean, you might want to check out this post and the ones after it:
http://forum.xda-developers.com/showthread.php?p=31675038#post31675038 (Thanks to TheGratefulDead, hit his thanks button!)
1. Download the script from here
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
I downloaded Update 9 RC10 (tested up to U9RC11T6 working too) and also download the starter kit. Extract starter kit to the root of your sd card
2. Download script manager and busybox installer from the play store. Install latest version of busybox
3. Open up script manager, click on root when it comes up. Navigate to the supercharger starter kit folder, and click on the script 'start me up.sh'. Run as root by clicking the little superuser android icon, and let it install by following the instructions, they are easy to follow. When some, close the script
4. Now go back to the root of your sdcard in script manager and open up the V6 supercharger script and root permission, let it do what it has to do. Follow the instructions. When it asks you about a patched services.jar, say yes, and automatic install, it will automatically download and install. For reference, I used the 768HP settings on an AOSP ROM like ice cold and I used the min free calculator settings on sense ROMs like ARHD and project x
5. When is asks you, do a superclean and restart, your phone will reboot. If at any stage it stays on the splash screen for more than 5 mins, restart with adb or by holding vol down, vol up and power for 10 seconds. Avoid pulling the battery as it can cause bricks
6. After your phone reboots, go to /system/etc/init.d and click on the 99supercharger script. Set it to superuser and run at boot.
This is not needed as proven by some people but I recommended doing so, it won't cause harm to do it
7. reboot again
8. Go back to the installer script (the update9RC10 one or whatever you used) and run it again. It SHOULD say 100% supercharged. If it doesn't, you've probably done something wrong or you have an incompatibility
9. Press thanks for this post and zepplinrox's post for the supercharger
He worked hard to deliver this to us and I spent ages writing this
Click to expand...
Click to collapse
Any questions, post here but read through the posts, ask google or use search before asking, your question may have already been asked
Any errors in the guide or if I am not thorough enough for you, lemme know
If you guys need pictures I can post them
Happy supercharging!!
Sent from my Nexus 7
Pro tip:
The further down the menu list the supercharger setting is, the more aggressive it is
I.e 256mb settings will not close apps often
1000hp settings will close apps frequently, not recommended for this device
I would say to use either 512mb or 768 hp settings, or the min free values
Aggressive settings = more apps closed = more free ram
Lenient settings = apps left open = less free ram = more multitasking!
BUT 768hp settings on the ice cold ROM or any aosp ROM will give decent multitasking
If you're unsure about something, ask
Enjoy
Sent from my Nexus 7
The Almost Project Butter hack/tweak, thanks to flak0
Original post here: http://forum.xda-developers.com/showthread.php?t=1855722
The "almost project butter" build.prop tweaks, credits to flak0 from the GS3 forums
Press his thanks button!
flak0 said:
This is an attempt to speed up our GS3 faster than stock and somewhat close to JB and provide odex benefits to both system and data without having to Odex .I have been running this for 48 hours and wow.
Just follow the steps below. Any feedback is appreciated.
The dalvik dexopt flag change were found through research of android and the internet. Below is the procedure to get some serious butter melted from our Gs3 along with a smooth ride.
NANDROID-BACK UP- YOU HAVE WARNED
Step 1: Back up current build.prop
Step 2: Open current build.prop with a root explorer, any will do.
Step 3: copy and paste the lines below to the bottom of your build.prop
Step 4: comment out with # any existing lines that contain dalvik.vm.dexopt or windowsmgr.max_events_per_sec
Step 5: Save your build.prop make sure permissions are set correctly 0644
Step 6: reboot into reocvery and wipe dalvik cache(this is extremely important)
Step 7: reboot, dalvik cache will rebuild
Step 8: Enjoy the buttery smooth gs3
Code:
#Odex Tweaks
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v,m=y
#UI Tweaks
windowsmgr.max_events_per_sec=300
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.ui.hw=1
ro.ril.disable.power.collapse=1
Click to expand...
Click to collapse
Follow the instructions. Don't worry about where it says "GS3" because it works on our device too, I am pretty sure its universal.
You can either delete or put a # in front of repeated lines. A # means it is not active/read.
Make sure to go to the linked thread and thank the person who originally posted the tweaks!
If you're up to it, or you can post some screenshots
Either I will happily post or link to in the op
Sent from my Nexus 7
markj338 said:
If you're up to it, or you can post some screenshots
Either I will happily post or link to in the op
Sent from my Nexus 7
Click to expand...
Click to collapse
If I were to take screenshots and upload it here, this thread will be flooded. So I'll pick the exquisite way of doing a tutorial
Sent from my potato chips using xda qwertyuiop
Thanks for the tutorial. It's good to see something written specifically for our device.
Wow, I installed as your instructions and it went great, 8.3 Rossi is now smoother and quicker than ever. THANKS FOR THE GUIDE, cause without it I probably wouldn't have tried it. Thanks for sharing!
Sent from my Incredible S using xda premium
Good one Mark
i spent the better part of a Saturday trying to figure out from the original thread
this should help a lot of ppl and i think everyone should use the supercharger.. it's really awesome
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
And i think this should be STICKIED..
Just sent a request for it to be
zukri90 said:
If I were to take screenshots and upload it here, this thread will be flooded. So I'll pick the exquisite way of doing a tutorial
Sent from my potato chips using xda qwertyuiop
Click to expand...
Click to collapse
Alright, good luck with it just don't record it with an iPad or something with low resolution
letmedanz said:
Good one Mark
i spent the better part of a Saturday trying to figure out from the original thread
this should help a lot of ppl and i think everyone should use the supercharger.. it's really awesome
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
And i think this should be STICKIED..
Just sent a request for it to be
Click to expand...
Click to collapse
Sorry I didn't create it a day earlier
Also, does anyone else agree that stickies don't get read? It's in another tab in the xda app that never gets pressed
No offence but that's the way I see it
And thanks everyone for the positive comments!
Sent from my HTC Incredible S
markj338 said:
Alright, good luck with it just don't record it with an iPad or something with low resolution
Sent from my HTC Incredible S
Click to expand...
Click to collapse
I call my camcorder, screen recorder. There's one in the play store.
Sent from my potato chips using xda qwertyuiop
markj338 said:
Also, does anyone else agree that stickies don't get read? It's in another tab in the xda app that never gets pressed
No offence but that's the way I see it
Click to expand...
Click to collapse
My script thread has 100k views and 1k replies so I guess somebody's reading it (usually not well enough though unfortunately)
Nonverbose said:
My script thread has 100k views and 1k replies so I guess somebody's reading it (usually not well enough though unfortunately)
Click to expand...
Click to collapse
At least its being read, but people will search for yours too
thanks for your thoughts though mate
And your script is amazing, plenty of threads link to it
Sent from my Nexus 7
markj338 said:
Hey all, i have been asked a few times lately how to install the v6 supercharger
So I have decided to finally make a tutorial thread
-=The V6 SuperCharger=- brought to you by zepplinrox
Original thread: http://forum.xda-developers.com/showthread.php?t=991276
If you're thinking whether or not to install the script, areas all the positive comments in the thread
This will work on every ROM with a init.d folder in /system/etc/init.d
I haven't tested this on ROMs without one!
but its tested on nearly every incredible s ROM and on about 5 nexus 7 ROMs. You can use this guide on nearly every device, its universal as long as you meet the requirements
Disclaimer: I, or zepplinrox or anyone here am not responsible for any damage caused to your phone. No one is forcing you to do this.
I did not impregnate your daughter or son
That said, its easy if you know what you are doing.
So, how to install on GB, ICS and JB
note: gingerbread does not need the patched services.jar so ignore that part if you are using a gingerbread ROM
Any questions, post here but read through the posts, ask google or use search before asking, your question may have already been asked
Any errors in the guide or if I am not thorough enough for you, lemme know
If you guys need pictures I can post them
Happy supercharging!!
Sent from my Nexus 7
Click to expand...
Click to collapse
THANK YOU , quick question.. can i use the layout type thing you done in your sig? i like how you have the phone name then the mods seperated by |
naathaanb96 said:
THANK YOU , quick question.. can i use the layout type thing you done in your sig? i like how you have the phone name then the mods seperated by |
Click to expand...
Click to collapse
What do you mean? Are you asking for permission or how to do it?
Cause if its permission of course, I didn't come up with the idea
Nonverbose convinced me to change it because it was too big lol
Sent from my Nexus 7
markj338 said:
What do you mean? Are you asking for permission or how to do it?
Cause if its permission of course, I didn't come up with the idea
Nonverbose convinced me to change it because it was too big lol
Sent from my Nexus 7
Click to expand...
Click to collapse
i didnt wanna make it look like i was stealing your sig
naathaanb96 said:
i didnt wanna make it look like i was stealing your sig
Click to expand...
Click to collapse
Oh alright, that's okay anyway, I see it as setting an example
BACK ON TOPIC
has anyone used the guide yet? It definitely works because I install the script every few weeks when I flash a new ROM
Just wanting to know if there is enough depth/clarity
Sent from my Nexus 7
markj338 said:
Oh alright, that's okay anyway, I see it as setting an example
BACK ON TOPIC
has anyone used the guide yet? It definitely works because I install the script every few weeks when I flash a new ROM
Just wanting to know if there is enough depth/clarity
Sent from my Nexus 7
Click to expand...
Click to collapse
it deff felt alot faster after a reboot. it seems to open things quicker . ill give it some time for that supercharger to set in haha.
naathaanb96 said:
it deff felt alot faster after a reboot. it seems to open things quicker . ill give it some time for that supercharger to set in haha.
Click to expand...
Click to collapse
It doesn't really need to settle like a ROM does, just open apps as you normally would and it will be in effect like the script says something like 'supercharge in effect immediately'
since your x5 has less ram than the incredible s, it would probably be a good idea to put it on that I find supercharger more effective when the ram is running low, like on sense ROMs or low ram devices
Sent from my Nexus 7
markj338 said:
It doesn't really need to settle like a ROM does, just open apps as you normally would and it will be in effect like the script says something like 'supercharge in effect immediately'
since your x5 has less ram than the incredible s, it would probably be a good idea to put it on that I find supercharger more effective when the ram is running low, like on sense ROMs or low ram devices
Sent from my Nexus 7
Click to expand...
Click to collapse
my mums using the x5 atm until she gets a iphone 5 when they come out lol. im trying to make her get the galaxy s3 or next galaxy device so i have something to play with but yeah the x5 has a custom rom on it so ill tell her im updating it then put supercharger on it
naathaanb96 said:
my mums using the x5 atm until she gets a iphone 5 when they come out lol. im trying to make her get the galaxy s3 or next galaxy device so i have something to play with but yeah the x5 has a custom rom on it so ill tell her im updating it then put supercharger on it
Click to expand...
Click to collapse
I Hate messing with other peoples devices
Especially when they ask me to do it, I don't feel safe to do it
I was recently asked to do a gs2 but I have never touched a rooted one, I don't want to be screwing around with one
Then again, this is your old phone so totally understandable mate
Sent from my Nexus 7
Here is my port thus far:
X Disclaimor - Rom does not boot meaning this is not working yet X
I think since sense 4 was obtainable I'd like to think Sense 3.6 is too.
Now, i'd like to ask for a little help if anyone is available.
Plus, I know developers because I am one; we have an insatiable palette for a good project.
I've discovered two things that have made me feel like i'm stuck:
4/12/2013
1) I am not sure what else I can remove from the system dir to decrease the size to what is needed ~ 272524902.4 bytes (259.9Mb)
The Roms system dir is ~274083573.9bytes (261.4Mb); I basically need to know what else I can get rid of that equal up to 1558671.5 bytes (1.5Mb)
Here's the catch- I already took out the weather from media and apps and have symlinked them from the data partition.
2) I am not sure if I have correctly made the kernel.
I have a boot.img from the sense 3.6 rom i used to port. And I added the bootclasspath from the base kernel.
I also have renamed the proper files that needed to be renamed with inc.
Update: 4/13/2013
I've shrunk the system/usr dir down and now the port is under the size limit.
I have also tinkered with the boot.img more. Can someone check it to make sure that I have done is okay..
`Link in my sig:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So far I've symlinked system/media/weather to data/system.weather and the system/app dir to data/system.app.
This is what i'm using:
symlink("/data/system.app", "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.app");
symlink("/data/system.weather", "/system/media/weather");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.weather");
Do you think i could do the same with the system/vendor dir?
Edit: Don't need to worry now that the current port's system partition,which is now uploading, will be under the size limit.
*Bumpdated*
v1_1 Upload
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
ChemicalSymphony said:
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
Click to expand...
Click to collapse
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
tiny4579 said:
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
Click to expand...
Click to collapse
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Tribulattifather said:
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Click to expand...
Click to collapse
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
zachf714 said:
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
Click to expand...
Click to collapse
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
zachf714 said:
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
How about the latest evervolv ICS release. That's what pure pulled from I believe.
@zachf714:
I will look also. If I find any, i'll upload them to the working folder i created for the project.
And if you guys find any, link me here and i'll download and do the same thing.
@tiny4579:
On the Luxe Rom we worked.. I don't have any of the files anymore. Do you happen to have a rom.zip of the project?
@project Community:
I've uploaded the Rom I used to port with to the dev host - droid in working folder.
I'm about to upload the other Rom I used.
Both the base and port rom I used to make the WIP are uploaded now.
Cm9 http://goo.im/devs/invisiblek/dinc/.../dinc-CM9-invisiblek-KANG-09-03-2012-1608.zip
This was actually the most stable ICS ROM I ran
Sent from my Nexus 7 using Tapatalk HD
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
zachf714 said:
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
Click to expand...
Click to collapse
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not until I just forked it and yeah you did
Damn. Wish I wasn't in bed already.
I'd compile pures git and see if his kernel does anything with the WIP.
My kid gets on the bus at 7:50a (est) and will Dev a bit before I get going for the day.
But if someone tries before then let us know the outcome.
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Tribulattifather said:
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Click to expand...
Click to collapse
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
zachf714 said:
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
That is exactly what I thought so took care of that hahaha.
Right now, imo, I'm thinking it's a lib problem from my recent logcat.
I'll hop on in a few minutes and take another logcat and upload it.
(I deleted the one I had because I hadn't realized that you all might want to take a look too)