Updated:
Changelog:
1.0
remove amazon apk
optimize all png's
optimize zips
based on new build
added su and superuser.apk
apps2SD enabled (requires FAT32 and EXT3 partitions on SD)
Wireless Tethering
Wired Tethering
added task killer tweak for speed
removed OTA
added systemro and systemrw - thanks jamezelle
Changed permissions for ADB to root
USB debugging on by default
Added Terminal
Added flash_image (for future ease when upgrading recovery images)
Added sqlite3
Added Market fix - thanks jcase
Added Overclocked kernel to 710mhz (767 didn't seem stable on everyone's phone)
Added SetCPU
Modified kernel to work with SetCPU's Autodetect
Warning: This is alpha. I don't have an eris to test this on.
Also, some phones won't be able to handle the speeds.
0.8T2
All changes from 0.7 but based on bugless 0.5.5 build (that was never released) without the De-odexing so no more FC's and other bugs.
Added systemro and systemrw - thanks jamezelle
Added wireless and wired tether apps
http://www.multiupload.com/4JGKZHXT40
0.7 Since 0.5.4:
Optimized all the pgn's in all the apk's
De-odex'd all apk's and frameworks
Zipaligned all apk's
Changed permissions for adb to root
Changed symlink to bin/ifconfig busybox
The png's and zipaligning will minimize the RAM usage of all preinstalled apps.
0.7 - http://www.multiupload.com/GN6IUOVU5G
Thank you Wes Garner for the tips on deodexing.
Based on the newest 2.1 leak - A lot of fixes by HTC
USB Debugging on by default in ramdisk
fixed su/superuser issues
Updated busybox and moved busybox symlinks to /system/xbin/bb
Removed su from xbin since it's already in bin
Added TERMINFO and libcurses to fix nano
Added flash_image for future ease when upgrading recovery images
Added sqlite3
Disable OTA (rm SystemUpdater.apk)
Changes to init.rc in ramdisk for busybox and TERMINFO
Build number now shows version number but not showing in Settings
Kill amazonmp3 app (it sucks up RAM like nobody's business)
Downloads
http://www.multiupload.com/VT874ICFFX
Don't have time to really give you a thorough intro at the moment, sorry.
Make sure to WIPE before you flash from another ROM.
Downlaoding now will flash to it tomarrow sometime thanks
Lol as soon as you put it someone put in on the irc.
Question:after this it shouldn't be full flashes and be just minor updates to the rom?
Or are they going to be full flashes? I think I asked you before but don't know if you answered.
will this unroot my phone
ivanmmj said:
Make sure to WIPE before you flash from another ROM.
Click to expand...
Click to collapse
what will happen if didn't WIPE?
Ivannmj will you allow your rom to be used as a base for other roms?
acually flashing now... so far so good ill edit the post when im done
ok, installed and working so good thanks
so ummm... ::squint:: how... do... u... wipe?
...
tonyfiasco said:
so ummm... ::squint:: how... do... u... wipe?
Click to expand...
Click to collapse
A) do you have root access on your eris?
and
B) have you put a recovery image on your eris?
tonyfiasco said:
so ummm... ::squint:: how... do... u... wipe?
Click to expand...
Click to collapse
no comment.
from recovery img, select wipe, choose factory reset, and wipe dalvik
jcase said:
no comment.
from recovery img, select wipe, choose factory reset, and wipe dalvik
Click to expand...
Click to collapse
I'll assume you have root and Recovery already.....
Does anyone have the md5 hash for this?
pkopalek said:
Does anyone have the md5 hash for this?
Click to expand...
Click to collapse
MD5: 182ACEC321A44D14F8734E249D0ED1D7
I have updated this rom, works great!
I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?
Morkai Almandragon said:
I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?
Click to expand...
Click to collapse
No this rom is for root users. and i dont know about that issue, i havent heard of that issue, im running the newest 2.1 leak and everything seems fine to me
Morkai Almandragon said:
I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?
Click to expand...
Click to collapse
Not at all. There is similar data in this one, to the one you're referring to.
The image of the one you're referring to is NOT a Root image.
it's a normal image. If you have a problem like that, try reflashing it, checking the md5 hash on that - making sure it matches someone else's that works AND/OR, just re-download the file.
Either way, you probably want to re-flash that PB00IMG.zip. But if you reflash it and the same problem happens, you will want to re-download it, or check to make sure the file is 100% intact.
<sigh> I am flashing more now than with my 6800, 6950, and Omnia combined
Can anyone verify which information is missing from Settings > About Phone > Software information?
Is it Kernel version? Build number? Software number?
pkopalek said:
Can anyone verify which information is missing from Settings > About Phone > Software information?
Is it Kernel version? Build number? Software number?
Click to expand...
Click to collapse
No information is missing in my phone, all fields are filled. Just flashed this ROM this morning and so far so good....
how does this compare to the 2.1 OTA root ROM?
I'm running evil eris right now, starting to get fed up with the bugs interfering with the necessary usage of my phone.
I am on the forums daily, but I'm getting confused with all the updates coming out and which one(s) are better than others.
Related
1) not for use with sense
2) jit is in beta
3) These are the same binaries as the original JIT.zip floating around, this just properly sets up your build.prop instead of flashing an outdated ones that does not work will all roms.
If people would like to see a jit on/off switch app just let me know. Binaries were from the original eris jit update ivan gave me.
Stop using JIT.zip
http://www.multiupload.com/PIFU7GNSR5
Make backup first, doesn't work don't grip. At your own risk, no support provided.
Step 1: download the zip put in sdcard
please
Step 2: Run these commands
adb remount
adb shell "busybox sed -i 's/#dalvik.vm.execution-mode=int:jit//g' /system/build.prop"
adb shell "busybox sed -i 's/dalvik.vm.execution-mode=int:jit//g' /system/build.prop"
adb shell "echo dalvik.vm.execution-mode=int:jit >> /system/build.prop"
Step 3: reboot to recovery, wipe dalvik cache, reflashe zip
To undo
Step 1:
adb shell "busybox grep -v int:jit /system/build.prop > /data/local/tmp/build.prop"
adb shell busybox cp /data/local/tmp/build.prop /system
Step 2: reboot to recovery wipe dalvik
totally awesome!! thanks jcase! I would love to see an app just to simplify the process
Has JIT been modified enough to "play nice" with SENSE based ROMS?
Riley1524 said:
Has JIT been modified enough to "play nice" with SENSE based ROMS?
Click to expand...
Click to collapse
Its JIT, bound to be unstable. No modifications to the binaries were made, just different way of applying it.
Cool!!! Be nice just to try it out. Thanks!
hmmm
Riley1524 said:
Has JIT been modified enough to "play nice" with SENSE based ROMS?
Click to expand...
Click to collapse
i thought these were for vanilla roms only
*votes for on and off switch app*
doing this now on my port, ill edit post saying how it went
thanks
DS36 said:
i thought these were for vanilla roms only
Click to expand...
Click to collapse
I knew that it was, just wasn't sure if anything was modified to work better with sense
so far, I have not been able to get JIT running stable on any of the roms that I've used
I'm on EE 2.0 with zanfurs OC patch @ 768mhz. I ran the sense remover from zifnab's site. Installed the Open GL patch (don't know if that mattered). Rebooted the phone, but the phone would lock up and reboot whenever sliding the phone to unlock. So the i flashed the Nexus One Screen Lock and rebooted. But when i went to unlock the phone that time, it didn't reboot and i pressed the home button and set Nexus Launcher as default. It seems to work fine now with no reboots. The highest i got in Linpack was 5.24 MFLOPS. Just don't know if i like the way the Nexus Launcher looks
Sense-able 3.1 with zanfur's v3 OC patch; same results, go to unlock the phone and it reboots.
/restore
+1 for the on/off app!!
EDIT: does not work with Ivans eris offical 1.0
Strangely lowered my MFLOPS from 2.8-3 to 1.7. Seems fishy. I will give it another attempt in when i have more time to experiment with it.
edit: I apparently suck.
Spencer_Moore said:
Strangely lowered my MFLOPS from 2.8-3 to 1.7. Seems fishy. I will give it another attempt in when i have more time to experiment with it.
Click to expand...
Click to collapse
I'm chiming in to confirm this works
on tainted vanilla 1.3.1 I just got 5.61 using this update
Thanks for all your work jcase
I can confirm the reboot.
Sense-able 3.1 (based on v3 leak) locks-up then reboots as soon as as I go to unlock phone. I tried it a few times to be sure it wasn't a fluke.
No JIT for me.
EDIT: I forgot to mention that I appreciate all the work you do despite this time it not working out for me.
br125 said:
I'm chiming in to confirm this works
on tainted vanilla 1.3.1 I just got 5.61 using this update
Thanks for all your work jcase
Click to expand...
Click to collapse
wow... I had to try....
got 5.195 using same set up! Fast!
edit: 5.3!
Any one use this on the 2.1 v4 leak ROM with success?
Code:
Originally Posted by jcase
Um its the same damn files, minus the build.prop that is from LEAK VERSION ONE in jit.zip.
ie EXACTLY THE SAME THING.
*edit*
im a moron occasionally.
FYI for those comparing it, it is completely the same binaries.
jcase said:
Um its the same damn files, minus the build.prop that is from LEAK VERSION ONE in jit.zip.
ie EXACTLY THE SAME THING.
Click to expand...
Click to collapse
Wow. I'm not saying you did anything wrong with the update. Maybe my flash was bad. But it did work with grdlocks jit. geez man... smoke a cig or something. I never said u messed anything up.
ROM: (HonnyComb)
Here is an ACER 3.2.1 near stock android image installable via clockwork recovery.
(Tested on a Wifi only acer a500)
[size=+2]acer7.014.14_CUST_ROOT_BBv4_S.zip[/size]
(MD5: cfd6ecee33891cc8e6e2625e8ea89511)
Note: April 30, 2012: The stock kernel will work both on HoneyComb and unlocked (v3) ICS bootloaders
Note: May 18, 2012: The update, no wipe required, to this ICS rom is now posted here this thread will remain for anyone remaining on HC
Simply install via clockwork or RA recovery; if you have a rooted and mostly unmodified version of HC 3.1/3.2 currently it may be possible to use this install without a wipe (4.010.41 users are likely to have the best results); However make sure you backup first just in case.
Users of the previous (acer7.006.01_CUST_ROOT_BBv2) version may safely upgrade without a wipe however the following is recommended: 1) wipe dalvik cache in the advance menu of CWM recovery, 2) you may need to the apps menu to get the new market icon (my previous homescreen shortcut was no longer valid but the one in the app list worked without a problem, as making a new shortcut)
Last if you notice slowdowns or forcequits withing 24/48h of upgrading before reporting them try going into recovery and running both "fix permissions" and "clear dalvik cache" then boot the tablet waiting for the logon screen to appear and the screen to dim and turn off before using the tablet. At this point you van use the tablet normally.
This file is based off the OTA update: Acer_A500_4.010.41_7.006.01_COM_GEN1_1315966386585_07733ac7.zip subequently updated to 7.014.14_COM_GEN1 by manually extracted these images
(As was sent via OTA here in canada)
Modification Log:
I've made the following changes to the original OTA files:
decrypted and configured for installation from clockwork recovery
remove the bootloader flash (Separate analysis will be required to tell if this is safe) If so it is still not useful in a rooted Clockwork rom install, since in future it may become a downgrade not an update.
remove recovery flasher
remove both OTA cert and original ca_certs in favor of the cacert by guardianproject
Add a version of busybox (built in my HTC Dream rom ezGingerbread build tree using target utility_busybox from the commit https://github.com/CyanogenMod/android_external_busybox/tree/995d0d35bde285)
make busybox the default shell
Include Superuser/su
configure runparts (runs scripts in /system/etc/init.d) only a "Welcome" script is included however if you wish to run any script on startup you can do so by adding them to your /system/etc/init.d directory)
Note this rom is still odexed
(v2) fix she-bang on am, bmgr, ime, input, monkey, pm, svc shell scripts
(v3) incorporate "Skype Fix" into rom, thus no need to flash a second file to fix skype video calls (obviously you still need to install skype from market)
(v3) incorporate "wifi fix" for infinate DHCP leases, unfortinatly this was still not working in the base rom, however the fix is now part of this install.
(v3) uninstall Future Dial (acer updater) this prevents the system update from appearing in the menu/background, as it won't work anyway with the modificaitons
(v3) rebased to Acer A500 7.014.14_COM_GEN1 (previously 7.006.01_COM_GEN1)
(v3) SuperUser updated to v3.0.7
(v3) Set wifi only by default (if you need otherwise you will need to comment out the last line of the build.prop file, information in the comment above said line)
(v4) Remove extra market related files (merge errors from the acer patches); this ensures the new version of market runs properly (thanks to civato for pointing this out)
* entries starting with (vN) - indicates fixed/added in version N, ie (v2) indicates fixed in version 2 and on
Additional Information:
This is a very simple set of changes that ought to allow rooted users looking for a basic version of Honeycomb 3.2 (and now 3.2.1) safely update without loosing root. Its intended for users that wish a minimally modified rom with root. Either to be used as a rooted stock rom as is; or to be a base to make other small modifications as needed.
As such I'm more likely to provide addons than changing the base rom its self. (excluding any bugs of my creation or new official releases form ACER)
Note the kernel is the stock kernel from acer. Acer's A500 kernel source code can be found at here
FYI: You may use this as a base for other roms as long as credit is given with a link back to this thread where reasonable.
Add Ons
~~-- Stock Kernel Modules --~~
Here are some kernel modules for the stock acer kernel
(Tested both on acer7.006.01_CUST_ROOT_BBv2_S, and acer7.014.14_CUST_ROOT_BBv3/acer7.014.14_CUST_ROOT_BBv4)
tun.ko
md5: bf93f2538c875f0f397f43f225bd595b
cifs.ko
md5: 86b936fb269daa1f688f3f8535c36c23
Since I'm having problems with a corrupt tar.gz file with the latest posted [by acer0] a500 kernel code; these have been built from the a501 version with a a500 config. (the "Application Guide (for Android 3.2 HoneyComb" posted on 9/19) Hopefully this will not be an issue but let me know if you have any issues with the modules (I've checked they load but not that they are fully functional)
~~-- Villain Iconia Kernel --~~
(Tested both on acer7.006.01_CUST_ROOT_BBv2_S, and acer7.014.14_CUST_ROOT_BBv3/acer7.014.14_CUST_ROOT_BBv4)
Here is a re-bundle of the Villain Iconia kernel (original zImage form richardtrip) The installer however has been modified since we now need a new ramdisk image than the one previously bundled with the kernel.
V3.7
acer7.006.01_CUST_ROOT_BB_Villain_iconia_kernel_3.7_S.zip
md5: 57908bd9d8fda3902cc24ebb23de9e6c
Previous verison:
acer7.006.01_CUST_ROOT_BB_Villain_iconia_kernel_3.4_S.zip (md5: 8c6c0783a961d65d465a3f3dccffbfb3)
For more information including source code see Villain_iconia_kernel_3.4.zip from Stock/HV/Taboonay V3.4 for HC 3.2 10-09 - 1.64Ghz/UV control
(This will let you overclock and access some more modules, but I've found the stock kernel overall more stable)
--------------------------------------------------------------------------------------------------------------------------------------
[Size=+1] The following is only for the previous acer7.006.01_CUST_ROOT_BBv2_S version:[/Size]
---------------------------------------------------------------------------------------------------------------------------------------
~~-- Wifi Dropouts Patch --~~
If you are having issues with your wifi connections it is recommended to check your router doesn’t have indefinite DHCP leases
However if you can't prevent the indefinite lease a patch for such dhcp connectivity problems is available:
wifipatch_7.006.01v2_S.zip
MD5: 39c0a1cdd755458eb6edd6aa786e4f5f
Additional details here
(Note this have been built in on V3 and thus is no longer needed)
~~-- Skype(tm) Patch --~~
Fixes video calls on market skype client
skypepatch_7.006.01v2_S.zip
MD5: 99cadf8c5b8eca25aa60b38aa83ec91a
Flash from recovery; and install skype form market as usual (or open it if already installed) video options will appear in settings.
Details of the problem/solution and the patch are in this post
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- Netflix --~~
Install from market:
https://market.android.com/details?id=com.netflix.mediaclient&feature=search_result
If you previously installed a modified version such as the one modified to play on the a500 without breaking video you will need to uninstall the modified version prior to installing the market version.
~~-- Cell Standby fix/option --~~
If you are seeing Cell standby in your battery use simply add ro.carrier=wifi-only to your build.prop
Via adb:
Code:
adb remount
adb shell
echo 'ro.carrier=wifi-only' >> /system/build.prop
sync
reboot
Via terminal/local connectbot
Code:
su
mount -o remount,rw /system
echo 'ro.carrier=wifi-only' >> /system/build.prop
sync
reboot
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- SuperUser 3.0 update --~~
We need to flash the rom manager update, but as rom manager is not yet working on this tab get the update zip and flash in recovery:
su-3.0-efgh-signed.zip
Md5: c05902fdf90f7635c711e4dcd1c32c45
(Note this has been built in on V3 and thus is no longer needed on that version)
~~-- Previous Versions --~~
[size=+1]v1: acer7.006.01_CUST_ROOT_BBv1_S.zip[/size]
(MD5: df11f6a309f34ac4c0209aded4ca3f20)
This version had an error in the she-bang of the included scripts such as pm, v2 corrected this to the expected '#!/system/bin/sh'
To save bandwidth I'm not providing the original file; however you can re-generate it with the following binary diff:
On a linux computer with the bsdiff package installed run:
Code:
bspatch acer7.006.01_CUST_ROOT_BBv2_S.zip acer7.006.01_CUST_ROOT_BBv1_S.zip acer7.006.01_CUST_ROOT_BBv2_to_v1.bsdiff
Using the v2 version and acer7.006.01_CUST_ROOT_BBv2_to_v1.bsdiff
[size=+1]v2: acer7.006.01_CUST_ROOT_BBv2_S.zip[/size]
MD5: b254140896742f3deec464c094fb2515
Longtime running version very stable, however some users have had some minor issues correctable by the above patches.
[size=+1]v3: acer7.014.14_CUST_ROOT_BBv3_S.zip
[/size]
MD5: c734317089d323dffde9c7d4fe7afce4
Inital upgrade to 7.014.14 had some issues with extra market related files, if you are running this version it is recommended to upgrade to V4 or (if you wish to avoid the download and the cost to me of the bandwidth) follow the instructions here to manually make the same change yourself.
Does Netflix work or do you still have to use a patch
Sent from my Nexus S 4G using XDA App
ruffjd said:
Does Netflix work or do you still have to use a patch
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I still needed the patch (you will need to apply it by hand)
I hear rumor's [but have not spotted it first hand] of some library that works with both camera and the library.. if I find that one I'd be happy to make a flash-able patch.
Also looking at the Stock/HV/Taboonay kernels, since he is not extracting the ramdisk from the existing boot.img it looks like they will not be 100% compatible with this rom out of the box. (will make something up shortly)
10/2: see note one netflix
Thanks, Working Great
I flashed from 4.010.13 without a full wipe without any issues. I cleared cache, wiped dalvik cache, and flashed. Thanks for your work. This ROM will be very useful for those of us that want to retain root and take advantage of the stability that the stock ROM brings.
Small bug with shell scripts such as pm, This can cause problems with rooted applications expecting them or adb commands, to fix just grab the updated version at the top of the op acer7.006.01_CUST_ROOT_BBv2_S.zip
If you already updated you can safely flash this new version over your current one; however if you subsequently changed items in /system (such as the netflix hack) you will need to make the change again after the upgrade.
Apologies for missing this in my initial testing last night. (my fault for working on this practically while sleeping..)
.. and A501 3G
why is it that when scrolling apps or scrolling of the home screen became sluggish after installing 3.2?
superbar said:
why is it that when scrolling apps or scrolling of the home screen became sluggish after installing 3.2?
Click to expand...
Click to collapse
If you had a non stock rom ported from another device it could be just incompatible data and a wipe is needed.
If it was a stock rom it could be a data issue try wiping dalvik cache and running fix permissions in recovery.
It could also be something ypu have installed. (Widgets in particular)
I see no slowdown really I don't see much difference from a user perspective from 3.1.
Börger said:
.. and A501 3G
Click to expand...
Click to collapse
This is a a500 stock rom with root modifications..If it works on a a501 great.. but if not I can't support it.. its another device.. Likely 3g will fail.
If works or you have a patch for me to make it work feel free to let me know however.
I wondered how you got the OTA when you have A500_4.010.41 originally ??
I thought North America the latest HC3.1 was version A500_4.010.13_COM_GEN2 ??
anyway...
I am on A500_4.010.13_COM_GEN2 rooted with CWM... should I go ahead and flash this ??
I understand that it will keep root... and since I will have root... I guess I can use "Acer Recovery Installer" to re-install CWM ??
and freaking Acer !!!... we were on GEN_1 originally awhile back (HC3.0.1)... then went on to GEN_2 (HC3.1)... now with HC3.2 they are back with GEN_1 ??... freaking confusing idiots !!
and the A501 is keeping this format (4.015.01)...similar to HC3.1 format !
while us A500 is going to this format (7.006.01)
Side note:
If we are seeing custom roms for HC3.2 keeping root..etc... why can't dev managed to root stock 3.2 ??
and is the CWM recovery working for 3.2 ??
UnicornKaz said:
I wondered how you got the OTA when you have A500_4.010.41 originally ??
I thought North America the latest HC3.1 was version A500_4.010.13_COM_GEN2 ??
Click to expand...
Click to collapse
No clue was what the device auto updated to what I had, then I rooted (+ intercepted the OTA last night).. I don't know the regions ACER is using.. butthe tab was purchaced at a local staples.
UnicornKaz said:
I understand that it will keep root... and since I will have root... I guess I can use "Acer Recovery Installer" to re-install CWM ??
Click to expand...
Click to collapse
The update I've provided won't touchrecovery, so you keep your current recovery and thus can restore your backup even if you mess up the rom.
You also will have root so you can re-flash reocvery if something goes wrong. But likely won't need to.
Last I'm not touching the bootloader so that will also remain as is.
UnicornKaz said:
Side note:
If we are seeing custom roms for HC3.2 keeping root..etc... why can't dev managed to root stock 3.2 ??
and is the CWM recovery working for 3.2 ??
Click to expand...
Click to collapse
Keeping root is diffrent from rooting the new system:
To keep root I pull the update zip from the system without letting it install, then I decrypt it (since acer encodes it) unzip it, then manually add/remove files to the update zip before installing via clockwork.
This way I don't need root to install superuser/su on a locked down system, but just install it via clockwork with the correct permissions.
Also recovery is seperate from the andoid system (seperate linuxkernel/ram disk from the main boot kernel/ramdisk) We need not touch it when installing a rom (even if most stock roms by default like to reflash recovery.)
I flashed my Packard bell libertytab with this rom and everything is just fine.
CWM and root.
Thanks.
Edit: I got the Thor 3.4 kernel running on it and it is fast.
24/7 at 1544MHz and even 1680 is no problem with it.
Max cfbench overall score is 9175.
my only problem is that the OP doesnt sound too sure of himself if this rom is even any good
thats just the feeling i got after reading his first post
it almost sounds like you dont have an iconia to test this on.
i do hope i am wrong. i guess i have not seen anyone post a rom and use the words in the manor you have. it just made me feel uneasy about if the rom even works.
Sent from my A500 using Tapatalk
v_lestat said:
my only problem is that the OP doesnt sound too sure of himself if this rom is even any good
thats just the feeling i got after reading his first post
it almost sounds like you dont have an iconia to test this on.
i do hope i am wrong. i guess i have not seen anyone post a rom and use the words in the manor you have. it just made me feel uneasy about if the rom even works.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I have an icona.. and its running the rom.
But the OTA hasn't even been out 24h (rooted or otherwise) so I've not had the time to really put the rom into its paces (nor has anyone else not working at ACER)
The other thing is my position on this rom; That is unless there is (a) a bug in the modifications I did make to provide root and some tools for end users to add their own tweaks; or (b) another official release provided by acer: I do not want to be updating the base rom; it ought to remain nearly as close to the stock OTA as possible (and any exception to this is already defined in my modification list)
Now if you have a interesting addition.. Or I come up with an interesting hack I'm happy to provide/advertise it as an "Add on" that the user may optionally flash on top of the rom to obtain the additional functionality.
(Of course I much rather work on roms with accessible source code.. unfortunately we will not be able to make such a thing until Google releases the source for Ice Cream Sandwich)
Rom appears to work fine fine. Cleared cache and dalvik cache and flashed to my Iconia with CWM from stock 3.1 and voila - 3.2
Flashed the modified HoneyVillain Kernel in post 2 and overclocked to 1504. Everything working fine so far. Netflix working with patch (rear videocam FC as usual).
I'm hoping for better battery life than Taboonay. Maybe it was just me, but I had awful battery life with Taboonay compared to stock.
Bob
---------- Post added at 05:12 PM ---------- Previous post was at 04:44 PM ----------
I should mention after flashing that kernel I put ro.carrier=wifi-only into /system/build.prop to remove cell standby from battery use.
Also, since I didn't do full wipe, this truly came out as an upgrade, since everything on my tablet stayed the sam ein terms of apps and configuration
Scrolling thu home screen is smooth now but scrolling thru apps still lags, not as smooth as 3.1, I wipe my dalvik cache and clean wipe, should I wipe my partition?
As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.
He already explained a few posts before. He took the update, dismantled it and took out the bit that will upgrade your recovery and wipe out the root. Repackaged it and viola! instant magic!
HarshReality said:
As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.
Click to expand...
Click to collapse
HarshReality said:
As I just got the update notice today (US) for 3.2 I suppose the only question I would have is... can you tell me exactly how you did this so I can do it and only have su installed. Dont misunderstand as I appreciate the dev aspect of things but I have yet to see a stock rooted ROM or direction on how to that anybody hasnt 'tweaked'.
Click to expand...
Click to collapse
Most of the "tweaks" in here are you find not as optional as you may think.. Particularly for a distributed product.
However I've not modified any binary files; this means all the changes are either text files or removal/addition of binary blobs thus to see what I've done:
You need the official OTA image and to decrypt it/unzip it information is here:
http://forum.xda-developers.com/showthread.php?t=1113878
(As well on two 3.2 update related threads happening in the a500 dev section)
Once you have unziped the zipfile and update.zip will be visible and is the base of the update.zip for this install.
In that file is system files, recovery flasher files a boot.img (this contains the ramdisk where I have modifications so adb shell works as root look into extracting the ramdisk with cpio) and scripts to help in the installation of the rom.. the updater-script (a few dirs under META-INI) is the script recovery runs.
From here you can compare the files in the official archive with mine, or ignore mine and modify the install to your own liking.
For best results knowing the structure of the files in system and how linux/android boots is important. Otherwise this is a hands on exercise, there is only so much advice I can give,thus looking at the original and seeing what I touched will likely provide insight particularly if your are stuck.
In the case of su/superuser I just pulled from the official zip on rom manager provided by ChainsDD (links at https://github.com/ChainsDD/Superuser/blob/gh-pages/manifest.js ) and placed them into system making sure to add the suid perm on su in the updater-script. This however will not allow adb shell as root or prevent clockwork recovery from being over written.
There is a bit of a learning curve.. even if to me this type of hack is trivial and I only bothered doing it so I could have the 3.2 OTA without loosing root, and without what I think are silly tweaks some other devs add.
suomaf said:
He already explained a few posts before. He took the update, dismantled it and took out the bit that will upgrade your recovery and wipe out the root. Repackaged it and viola! instant magic!
Click to expand...
Click to collapse
Not very technical.. but once you decide to use the rom yes is about how its supposed to act.. And how I hope most of those that have downloaded the image think of it.
When i flash this, and reboot, i hang on the Acer bootup logo. No changes. I can go back into recovery and restore, but i can seem to get this to flash properly. I'd like to have a nice clean minimal 3.2.
I even wiped and did a clean instal, one note it did say
Offset:0x180
Before it said installation complete, it also 'installed' the file far to quickly in my opinion.
For my personal opinion the 200DPI is the best one, it's not to small as 160 and not to big, it's just perfect and compatible with the Tabblet UI.
How to?
(1) Install android SDK Tools download here;
(2) Be sure to check the adb option while installing;
(3) Go to windows Run and open cmd (hotkey is winflag + R);
(4) Now type cd\;
(5) Then type cd "installation path of adb" (prev. cd C:\Program Files (x86)\Android\android-sdk\platform-tools);
(4) Now connect the phone and reboot your'e android in to recovery and go to mount, mount the /system;
(5) Now in the cmd type: adb pull /system/build.prop c:\;
(6) Open the build.prop (located on c:\ drive, main folder) file with any text editor and search for ro.sf.lcd_density=;
(7) After the "=" just put a number like "200" (prev. ro.sf.lcd_density=200);
(8) Save the file;
(9) Go back to the cmd and now type: adb push c:\build.prop /system;
(10) Now type: adb shell;
(11) Now type: chmod 644 /system/build.prop;
(12) Reboot.
Thats pretty much it, i know it looks like, OMG, but it's very simpel if you done it one or two times you will now this without watching this topic again so it will work if you just follow the steps 1-by-1. Now don't be that smartass that says, don't type the "" symbols.
If you got any questions just ask and dont forget to thank
Btw im now responsoble if you done something stupid xD
You do NOT have to do all that to change the DPI. You don't even have to use ADB. Just use ROM Manager or open up the build.prop file in Root Explorer using Text Edit, find the line and change it, save and reboot. Some ROMs have the ability to change in the settings.
This thread isn't really needed in my opinion.
And don't forget if you use a custom dpi other then 320, 240, 160 etc lots of apps in the playstore won't run anymore.
andreww88 said:
You do NOT have to do all that to change the DPI. You don't even have to use ADB. Just use ROM Manager or open up the build.prop file in Root Explorer using Text Edit, find the line and change it, save and reboot. Some ROMs have the ability to change in the settings.
This thread isn't really needed in my opinion.
Click to expand...
Click to collapse
And what about the permissions fix? if you use ROM manager will it automatlicly fix the permissions?
friedje said:
And don't forget if you use a custom dpi other then 320, 240, 160 etc lots of apps in the playstore won't run anymore.
Click to expand...
Click to collapse
Well, all my tabblets apps still work on 200DPI
The app, rom tools lite is doing all that, and more
Just move the slider to the dedired dpi, and apply
Reboot - finished !
Well i didnt new that, im glad i now how adb works now so for the people that likes it just say thank and dont be that *****y. Im going to create a hole tutorial how to flash from stock to Stunner step by step for the noobs under us, sounds good or not?
Edited: ...
Galaxy Note N7000 - PARANOID ANDROID (CM9)
thomasvdalen90 said:
And what about the permissions fix? if you use ROM manager will it automatlicly fix the permissions?
Click to expand...
Click to collapse
Apparently, because I've never had any problems with just changing the build.prop file and rebooting. I never use rom manager, I was just saying it does it if you want an app to do it instead of digging in system files.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
thomasvdalen90 said:
Well i didnt new that, im glad i now how adb works now so for the people that likes it just say thank and dont be that *****y. Im going to create a hole tutorial how to flash from stock to Stunner step by step for the noobs under us, sounds good or not?
Click to expand...
Click to collapse
Ehh....I wouldn't use Stunner right now. Don't get me wrong, it is a fantastic ROM! However, it is still on a faulty kernel and we don't want people bricking their Notes. Do a ROM like Asylum or ParanoidAndroid or CM9 itself. Anything on the CM9 kernel.
But, every OP explains very well how to flash. If people would just read it.
You can use whatever file manager app you want as long as it has root access. Go to /system/build.prop, edit the line, reboot. It takes exactly 7.4 seconds.
(some of you have to change the permissions, so tap menu, permissions/properties and set to RW-R-R, reboot)
request for a move to general threads...nothing new here mate no offence...changing dpi can be done using apps (lcd density modder, rom toolbox etc) or manually by root explorer...and lets leave the tutorials for rom installations to the devs OP...
And this is in development why?
Use density modder app from market..
close thread?
andreww88 said:
Apparently, because I've never had any problems with just changing the build.prop file and rebooting. I never use rom manager, I was just saying it does it if you want an app to do it instead of digging in system files.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
Ehh....I wouldn't use Stunner right now. Don't get me wrong, it is a fantastic ROM! However, it is still on a faulty kernel and we don't want people bricking their Notes. Do a ROM like Asylum or ParanoidAndroid or CM9 itself. Anything on the CM9 kernel.
But, every OP explains very well how to flash. If people would just read it.
Click to expand...
Click to collapse
Why is it faulty? i read something about it but i dont have any problems and i though its the standard kernal.. I flashed abyss kernal to install Stunner for the safe way
thomasvdalen90 said:
Why is it faulty? i read something about it but i dont have any problems and i though its the standard kernal.. I flashed abyss kernal to install Stunner for the safe way
Click to expand...
Click to collapse
Causes the bricking because of the eMMc bug that corrupts your data partition (well, the motherboard is being replaced on those that have been bricked).
andreww88 said:
Causes the bricking because of the eMMc bug that corrupts your data partition (well, the motherboard is being replaced on those that have been bricked).
Click to expand...
Click to collapse
Yeah but i just flashed like this:
1 just odin to gingerbread
2 cf root
3 install abysskernal trough cwm
4 wipe
5 install stunner
6 stunner update
am i on a safe kernal now or not? just wanne now before im gonne flash my girlfriend gNote
thomasvdalen90 said:
Yeah but i just flashed like this:
1 just odin to gingerbread
2 cf root
3 install abysskernal trough cwm
4 wipe
5 install stunner
6 stunner update
am i on a safe kernal now or not? just wanne now before im gonne flash my girlfriend gNote
Click to expand...
Click to collapse
No you are not technically.....because you are on Stunner now. Stunner is not safe. Abyss is a GB kernel so that won't work. Stunner will need updating before it is "safe".
Basically, read the OPs and anything that says "CM9 kernel" is safe right now.
andreww88 said:
No you are not technically.....because you are on Stunner now. Stunner is not safe. Abyss is a GB kernel so that won't work. Stunner will need updating before it is "safe".
Basically, read the OPs and anything that says "CM9 kernel" is safe right now.
Click to expand...
Click to collapse
oww oops didnt new that, but im on stunner now, so if they update its safe? its working now will i be safed if im now flashing anymore? and can i just odin back to GB without risk?
thomasvdalen90 said:
oww oops didnt new that, but im on stunner now, so if they update its safe? its working now will i be safed if im now flashing anymore? and can i just odin back to GB without risk?
Click to expand...
Click to collapse
Abyss is used to restore nandroid backups on ICS since CWM can't.
Well, if you wipe data or do anything with BIG files you could potentially mess up your eMMc by "activating" that bad bug.
Personally, I would immediately ODIN back to GB, root it, and go to a CM9 based ROM.
andreww88 said:
Abyss is used to restore nandroid backups on ICS since CWM can't.
Well, if you wipe data or do anything with BIG files you could potentially mess up your eMMc by "activating" that bad bug.
Personally, I would immediately ODIN back to GB, root it, and go to a CM9 based ROM.
Click to expand...
Click to collapse
I im copiieng big files to my externalsd card theen my phone disconnects from the computer, is that the brick? :O then im already screwed
and does cm9 have tabblet ui?
thomasvdalen90 said:
I im copiieng big files to my externalsd card theen my phone disconnects from the computer, is that the brick? :O then im already screwed
Click to expand...
Click to collapse
External SD card? Umm, I don't think so. I haven't seen that. For your sake, I truly hope not.
Can you boot up? Can you get in recovery or download mode?
Edit:
PM me so we don't keep blowing up this thread with more potential "brick" stuff.
Here is just some of what is changed. Mine isn't just a stock port, mine has stuff removed. dave71670's Salty Rom is in the second post.
Now without further ado, here is my V26 Test Release
Wipe Data/Factory Reset/Wipe Dalvik Cache/Flash Rom/Flash Addons/Advanced Fix Permissions In Recovery. If your power button randomly stops working from flashing my rom or anything else happens and you blame me I am going to laugh at you. If you do not know what you are doing, don't attempt to flash it. If you break it you fix it, I will help, but I am not responsible for anything.
My V26 Test Build = http://www.mediafire.com/download.php?iv6mz6cr82l663p
V26 Addons (Same As V25) = http://www.mediafire.com/download.php?ja32agzq3o82ky3
Removed Apps & Files Folder (Some of them are newer than the old folder) = http://www.mediafire.com/?c0f17oxct7dq5
I am calling it a test release at this point, since I haven't ran it more than about an hour. I haven't had any problems though. If coming from CM10 or something else you will more than likely need to flash twice, first flash will go to around 15% and flash the kernel and reboot, second flash will go all the way and say install complete.
Changelog :
Based on 09/04/2012 Helly Bean
MMS updated with pop up notifications
Added https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&hl=en to the rom since I have noticed people complaining of losing there EFS folder a lot lately. I would download this on your current rom and back it up as long as you imei is correct, just to have it for all future releases of my rom or whoevers rom you decide to go to in case you ever lose your EFS folder which has your IMEI. It is a small app, is free and works great, I tried it by backing it up on my phone and then deleting my efs folder, then restoring it later with this program after I got the generic imei error. Credits go to Helroz for the app
Old Version Still Available V25 Rom = http://www.mediafire.com/download.php?mlet0rdrlduzl8k
My V25 Addons (Same As V24) = http://www.mediafire.com/download.php?0661t2w37jevi98
Link To Folder With Removed Gapps & Files = http://www.mediafire.com/?skubg7sgqbsew[/URL]
Md5 On Rom Zip = 839AC816B9D36E229C4A9344DA54EA33
Changelog =
Compiled from latest source of CM10 which you can find the changelog at http://changelog.bbqdroid.org/#captivatemtd/cm10/next
renamed the two navbar menus
More Build.prop tweaks
Edited Build.Prop Look In About Phone
Kernel in rom is always the latest VC Kernel
Updated GPS Config
Changed Boot Animation, Wait for a few seconds on boot up if you think it froze, It did not.
Changed Modem To KC1
Changed Updater.sh to Flash Modem if you have a modem already installed or not.
I have also created what I would like to call Cbalts Launcher Program. I have 4 launchers in the removed files folder, Apex, Nova, Trebuchet, And Zeam. You can flash any of them and it will remove the default zeam, to get zeam back flash Removal Tool.zip which will remove all 4 of the launchers if you decide to install all four of them at once. Then reflash the launcher of your choice and that will be the only launcher you have. If you do not reflash a launcher after flashing Removal Tool.zip you will not have a launcher. All launchers remove zeam, but the zeam launcher, I set it up that way since zeam is the default launcher. If you want a new launcher, tell me your choice and link me to it and I will make a flashable zip for it.
Removed
Apollo.Apk
CMWallpapers.apk
Development.apk
DevilAppSGS.apk
DevilKernelConfig-0.9.apk
DSPManager.apk
Email.apk
Exchange2.apk
HoloSpiralWallpaper.Apk
Changed LatinIME.apk To Smaller One With English Only
LiveWallpapers.apk
MagicSmokeWallpapers.Apk
Media/Video Folder
NoiseField.apk
Phasebeam.apk
QuickSearchBox.Apk
RomManager.apk
Term.Apk Aka Terminal
Trebuchet.apk in favor of Zeam
VideoEditor.apk
VisualizationWallpapers.apk
VoiceDialer.apk
Replaced Alarms Folder With My Own
It Only Has
Alarm_Beep_02.ogg
Alarm_Buzzer.ogg
Alarm_Classic.ogg
Alarm_Rooster_02.ogg
Beep_Beep_Beep.ogg
Buzzer.ogg
Cesium.ogg
CyanAlarm.ogg
Replaced Notifications Folder With My Own
It Only Has
Altair.ogg
Antares.ogg
Cobalt.ogg
Cricket.ogg
CyanMessage.ogg
Doink.ogg
DontPanic.ogg
PixieDust.ogg
Plastic_Pipe.ogg
Proxima.ogg
Tweeters.ogg
Replaced Ringtones Folder With My Own
It Only Has
Boxbeat.ogg
BussaMove.ogg
Carina.ogg
Enter_the_Nexus.ogg
Girtab.ogg
No_Limits.ogg
Playa.ogg
Pyxis.ogg
Ring_Digital_02.ogg
UrsaMinor.ogg
Replaced UI Folder With My Own
It Only Has
Dock.ogg
LowBattery.ogg
Media_Volume.ogg
Undock.ogg
VideoRecord.ogg
VideoStop.ogg
VolumeIncremental.ogg
Removed From Addons
FaceUnlock Stuff
GenieWidget.Apk
GoogleFeedback.apk
QuickSearchBox.apk
Talk.apk
Talkback.apk
Okay, since someone else already grabbed above me, I gotta say this.
This boot animation (cbalt) is beyond atrocious. The idea is not to have as much **** fly over the screen as possible. The last image looks like a 10 year old + ms paint.
Look at slim ics' animation. That one does it's job, looks good and classy.
I know I'm coming off as a troll, but it needs to be said.
I look forward to the rest of the ROM. Thanks a lot. I do really appreciate it.
I think the separate thread was a good idea.
Cool!
I may check this ROM out.
You may want to create a zip file for those who want to add back on any of the removed stuff.
I woud not need this as I use Titanium Backup.:victory:
factory reset?
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
hakim7489 said:
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
Click to expand...
Click to collapse
Probably a wise idea since you are coming from a different JB ROM or an ICS ROM or GB.
I would imagine that subsequent flashes of this ROM would not require a factory reset or /system wipe once you are on this ROM.
hakim7489 said:
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
Click to expand...
Click to collapse
Wipe data and factory reset are one and the same. Next time you flash take a look in recovery.
dave71670 said:
Wipe data and factory reset are one and the same. Next time you flash take a look in recovery.
Click to expand...
Click to collapse
now that you mentioned it, it does looks familiar 'wipe data / factory reset' in cwm. initially i thought factory reset means formatting internal storage. i don't want that to happen.
networkdood said:
Probably a wise idea since you are coming from a different JB ROM or an ICS ROM or GB.
I would imagine that subsequent flashes of this ROM would not require a factory reset or /system wipe once you are on this ROM.
Click to expand...
Click to collapse
I personally recommend a wipe every update of this rom, just to help avoid issues, since dirty flashing is never ideal. Yes you can dirty flash, would I do it no, I wipe every time even if it is just a little change I did in the rom, I like to try and avoid issues as much as possible.
Full wipe it is - format /system, too?
Anyways, you need to update your sig/link:
I spend most my time in CWM flashing roms. Check Out My Port Of HellyBean Thats Slimmed Down, Pm Me And Tell Me Thanks If You Like Or What You Think I Should Change, If I Get Enough Requests For The Same Thing I Might Do It.http://forum.xda-developers.com/show...84&postcount=1
networkdood said:
Full wipe it is - format /system, too?
Anyways, you need to update your sig/link:
I spend most my time in CWM flashing roms. Check Out My Port Of HellyBean Thats Slimmed Down, Pm Me And Tell Me Thanks If You Like Or What You Think I Should Change, If I Get Enough Requests For The Same Thing I Might Do It.http://forum.xda-developers.com/show...84&postcount=1
Click to expand...
Click to collapse
Yes I would do that to. Why do I need to update my sig? That link works. I still spend most of my time in CWM Flashing roms (mostly my versions though) .
Sounds like you've got a great rom here. The change log is GREATLY appreciated. Could you fill me in on the difference between "my v13" and devil v13 please. Do the "nightly 8/1 changes" apply to only the devil edition or your v13 as well? Thank you!
Sent from my SGH-I897 using xda premium
nadaltennis77 said:
Sounds like you've got a great rom here. The change log is GREATLY appreciated. Could you fill me in on the difference between "my v13" and devil v13 please. Thank you!
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Most of the difference is the stuff that is removed from devils version in my version. There are some other differences, such as some build.prop changes, updater-script changes, gps changes and some other stuff. If you look at the first post it will show must of the stuff I removed.
PS I am working on CWM Flashable Zips to Restore All Apps I removed and then Individual Zips to restore just one app that you want or more than one. Also working on a flashable zip to restore media aka notifications, system sounds etc.
cbalt said:
Most of the difference is the stuff that is removed from devils version in my version. There are some other differences, such as some build.prop changes, updater-script changes, gps changes and some other stuff. If you look at the first post it will show must of the stuff I removed.
PS I am working on CWM Flashable Zips to Restore All Apps I removed and then Individual Zips to restore just one app that you want or more than one. Also working on a flashable zip to restore media aka notifications, system sounds etc.
Click to expand...
Click to collapse
So in the second post, where it says "nightly 1/08/12 changes," do those changes apply to your v13 rom in the first post?
Sent from my SGH-I897 using xda premium
nadaltennis77 said:
So in the second post, where it says "nightly 1/08/12 changes," do those changes apply to your v13 rom in the first post?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Yes they do, since his rom is my base that I improve more to my liking since I like a slimmer rom personally and dont use all the stuff I removed. He rom is an amazing rom and is perfect if you use all the stuff he includes.
quick question, if i am on Devil Edition V13 Aka 0801 Build, but want to try cbalt's V13 Release, does that require a wipe / factory reset? or could i just wipe cache and dalvik and flash?
pros - quick boot time, snappier than DerTeufel1980's V10 (rom which i was from), benchmarks show better scores than my previous rom (antutu, quadrant, linpack,nenamark,smartbench)
cons- not sure what you want to show in your bootanimation but i've seen better ones. changelog contains negativity. i don't know what happened between you and those 3 people but including rage in your rom does create some perceptions among users, at least me.
nonetheless, keep up the good work! with less anger perhaps
keredini said:
quick question, if i am on Devil Edition V13 Aka 0801 Build, but want to try cbalt's V13 Release, does that require a wipe / factory reset? or could i just wipe cache and dalvik and flash?
Click to expand...
Click to collapse
Full wipe.
hakim7489 said:
pros - quick boot time, snappier than DerTeufel1980's V10 (rom which i was from), benchmarks show better scores than my previous rom (antutu, quadrant, linpack,nenamark,smartbench)
cons- not sure what you want to show in your bootanimation but i've seen better ones. changelog contains negativity. i don't know what happened between you and those 3 people but including rage in your rom does create some perceptions among user, at least me.
nonetheless, keep up the good work! with less anger perhaps
Click to expand...
Click to collapse
Was my first animation, haven't had time to create another one and improve on that one. If you don't like what I put in the changelog and don't like the rom, then don't install it. Simple as that. I make the rom primarily for me and share it to be nice.
Btw im not angry.
Updated OP-Included Folder with all removed files.
Wasn't sure which thread to post in:
Running Der Teufel version and only issue I'm noticing is SDCard not being mounted after a reboot. Have had to go into Settings -> Storage -> select Mount SDCard each time. This also causes my default ringtone/notification to show as "Unknown" and has to be reset.
Anyone else having similar issues?
Like the title says, this is a work in progress and i'm releasing the zip for 4.2.1 for LaNightv9.x. I don't want anyone flashing previous LaNight flash this by mistake thus a new thread. This is a thread for android 4.2.1 only.
LaNight is a pure AOSP build, meaning it is NOT CM or built from CM source, so please do NOT ask for CM features. However, it does use device/hardware files from CM and rest from its own build.. so any device specific problems that is in CM may or may not be in LaNight. If you don't like "pure" AOSP, move on.
Features:
- Android 4.2.1 JellyBean
- Pawtip kernel for 4.2
- Build.prop tweaks
- init.d tweaks
- Galaxy Nexus Tweaked HW Acceleration
- New CM10.1 partition
- Speed and Cleanness of AOSP
- GPS Hack
- KC1 modem
- Stock Fonts
- And a lot more stuff!
What's working:
- Camera
- Logcat
- Sound
- Surface flinger
- Media Scanner
- Touch
- GPS
- Phone
- Internal Storage
- Tether
- Slight problem with Virtual Operators and roaming
- Bluetooth
- Everything
- Settings -> Storage FC
- Mount Ext SD to PC
- WiFi
- Data
- SMS
What's not working:
- Nothing i could find
Download:
- v9.2.1 Download is HERE
- v9.3 Download is HERE
- v9.4.1 Download is HERE
Others:
- Potential WiFi fix for people that don't have their WiFi working from HERE (DO NOT FLASH IF IT'S WORKING!)
- WiFi Fix from paw tip(I don't know what he did there to fix it in his ROM) http://goo.im/devs/pawitp/galaxysmtd_aosp42/fixes/20121125_wifi_fix.zip
- Clock font fix http://forum.xda-developers.com/showpost.php?p=34798184&postcount=55
Screen shots
- http://forum.xda-developers.com/showpost.php?p=34797716&postcount=54
Recommended flash procedure:
- Keep a copy of efs folder for security
- Reboot into recovery
- Make a nand backup before you proceed
- Wipe data/ factory reset
- mount and storage -> Wipe System/cache/data/datadata
- Wipe cache/cache partition
- Advanced -> Wipe dalvik cache
- Wipe voltage cache (If the option is given)
- devil -> run clean NStools options
- devil -> run clean init.d directory
- install rom zip from sdcard
- install rom zip once again if it boots you back in recovery (It's flashing kernel/recovery/partition if it finds an incompatible partition)
Required Set up:
- Settings > developer > background process limit > at most 2
- Settings > developer > Force 4x MSAA
Special thanks to:
Google
Whole CM10 Team
TeamHacksung
Pawtip (For first functional AOSP)
Derteufel (For the kernel and first AOSP rom)
Elitemovil(For the first 4.2 port)
Bigixie
Be18
Steeve76
HP40
iall5tar
mkalter (HW acceleration)
mikel.canovas & H3llstorm(For GPS hack)
Will try it out tomorrow. Thanks for all your hard work ace.
Sent from my SGH-I897 using Tapatalk 2
I will help.
Ace,
I can help a little. I will load this up and try a couple of modems, etc today but the majority of testing will have to wait until tomorrow. Let me know if that is too late. Thanks for the new toy.:victory:
Update:
Got it to boot easily with standard clears and wipes.
Had to revert back to Lanight 8.5 DD to load a GAPPS package and some modems on my SD card, USB doesn't work for me. It comes up and says "Connected as installer" which my PC doesn't recognize. So, I loaded several modems, a couple of GAPPS packages and reflashed. (BTW, if I select MTP in the USB select option, the PC sees the I897 but can't read the memory)
No advanced recovery options, have to power down and 3 button to recovery (Boo!)
KDH_Next_Gen_GAPPS kills the setup wizard.
gapps-jb-20121117-JOP40C-dmd151 loads OK with a couple of force closes, those can be worked through.
No modems install or are recognized.
Manual APNs do not save.
Lockscreen is a little skewed with the clock being partially obscured on wake.
Checking for storage from settings kills settings.apk
More later.. Thanks Ace, most fun I have had all day.
Play around with it that's why I posted here. Try new things and see if you can get it working. And share the findings here.
I will upload test2 today, hopefully the data,phone and storage issue is fixed.
I tried jl3, jk4 and kg3 modems, but none of them worked. This still is a great start. I see great potential with this one. I'll keep trying and reporting.
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Thanks for the tip Dave71670, I will play around more tomorrow but I tried to replace some of the files in the zip and my 7zip or WinRAR couldn't recognize the format of the zipped files. Really weird. I PM'ed Ace on it. I will try more hacking tricks later. I love this kind of stuff.
dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Downloading the latest CM10 now. I'll replace the .xml and report back.
Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
Test2 Changelog:
- Huge fix in build.prop
- Almost Everything ril/storage related in Framework has been hacked to work
- Added init.d fixes
- apns-config.xml has been edited
- Changed the modem
- vold.fstab hacked
- using the ril drivers from pawtip source code
- A lot more things has been changed that I don't remember
- Some drivers were edited to put on forced mode to work with the device
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!
AceofSpades90 said:
Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!
Click to expand...
Click to collapse
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.
dave71670 said:
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.
Click to expand...
Click to collapse
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test1 AND Test2 with updated mount points so I don't see the need for 1.9.2 in my build. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
EDIT: Are you saying the data and phone is working for you? If that is the case, can you share how you got it to work?
AceofSpades90 said:
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test2 with updated mount points so I don't see the need for 1.9.2 in test2. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
Click to expand...
Click to collapse
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. I am downloading your build now. Thanks Ace
dave71670 said:
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. Thanks Ace
Click to expand...
Click to collapse
Thanks for always helping me out lol. Can't appreciate enough.
AceofSpades90 said:
Thanks for always helping me out lol. Can't appreciate enough.
Click to expand...
Click to collapse
No problem. I am getting file for repo now. I will let you know how it goes.
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.
dave71670 said:
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.
Click to expand...
Click to collapse
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..
AceofSpades90 said:
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..
Click to expand...
Click to collapse
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.
dave71670 said:
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.
Click to expand...
Click to collapse
lol THANK YOU! I thought I wasn't bright enough for such an original and creative idea haha
Lost Root
Ace,
I lost root when I installed test2. Alot of other things are definitely fixed though. I will play around a bit and see if I can get root back and do some further testing. Great job again.
Looks like a good start, will try when there are less things that don't work. GL.
Devil 1.9.4 released for I9000, flash it and see if the storage issue is resolved.