218,000 Views!
If you have any problems, questions, suggestions, ideas(especially), [many other words that mean the same thing], shoot me a tweet @wesgarner or reply here
Wanted to give thanks to everyone helping on this ROM:
shagge68: Thanks for the support and encouragement on getting this ROM great =)
ninjabyte: Thanks for the server space, you were right drop.io sucks
Dwang: Great communication and help to try to work on the ROM, and the work you have put into everything. Your ROM created a great base for how fast these phones can run
Fnorder: Thanks for the couple things with ZipAlign, hope I can help with getting AUFS to work for Smart A2SD to include here
oknowton: Thanks for helping with ZipAlign back long ago ha
Garz: Thanks for all the info with theming and problems, I really need to help get the themes all working
brotbuexe/xillius200/PLZHelpMe/ID#: You guys are cool =)
Cyanogen: Thanks for your ROM of course (grr, just wish you were nicer about responding on Twitter - just playing)
Awesome people who have been helping during my absences: RavenII, gwydionwaters, Garz, BrutalHoe, FatBoyExtraordinaire (and more, but I suck at copying and pasting, seriously guys thanks a lot)
Beta Testers: Thanks for helping with all the oops in the ROM lol
Supporters: Thanks for supporting me in working on this ROM, and the great ideas you guys come up with
Twitter Followers: Wow too many to count, great and quick responses on everything!
日本人 Supporters: You guys made me laugh on Twitter lol
Donations: Skynet2Mainframe($30), outsider787($20), RevDave($20), Adrian($20), djn541($20), gwydionwaters($15), zeppelin481 ($15), aloxotls($15), Fausty($10), BrutalHoe($10), zsouthboy($10), jdhedden($10), ccriffman ($10), Jamdat33($8), Cheko ($5), carnegie0107($5), Delic($3) FatBoyExtraordinaire ($2.50)
Thanks guys - not going to use this for personal use. Done with my eBay shopping for the year lol
And yea these guys get special attention (well really because I can e-mail back and forth with them lol)
Click to expand...
Click to collapse
IMPORTANT: First Bootup will be slow - it runs DexOpt, A2SD, and ZipAlign
Click to expand...
Click to collapse
OK!
Run a Nandroid back up first (just in case)
Download, Install, RebootIf you are really wondering what has changed in this build, look at the kernel. Where my previous ones just use CM - this one is from scratch!
Now Active Issue Tracker: WG-Build and WG-Kernel Issues: http://code.google.com/p/wgbuild/issues/list
Build Y2-2.6: AndroidSPIN CFS with 10MB RAM Hack
CFS without RAM Hack (for 3D Gamers)
BFS with RAM Hack
BFS without RAM Hack
PS: FirstBoot will be incredibly slow because it wipes the Dalvik-Cache on FirstBoot.. sorry it was a necessary evil
Special Thanks to the best donation so far! Skynet2Mainframe gave $30 - Thank you so much
Incremental updates/changes
Stericson's Lockscreen
International GMaps
Advanced Launcher Replacement(Hero-Themed)
Application Fix instructions are below * Updated to latest CM Build
* WG-Kernel v2.0 (See below - this is the best of the best for kernels)
* Removed: Automatic Backing-Swap if that partition is detected
--- Personally, I do NOT recommend a swap partition - in my experience it only slows down the phone
* MultiTouch working in the new Browser app and Gallery
* Fixed All ROMs WiFi/RHack/etc...
* Updated to Market 1660 plus themed
* Updated to Contacts.apk v2.8
* Dalvik-Cache wiped on FirstBoot to give a fresh start with the framework
* Stericson's Lockscreen is now an incremental update (Yay!)
* Data Sync Bug Fixed - Forever!
* Reverted Build Prop to fix connection problems
* Changed WiFi Scan rate to 2min instead of 45sec to save battery
* No Longer Requires Danger SPL
* Exclusive Latest BFS Kernel =P
* Tons more things - can't keep up with..
Kernel Updates in Build Y-2.6:
WG-Kernel 2.0
CFS/BFS Options & RHack/NoRhack Options
* SLOB Memory Allocator http://en.wikipedia.org/wiki/SLOB
* Preemptible RCU
* Group CPU Scheduling for FIFO Deadline (CFS-Only)
* Deadline I/O Scheduler (FIFO=1 in init.d)
* Longer Default Panic Timeout in case of major temporary slowdown (helps prevent random reboot)
* 5 Ticks per CPU Check for CPU Speed versus other dev's default 1
* Latest SD Drivers from Cyanogen
WG-Kernel v1.0
* Swap-enabled (plus working CC)
* Deadline I/O Scheduler (FIFO=1)
* Setup Group Scheduler for Deadline (CFS-Only)
* Using Tree-based hierarchial RCU
* CPUFreq Setup (with 45% CPU upspeed threshold)
* Enabled Preemptible Kernel
* WLAN.ko is compiled with Kernel Modules
* USB Function has Ethernet Tether
* WiFi Tether Enabled
* No unneeded modules such as SquashFS, CramFS, HID-Dummy, etc etc etc
* IPV6 is included in kernel
* EXT3 runs on EXT4 Drivers, EXT2 runs on old drivers
* Disabled Kernel Debugging (for faster usage)
Archived ChangeLog
PS if you like my ROM, rate it well =)
Includes:
Multiple kernels to select from
SmartA2SD (keeps system dalvik-cache on data partition)
Automatic ZipAlign (from CM 4.2.8 instead of my old script)
Latest CompCache modules
---- (xvmalloc.ko(by me) and ramzswap.ko(by Dwang) compiled from source)
EDGE/3G Modified Build.prop for faster throughput speeds
Meltu's Audiomod: v2r2
Maps with Navigation(3.3.1) (International Capable version(3.3.1))
APN Android App: Turns data on/off
cytown's Phone.apk v21
Wysie's Eclair Contacts.apk v1.72
Fix_Permissions 2.03
ClearCache (my own script)
Work E-Mail
WiFi Tether
Market 1.66
SlideMe
Known Bug: Also, looks like people are having trouble with GApps
Package manager doesn't resetup permissions for the apps
For anyone having any trouble with GApps, Maps, FB etc..
Use this: http://www.androidspin.com/downloads.php?dir=wesgarner/ROM/&file=fixme-signed.zip
Run the update, let it boot
Once it finishes, don't do anything - just reboot
Once it reboots the second time, log into your Google account and you're good!
Click to expand...
Click to collapse
I'mma try this out to see how it is.
thanks buddy
is this still 1.6 or is this the 2.0 version of Android?
CrazyEye said:
is this still 1.6 or is this the 2.0 version of Android?
Click to expand...
Click to collapse
it uses CM 4.2.6 (so Donut with a touch of Eclair)
flashed...waited 5 minutes so far at T-mobile Screen....dang this is long...how long you say this will take?
CardinS2U said:
flashed...waited 5 minutes so far at T-mobile Screen....dang this is long...how long you say this will take?
Click to expand...
Click to collapse
an eternity! ZipAlign all happens during the TMo screen - took me around 15min (but completely worth it)
check the logcat, it will give you details on what's going on (you can see it never freezes or crashes)
(said in the next post, but wanted to explain why)+
Zip Align reduces the amount of RAM used during processing running for a major speed increase in dex-opt and running the apps, along with the RAM hack and a CC (or your userinit) boots speeds incredibly: http://developer.android.com/guide/developing/tools/zipalign.html
Most developers have not used this yet, but this does for the system apps provided from the now old Google Apps
CM does not ZipAlign his apps as most dev's don't - but this is a great advancement in speed and RAM usage
wesgarner said:
an eternity! ZipAlign all happens during the TMo screen - took me around 15min (but completely worth it)
check the logcat, it will give you details on what's going on (you can see it never freezes or crashes)
Click to expand...
Click to collapse
What is zipalign?
ZipAlign
rpesigan6 said:
What is zipalign?
Click to expand...
Click to collapse
Zip Align reduces the amount of RAM used during processing running for a major speed increase in dex-opt and running the apps, along with the RAM hack and a CC (or your userinit) boots speeds incredibly: http://developer.android.com/guide/developing/tools/zipalign.html
Most developers have not used this yet, but this does for the system apps provided from the now old Google Apps
CM does not ZipAlign his apps as most dev's don't - but this is a great advancement in speed and RAM usage
ran for close to half hour. Gave up. going back to CM 4.2.6
CardinS2U said:
ran for close to half hour. Gave up. going back to CM 4.2.6
Click to expand...
Click to collapse
you should wait - the first boot takes an eternity (sorry for that) - depending on the apps you run, ZipAlign will take a long process time
Boot will always be slow at first boot, then also slow when you install many apps
These enhancements prevent "out of RAM, removing background processes"
where did u place the zipalign script to zipalign all apks
dont wana dl the whole rom bad connection here
wesgarner said:
you should wait - the first boot takes an eternity (sorry for that) - depending on the apps you run, ZipAlign will take a long process time
Boot will always be slow at first boot, then also slow when you install many apps
These enhancements prevent "out of RAM, removing background processes"
Click to expand...
Click to collapse
took your word for it..wipped everything. wipped all apps. backed up mileage data then thats it..hahaha now restarting this..this time gonna let it run for an hour..hahaha lets hope it doesnt take that long......
woot..it made it
woah that took 5 minutes after a clean wipe..hahaha. Now at the android screen
thanks...
So u're saying every time I install new apps and shut down it will do that to the new apps installed?
kingklick said:
where did u place the zipalign script to zipalign all apks
dont wana dl the whole rom bad connection here
Click to expand...
Click to collapse
copy other peoples work now?
rpesigan6 said:
copy other peoples work now?
Click to expand...
Click to collapse
http://developer.android.com/guide/developing/tools/zipalign.html
I don't think so?
rpesigan6 said:
where did u place the zipalign script to zipalign all apks dont wana dl the whole rom bad connection here
Click to expand...
Click to collapse
copy other peoples work now?
Click to expand...
Click to collapse
Actually I was wondering the same thing; I'd rather run this via
ssh or adb and stick with my current rom.
Plus if it's a run-once thing it would be a good utillity for recovery.img
Fnorder said:
Actually I was wondering the same thing; I'd rather run this via
ssh or adb and stick with my current rom.
Plus if it's a run-once thing it would be a good utillity for recovery.img
Click to expand...
Click to collapse
I'm interested in this as well, if the only performance issues are increased boot up times, I'd like to try this on SenseHero if possible.
The script seems well coded and I'll probably use this rom as my next upgrade base. FYI, since system/etc/init.d/06zipalign checks all apks on bootup, you might want to use something besides md5sum. stat's printout of size:mtime should be enough, though cksum is faster too. On high load (like present on a bootup) md5sum took up to 8 seconds, cksum 5, and stat 0.3. This is for 66 apk's.
[[email protected]]~/za/system/app# (time /system/opt/bin/busybox stat -c '%s:%Y' /data/app/*.apk)2>&1|grep real
real 0m0.120s
[[email protected]]~/za/system/app# (time /system/opt/bin/busybox cksum /data/app/*.apk)2>&1|grep real
real 0m1.094s
[[email protected]]~/za/system/app# (time /system/opt/bin/busybox md5sum /data/app/*.apk)2>&1|grep real
real 0m2.599s
This looks promising, could be great for those slow ass hero roms lol
This looks very promising. Only issue I have with it is that all of my settings and whatnot were cleared. I had to relink my google account and although all the apps are there all my settings are gone
Abolfazl said:
This looks very promising. Only issue I have with it is that all of my settings and whatnot were cleared. I had to relink my google account and although all the apps are there all my settings are gone
Click to expand...
Click to collapse
You should use Backup for root next time it works for my setting and my desktop apps I have all over my screens.SOOOOOOOO has anyone flashed this rom yet?
Related
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
DEAD
I will try it today and let you know
thank you for the ROM
Sorry for slow download guys! When I finish my build, I upload to ge.tt which allows end users to instantly download while I upload. R3 is also broken -_- ; will upload fixed again
Please stick with r2 atm until r4 is done uploading.
Why the mandatory 96MB Swap and 512MB Ext4?
Wow...this rom is so horribly slow. Amazing how Roms can still get worse.
Slow UI, no improvements over 2.2.1, Market doesn't download anything. No Superuser installed. No busybox installed either. Commands such as a simple "cp" doesn't work.
Horrible.
Honestly with EzTerry's odex'd Asop and Richies F4T 182 de-odex asop build you are a long long long way off lads, nice effort but there is a lot better available already. And as for it being Danger SPL or custom mtd patch needed for what 90% of people are using 2708 with 14mb extra ram then this is a massive home goal.
Sorry just speaking the truth.
No, thats allright, I haven't applied much stuff to it yet.. I just uploaded it the day I compiled.
i'm impressed, just needs a little work. Also, those figures you have for free ram is with or without swap??
do you include a 2708 kernel? is that the default one? that could be a little clearer.
Sorry for the bugs, it is my first native phone rom.. Those figures are for free ram (physical) with the stock system without google apps with 2708 kernel. I did not include 2708 kernel yet but I will very soon! With the google apps and without the 2708 spl/radio, i got around 30 mb of free ram.
The mandatory ext4 partition and swap is for the R5 (uploading now) with a2sd but su still does not want to work. The "su" file was not included in the aosp compile for some reason and it messes everything up..
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
shadowch31 said:
I like the fact you have changed the OP now about it being fast or faster
Look forward to see where you go with this fella, maybe a look at EzTerry's Froyo Parts.apk if it can help you out. I ported it with Terry's permission to F4T 182 and may be a useful additional update for your rom in the future to add additional functionality.
Click to expand...
Click to collapse
Yeah sorry I overestimated
35 MB of free physical ram with market, pinyin IME, and google messaging running DangerSPL and stock radio, no 2708.
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
highlandsun said:
Well, I'm curious to see Froyo 2.2.2 on my G1 anyway. I have it on my TP2 and the major difference I noticed is that 2.2.1 doesn't have wifi tethering in its Wireless and Networking settings but 2.2.2 does. (Not really a big deal I suppose, since I already have a tethering app.)
I'm kinda curious about why Lazlo or the others haven't merged 2.2.2 yet.
Click to expand...
Click to collapse
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
shadowch31 said:
Simple answer - Go ask them
My guess is nothing more than a reduction in memory footprint??? And Wireless tethering is so easy using the google code website (just for those that don't know) http://code.google.com/p/android-wifi-tether/ last time I remember wireless tether included in a rom was back in Donut days.
Click to expand...
Click to collapse
link is broken, tried chrome and IE thinking it was the site...
Link works for me... Using Google Chrome
Updating rom soon (this week) with EVERYTHING fixed. No more lags and bugs..
jcarrz1 said:
link is broken, tried chrome and IE thinking it was the site...
Click to expand...
Click to collapse
Nothing wrong with the link, works fine. I suggest taking a closer look at your pc
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Ok, R5_Stable released. It is COMPLETELY STABLE with 97% bugs fixed. The UI is smooth and fast after all dalvik-cache has caught up on first boot. I have already messed with odexing and it works but will be in next release(s) because I still like my themes!
Note:
-DO NOT use QuickBoot application as it shuts down android incorrect (at least on this build), it works, but after you press "reboot" and android loads, up, android immediately crashes, and then reboots again and works fine..
-Now includes Live Wallpapers
-Launcher pro is default launcher
-seperate google apps for legal reasons (yeah again)
-On first boot, please wait until dalvik-cache has caught up (about 2 min) or until the phone has received radio signal for rom to run at full speed
-Pershoots .11 kernel added now
- 30+ MB of free physical ram with danger spl!! 60+ with 2708+ radio/spl/kernel.
-Requires Danger SPL now
- battery life is good but does not last 2 days
- setCPU recommended with ondemand at 122mhz-614mhz s (lower if you want to save battery but still runs fine @ 528mhz)
- usb tethering does not work unfortunately (the one built into rom)
jcarrz1 said:
i was using an adblocking hosts file. who the hell doesn't? especially on xda... LOL i guess some people like ads
Click to expand...
Click to collapse
Fella just because you use a host file please don't blame the links or assume no-one else is using them when links work for them. Not my fault you blindly use the host file and have no clue of how to configure it to allow certain things. The fault is the user because a computer works on a simply principle of it can only do what YOU tell it too.
smooth but on the mytouch wen using any other kernel it breaks wifi and the stock kernel doesnt support the new radio
Welcome To VegaComb BETA 1.7!
Apologies that this has been so long in the making, I haven't been sitting idly by, but real-life responsibilities mean that I don't have anywhere near the time to work on the Vega as I once did. BUT, we are ready for a BETA 1.7 release! So, without further ado, here is what I can remember of the changelog:
Rebel1's 3G patch is now built-in to this build by default.
The /data/tombstones folder will now be automatically cleared out every reboot, to try and avoid it devouring all of your available /data space. This is a stop-gap until I can fix the problem fully.
The default Browser has been edited to remove the Asus homepage and replace it with Google, also TabletRoms.com has been added as the first bookmark.
Default dictionaries have been added to the default keyboard by popular demand! Languages are: En, De, Cs, Es, Fr, It and Nl. You will have to enable dictionary suggestions in the Keyboard settings to see these.
Default system wallpaper has been changed from the boring blue stock Honeycomb one to a much nicer abstract wallpaper.
A whole multitude of wallpapers have been added to the built-in Wallpaper-Picker, this is a mix of the nicest wallpapers I could find from the Acer Iconia, the Asus Transformer, the Motorola Xoom and some custom ones from around the net!
The Youtube app has been re-hacked to dramatically increase the quality of videos. The HQ option now works correctly to switch between high and low quality, and (while not 720p) the higher setting is VERY crisp and clear compared to before.
FLASH! Ahhhhahahahhh (think Queen). download the OFFICIAL flash player from the market (10.3 currently), download Opera Mobile from the market, watch flash. Simples. Green bar glitching, ghosting and other flash strangeness should now have been all fixed. Flash video can still be a little jerky as it is being rendered in software, overclock to get around this if you feel you have to (but it does work well at the default speed!)! BIG thanks to brucelee666 for this, when my transfer cable broke, he picked up and did a ton of testing to get this working!
Brand new (extra shiny) boot animation has been added. HUGE thanks to ThinkDevoid from the TabletROMs team for creating this for me!
The required default /system partition size for all future VegaComb releases is 155mb, we now have much more room to play with which removed a HUGE limitation that was actively holding me back!
More? Who knows, my memory is crappy
Before you update using either the 1.6-1.7 upgrade patch, or install 1.7 from scratch, you MUST be running my new ModdedStock base as this increases the /system partition size to make VegaComb BETA 1.7 fit. IF YOU DO NOT DO THIS THE INSTALL WILL NOT WORK CORRECTLY AND YOU WILL SOFTBRICK YOUR VEGA! Please fully read the ModdedStock thread to make sure you understand how this works!
I have been working HEAVILY in conjunction with MrGuy of TabletROMs now for a while, and especially on BETA 1.7 (Thank him for many things including the awesome YouTube app hack). Together we have now not only updated VegaComb, but now AdamComb as well for the NotionInk Adam. Vega owners owe a lot to MrGuy, so show him your love people!
Update notes from previous versions:
Code:
[I]Previous Notes:[/I]
[B]Changes in BETA1.6:[/B]
Spare Parts settings fixed - Setting power button to "Home, then sleep" now works correctly.
Bluetooth should now correctly turn on and pair "out of the box" without tweaking.
DPI settings have been changed. The default DPI is still 120, but you can now manually set this to 160 if you wish, unfortunately though the Google Apps will not function correctly at this density (although most other apps should now be fine).
Youtube app has been hacked (thanks to MrGuy for wokring with me for this!) to disable HQ playback by default on all videos. This should now mean that you can play all YouTube vids through the app. The HQ button is still there, but if you select it, the video will not play.
Default CPU speed set to 1.2ghz instead of 1ghz as there appears to be some strange speed issues when defaulted to 1ghz.
Fixed an issue where you needed root to read contents of NTFS drives.
Added OpenVPN support (thanks to Scanno!)
Hopefully fixed any lingering 3G issues (thanks to rebel1!)
Possible fix to GPS issues but this cannot be tested by me (unfortunately!).
Added a seperate download for an EXPERIMENTAL FlashPlayer hack. This hack unfortunately does not fix flash video playback on most sites (YouTube and BBC iPlayer do not work for example, but the small videos on the Yahoo news website do). What this hack DOES fix, is most other Flash applications, such as web games etc. Using this patched version of Flash, Kongregate Arcade should work correctly, as well as other apps such as Zoodles Kid Mode that use flash within the application to play games. Please use this at your own risk and report the results! Trying to play flash video using this patched version WILL crash your browser, you have been warned ;)
Added an animated VegaComb boot screen.
Possible speed increases due to various changes to the init + memory management tweaks.[B]EDIT: Apparently, this has caused a much more significant speed increase than was expected, 1.6 has been reported to be VERY fast! :)[/B]
[B]VegaComb BETA 1.5.2 Patch![/B]
Small patch to apply over the top of 1.5.1 (ONLY to be used on 1.5.1) which fixes Root (for people who upgraded) and App2SD for everyone. Link at the bottom of the thread!
[B]VegaComb BETA 1.5.1 Patch![/B]
This patch simply fixes a small issue with Wifi in 1.5, you can use the 1.4to1.5.1 patch to either upgrade from 1.4 to 1.5.1, or to patch 1.5 to 1.5.1 if you had already flashed it and have the issue :) Apologies for the bug!
[B]Welcome to VegaComb BETA 1.5![/B]
Hello all! We are back, as promised! The release cycle is slowing down a little now as expected, but we still have some damn juicy treats for you in the BETA 1.5 package :) So, without mucking about, here is what's changed since 1.4:
Speed... I spoke about this a little in the [URL="http://www.youtube.com/watch?v=VMqeqcRh5pM"]development update I put on youtube[/URL], but just to clarify here... We were not happy with the overall speed of the ROM in BETA 1.4. While repairing the stability issues in 1.3, we went a little overboard with "safe" settings, making 1.4 rock solid, but noticeably slower than previous releases. We didn't want to reach a "happy medium" with part-speed and part stability... and so, there has been a full review of all the memory settings, testing dozens of combinations until we reached a setup that offers both impressive speed (at least the speed of 1.3 IMO) without (hopefully!) any of the reliability drawbacks. And so, our hope is that 1.5 will be both the fastest, AND most stable release so far!
Bluetooth should now be fully working, searching and pairing has been tested with several devices, so pair away!
The Screenshot option in the Display section of Settings was causing Force Closes, this is now fixed, so you can take screenshots of your VegaComb tablet in action :)
The 3G APN (and related) settings should now be correctly visible in the settings menu, for those of you with 3G cards.
Issue which was causing the Launcher to sometimes Force Close on boot should now be fixed.
Problem with the media scanner not correctly locating music on the MicroSD card is now resolved.
Overclock increased back to a maximum of 1.5ghz.
Xpad support should now be available again (to connect Xbox pads over USB).
The Dreaded blue light of DOOM under the camera has been banished to the fourth dimension of hell.
Force Close problem when downloading from the stock browser or Gmail/Email apps should now be fixed.
Force close that was sometimes plaguing the recent apps menu should now be fixed.
Google maps framework has been added. this was previously causing certain apps (such as Tweetdeck) to immediately force close when you logged in. These apps should now be working correctly.
We have had a whip-around and provided the Honeycombs on the boot screen with an extra face each (PHEW! Pedants, move along, nothing to see here :P)
Shutdown menu has now been put in place (thanks to the AMAZING work of HomerSp), it is not the ordinary power menu, but a lovely custom one that provides you with the options for: Home, Shut Down, Reboot and Reboot to Recovery!
Because of the new shutdown menu, the recovery reboot app has now been removed (not needed!).
Added working screen calibration app. This will help with most issues (like home/back buttons) but does not fix the top-of-screen sensitivity issue as of yet I'm afraid!
App drawer has been edited to remove the bottom row of icons, so you can now better access the screen previews below them when placing a shortcut :)
Again, there may be other stuff that was fixed and forgotten :P Let us know if you find anything!
[B][I]I also want to make an important note for those who are confused... I am NOT working on this ROM alone, this has been a group effort from the start. Originally worked on by myself and Corvus (with help from the guys here at TabletROMS. Since then we hooked up with HomerSp (LEGEND!) who does magic things with Android that I really don't understand (some say he's a clone grown at google), and the project has moved in leaps and bounds. Unfortunately, Corvus has recently been forced to back out of this project due to time limitations in his real life, with work and family, so now it is primarily myself and Homer who work on VegaComb. I hope this clears things up, credit where credit is due![/I][/B]
[b]Welcome to VegaComb BETA 1.4 - Codename: Arnold Veganator (Hasta La Vista Processes)![/b]
As promised! BETA 1.3 was more of a features update, trying to get the ROM more in-line with where we would like it giong forwards, cleaning up files, opimizing and getting as much as possible working. We realized at that time that tehre were memory issues with the build, but we are trying to take a modulated approach to developing this ROM, so one step at a time :)
1.4 is primarily a performance release. You won't see any HUGE new features here (other than Huawei 3g support, thanks to rebel1!) but a lot has gone on in the background to try and make this ROM useable as your daily OS. Memory values have been tweaked, the kernel has been re-compiled with HoneyComb specifically in mind and (hopefully!) all of the freezes and hard lockups present in 1.3 have now been eradicated.
[b]Changes in BETA 1.4[/b]:
Kernel has been recompiled from scratch (thanks to @HomerSp!) gearing it for HoneyComb. [I]Some features such as xpad support are not yet present in this kernel, they will be added back in soon, but there shouldn't be much other than that.[/I]
Kernel bug that was preventing lowmemorykiller from working effectively has been fixed in this build.
Memory tweaks made in init to values better suited to both the Vega and to Honeycomb.
CPU clocking now defaults to 1ghz instead of 1.5, the top-end has been lowered down to 1.4 for now (this will be put back to 1.5 hopefully in the next release). Install SetCPU (from XDA) or download CPU Master from the market (free) to overclock if you want.
Support for Huawei 3G dongles added (HUGE thanks to rebel1 for this patch!) - this has NOT been tested as of yet, as I don't own a 3g dongle! :P
EGL patch tweaked slightly taking a new approach, hopefully making this simpler to manage in the future.
The issue where the battery indicator was not updating correctly MAY be fixed in this build (not 100% confirmed yet)
Replaced an icon I missed when the BACK button is pressed (oops!)
Adjusted a couple of apps to save some space in /system.
[I]Please make sure you ask for help and post bugs in the threads provided, I am getting WAY too many PM's to answer them all (sorry, don't take it personally!).[/I]
[B]Changes in BETA 1.3[/B]
Switched to Transformer Frameworks - Better fit for our hardware and to stay in line with what the Adam guys are doing.
New frameworks are more streamlined, should make the UI feel snappier overall.
Framework edited which should allow all web related apps to render correctly (not flash)!
[i]This means that you can now use browsers you download from the market like Miren and Dolphin, and news readers such as Pulse will now work.[/i]
Wifi issue that caused you to need to reboot after the first flash before Wifi would turn on is now fixed. You can connect straight away after flashing the ROM!
Corporate email setup added to Accounts & sync (all security settings work correctly, but remote wipe does not factory restet the device as of yet, but is does disconnect the emails).
Screenshot function added (select in Settings > Display). You can take screenshots by long-press of the Recent Apps softkey.
The Calendar app is back from Vacation and ready to organize your life.
The Books app has gotten over it's shyness and now shouldn't dissapear shortly after boot. This is still slightly strange so it might go walkies if you don't pin it down :/
Working Recovery Reboot app added, this one works so you no longer need gscript to reboot to recovery! (thanks to Paul O'Brien for this app!)
VegaComb Beta simple boot logo added.
REALLY annoying black fade on the right-side when using the notifications popup has been removed as it refused to display correctly.
MicroSD card now correctly displays as what it is, instead of showing as Internal USB storage.
Moving apps to the MicroSD should now work correctly, and apps launch fine, even if you have USB debugging turned on.
USB external storage now shows correctly, and gives a notification when it is plugged in (you can click on the notification to browse files or dismount the USB storage).
Can now correctly mount FAT, EXT and NTFS USB storage and browse through the file browser.
When you connect the Vega to the PC with your USB cable, you now get a notification allowing you to mount your SD card over the USB to share your files!
Doubled the ammount of memory that was available to apps in order to try and combat some of the freeze-up issues (MAKE SURE YOU WIPE DALVIK CACHE WHEN YOU INSTALL THIS BETA!)
Other stuff I've forgotten again :/
[B]Welcome to VegaComb BETA1a[/B]...
1a release is a very small patch to the installer script to make sure everything is installed correctly!
[B]What's new in BETA1?[/B]
This is a HUGELY new build, and has required a ton of testing, so please bear this in mind :P
Files have been streamlined and some slowdown bugs should have been fixed, you should see a nice little speed increase in this build.
SuperUser is FINALLY fixed! [B]No... I really mean it this time :P[/B]
WiFi has been patched. You will still have to reboot as it will lock the first time you try to turn it on, but after that it should be much more stable than before, and shouldn't require you to toggle WiFi on/off all the damn time.
The Dolby Audio section in the Settings menu was causing Force Close errors, so this has now been removed from the menu completely.
Web browser has been hacked to prevent you having to disable EGL rendering in order for it to work.
Gmail and Email apps have been FIXED. You can now read your emails in both apps, they should be working perfectly as far as I have tested.
Bluetooth libs and binaries have been added. Bluetooth now turns on without any errors, but I cannot yet confirm if it actually works. If someone tests this, please let me know!
WiFi has been patched to connect correctly to ad-hoc networks. So you can now tether your Vega to a phone such as the HTC Hero.
The whole image has been SHRUNK (massively) to fit into the Vega's default partition size. It's a hell of a squeeze, and some apps have had to be pushed to /data to make it fit. All of these are apps that can be re-downloaded from the market like maps etc) other than two, the Android keyboard (it's a huge file :P) and the Android Music app. If you prefer to use a different keyboard, you can remove this one, but if you wipe /data, you will have NO keyboard installed, and the world might implode :P
This is now a ClockworkMod image, designed to be used on the Vega's default partition tables, so DO NOT flash this over the top of ALPHA4. Re-flash 1.09 (or some other standard image) before installing this through CWM. You now have a healthy 293mb to play with in /data, so you can download stuff off the market without worrying like in ALPHA4 :)
OK, LOTS more stuff has changed, but I can't remember a lot of it, I'm sure it will come back to me, but my brain is a little fried right now and I need a beer :P
[B]Updates from ALPHA4:[/B]
Gapps WORKING! (Huge effort on IRC, big thanks to MrGuy!)
NTFS usb drives should now be detected in host mode (not tested)
Moved some apps to /data and shrunk the /system partition to 260mb to give you some more space now that the market works!
3D Photo Browser, Books, Maps, Youtube, Google Talk and Music Apps moved to /data (you can uninstall them from there to save space, if you wipe data/factory reset you will lose them!)
Browser patched to turn off EGL rendering by default, so no more need to use about:debug anymore.
SuperUser fixed!! (Hopefully properly this time! :P) [B](ONLY JOKING I BROKE IT AGAIN! :P)[/B]
Other stuff I've forgotten :P
[B]Updates fromAlpha3:[/B]
SD Card is now detected
Audio fixed (HomerSp, legend :) )
WiFi Fixed (Guess who? :P ) (This is still buggy, the first time you turn it on, it will not work. Reboot, then try again. Sometimes need to toggle on/off to get it running)
G-Sensor fixed (yup, you can rotate happily now!)
Bottom-Bar Home button fixed.
Lock screen added.
Hardware buttons now work, power to sleep/wakeup etc.
Added Spare Parts, you can set power to home/sleep.
Root and Superuser added (you should be able to use CPU tools to overclock now). [B][I](WHOOPS I BROKE THIS! SEE BELOW ON HOW TO FIX!)[/I][/B]
Bunch of changes in build.prop
More updated libs and binaries than you can shake a llama at.
[B]Initial Features from Alpha1:[/B]
It boots!
Hardware Acceleration!
Widgets.
Most (not tested) android apps should run.
What doesn't work (updated as of 1.7):
Camera Still FC.
Flash player doesn't work in apps or in the default browser (Opera Mobile only!)
Battery indicator doesn't always update correctly (wipe battery stats tog et around this).
Audio has been reported as "Tinny" - we are looking in to this.
Factory reset (and remote exchange wiping) not working.
Cannot connect to PEAP Wifi networks.
We will keep working on this!
CREDITS!
Myself and Corvus have put a whole ton of work in to this, but there are others who deserve praise for all of their work:
HomerSp, for his brilliant work on fixing the Hardware acceleration, sound, wifi, the world, curing cancer and generally being awesome!
The guys working on the NotionInk Adam port here at TabletROMs - They have helped us a LOT both with their original port to use as a base, and a wealth of help they have given us on IRC to get this working, our original port was based on files from the SDK, Xoom and Transformer, we are now completely basing our work on their amazing ROM (which is based on the Transformer and Iconia) Thanks guys!.
MrGuy has worked with me extensively on version 1.7 (and with lots of parts before!), so HUGE thanks to him!
Lenny from VillainROM. Lenny has pretty much tested and approved EVERY build of VC to date, given opinions and hilighted bugs. Thanks a lot man!
THE DOWNLOAD COMES IN 2 FLAVOURS! A full ROM for flashing from scratch, or if you are already running 1.6, there is a handy-dandy 1.6-1.7 update patch! download the right one for you!
YOU MUST BE RUNNING THE MODDEDSTOCK BASE FOR VegaComb BETA 1.7 AND ABOVE TO FIT ON YOUR VEGA CORRECTLY! YOU HAVE BEEN WARNED!
FULL INSTALL DOWNLOAD:
DOWNLOAD VegaComb BETA 1.7 NOW!
1.6 to 1.7 PATCH DOWNLOAD:
This can be applied directly over any 1.6 version
Download FIXED BETA 1.6 to 1.7 Patch here!
newbe5
EDIT BY ADMIN:: To receive honeycomb updates, please join us on twitter |here|
cool intersting times ahead! good luck on port, hopefully 3.0 sourcecode out sometime soon
In the title it says xoom(ish) port but it looks more like a transformer port in the video? Either way Honeycoooooomb! Good luck guys
Good luck and keep up the good job!
It is a mix of all 3. SDK, Transformer and Xoom. I took a few libs from the Xoom, as well as a ton of stuff from the Adam Transformer port and the SDK files factored in too. It's kind of a Frankenstein-monster effect going on Changed the title to reflect this!
Cool, great work. Am pretty certain the source will actually be released soon. Googles i/o is on tuesday and am sure this is when they are gunner announce or hopefully release the source for honeycomb, or possibly icecream, which will be a mashup of gingerbread and honeycomb am sure.
So hopefully that will help getting honeycomb onto the vega
Well done guys, keep the good work going.
mintvilla said:
Cool, great work. Am pretty certain the source will actually be released soon. Googles i/o is on tuesday and am sure this is when they are gunner announce or hopefully release the source for honeycomb, or possibly icecream, which will be a mashup of gingerbread and honeycomb am sure.
So hopefully that will help getting honeycomb onto the vega
Click to expand...
Click to collapse
Yeah i expect we will c this aswell
good work with the port too
[honeycomb][cross pollination][adam]
FRESH TODAY 9th May 2011 11:30AM EDT
Cross collaboration between devs of sister tablets in the ##adamroot freenode IRC channel this morning!
Devs: HomerSp got hardware acceleration working, newbe5 got it working on the Advent Vega (video demo below) and DJ_Steve applied them to the Adam HC rom and confirmed to now be working smoothly!
9th May 2011 12:05 EDT
DJ_Steve showsoff hardware acceleration implementation on Notioink Adam.
I encourage guys, let's take the VEGA to infinity and beyond
your second video looks pretty smooth any reason why a dev only download isnt appropriate ? not pushing this is amaing work you must have great patience just intrigued
Curious to know how much space is left for app install after Honeycomb is put on the vega???
bob1369 said:
your second video looks pretty smooth any reason why a dev only download isnt appropriate ? not pushing this is amaing work you must have great patience just intrigued
Click to expand...
Click to collapse
you can try now
http://tabletroms.com/forums/showthread.php?453-ROM-VegaComb-by-newbe5-and-Corvus
I'm staggered at how smooth H/C is from the video!
I did try but i had a falling out with nvflash so i'll look forward to a update.zip I can use, I assume when wifi is working!
I did spy from the video there didn't seem to be any gApps, I assume this will be added unless there is a seperately gApps download for H/C?
google i/o 20011
hopefully honeycomb sourcecode released at todays event at 5 oc'lock london time, who nows we might even get an update from advent or pov.
fingers crossed
serialkillazzs said:
hopefully honeycomb sourcecode released at todays event at 5 oc'lock london time, who nows we might even get an update from advent or pov.
fingers crossed
Click to expand...
Click to collapse
i'd be surprised tbh!
I was under the impression from Advent we would be getting 2.3 and the source code has been out for quite some time and still nothing. yet you can get a CM nightly which is 2.3.4.
Unless they've had access to the H/C as a vendor and been working on that but some how i doubt it :S
Wow, a mention on the front page!
Congrats on this, guys!
Wow. Does this mean hardware acceleration may make its way into other Android devices? I hope so!
chrisjasper said:
Curious to know how much space is left for app install after Honeycomb is put on the vega???
Click to expand...
Click to collapse
after trying it an hour a go it's 130mb
bewA said:
after trying it an hour a go it's 130mb
Click to expand...
Click to collapse
Thanks, apps2sd looks like a necessity then, assuming there isnt too much that can be stripped out
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the ZTE Blade, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-Blade
Download: link
Mirror: link
MD5sum: 580c9db7463a1d737f9890e4ea488ccf
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
I didn't see the market after i flash, any solution to get the market?
andy8274 said:
I didn't see the market after i flash, any solution to get the market?
Click to expand...
Click to collapse
Dear Andy8274,
Usually people say "hello", "please", "thanks", and at least start reading the entire post, even sometime use the research tool, before asking this kind of question.
Best regards,
Tuc
maybe You have to install gapps? I don't know :/
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)
uosiumen said:
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)
Click to expand...
Click to collapse
I had the same issue in the GSF b27 while trying your method. and finally managed to make A2SD working perfectly using the following commands in the terminal emulator:
Code:
su
a2sd reinstall
a2sd datasd
I don't know if it can help...
Tuc
Tugdu77 said:
I had the same issue in the GSF b27 while trying your method. and finally managed to make A2SD working perfectly using the following commands in the terminal emulator:
Code:
su
a2sd reinstall
a2sd datasd
I don't know if it can help...
Tuc
Click to expand...
Click to collapse
So, you've installed dark tremor A2sd? Out it was built-in your system?
Sent from my ZTE-BLADE using XDA App
Clean install, all was going well and now.
Then tried to make a call, died had to pull the battery out.
In addition i can't make calls or connect to the internet, setting are all ok
uosiumen said:
So, you've installed dark tremor A2sd? Out it was built-in your system?
Click to expand...
Click to collapse
I'm still using GSF b27: A2SD was already built-in, just needed to be activated. So once you installed A2SD, try to activate it with my previously described method.
It also found an app that could help: http://forum.xda-developers.com/showthread.php?t=917377
Tuc
uosiumen said:
maybe You have to install gapps? I don't know :/
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)
Click to expand...
Click to collapse
Use S2E app from the market it working OK with CM7.
I can confirm:
CM7.1 + S2E (market) = victoria
--
simono_pl: dzięki
GAMES work great
Hiya,
Just wanted to say that this ROM is the best for 3D (for me anyway). Been using GSF for a few months now and I gave up on angry birds (sluggy) and others.... Just put CM 7.1.0 and Angry birds workds like a dream
General UI (scrolling and oppening apps) it is slower than GSF (dunno why, maybe the theme?) But performance wise (once the stuff has been opened) it seems to run faster and thats what I want. Any chance of having a less heavy theme available?
WIFI - Works
CALLS - WORK
LATITUDE - works (even checks in automatically, never managed that on GSF)
GAMES - WORKS LIKE A DREAM
BLUETOOTH A2D - Works perfectly. Playing music with (andless, I love that prog, so easy UI and folder view ...)
So, basically, All good work guys I just wish for a less heavy UI
Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk
ironman159 said:
Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
install ClockworkMod 3 and Bobs your uncle
Btw. Played a bit more with interface options (quite a few ...) and managed to get a performance quite similar to the GSF one so quite happy now
all seems to work for me
What settings have you guys changed for better performance?
obsydian said:
Clean install, all was going well and now.
Then tried to make a call, died had to pull the battery out...
Click to expand...
Click to collapse
+1
Solution?
Edit: going in the zte entry of the application menu and calibrating the proximity sensor fix this
ironman159 said:
Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
You want to use the Gen1 to Gen2 tpt upgrade - http://forum.xda-developers.com/showthread.php?t=1258855
hmmmm 7.1.0 is nice in performance as now more heap size .more overclocking level i can reach upto 787 stable
but it has a really slowww interface
games work well without glitches .
but many hd gameloft latest games are unplayable i know it is bcoz of hardware .but sometimes software can enhance hardware performance as do overclocking
in next mod if possible cyanogen can increase gaming performance
applicationz said:
hmmmm 7.1.0 is nice in performance as now more heap size .more overclocking level i can reach upto 787 stable
but it has a really slowww interface
games work well without glitches .
but many hd gameloft latest games are unplayable i know it is bcoz of hardware .but sometimes software can enhance hardware performance as do overclocking
in next mod if possible cyanogen can increase gaming performance
Click to expand...
Click to collapse
There is only so much that can be done with a 600mhz armv6 phone. Most of those gameloft hd games were designed for armv7 phones at around 1ghz, the blade is half that speed.
The interface can be sped up by turning on 16 bit transparency in cyanogenmod performance settings, that allows it to use more hardware acceleration for drawing the interface. It causes a few minor graphics glitches though. You can also replace the launcher, remove the theme chooser & do a few other things to speed it up.
wbaw said:
There is only so much that can be done with a 600mhz armv6 phone. Most of those gameloft hd games were designed for armv7 phones at around 1ghz, the blade is half that speed.
The interface can be sped up by turning on 16 bit transparency in cyanogenmod performance settings, that allows it to use more hardware acceleration for drawing the interface. It causes a few minor graphics glitches though. You can also replace the launcher, remove the theme chooser & do a few other things to speed it up.
Click to expand...
Click to collapse
see now gameloft games are designed for 1 ghz processor as you are saying
so basically without overclocking it should work on 1 ghz processor with switched off graphics or without any graphical setting
now in this mod we have got 810 mhz we can provide more vm maybe we could reach 900mhz in next kernel .we could enable graphics using blade buddy and we have 512mb ram which can handle heavier processes .we could reduce those 100mhz gap in running game using graphics ,,ram and other system properties
applicationz said:
see now gameloft games are designed for 1 ghz processor as you are saying
so basically without overclocking it should work on 1 ghz processor with switched off graphics or without any graphical setting
now in this mod we have got 810 mhz we can provide more vm maybe we could reach 900mhz in next kernel .we could enable graphics using blade buddy and we have 512mb ram which can handle heavier processes .we could reduce those 100mhz gap in running game using graphics ,,ram and other system properties
Click to expand...
Click to collapse
It's not just the mhz, armv7 processors are more efficient, faster at the same speed & provide more features. Some Gameloft games will run, but you shouldn't expect them all to run, or run well, they were designed for higher end phones.
A11 & A11 - use v16
A13 - use v16
Hey Coral / Flame Gang!
First off, I'm glad to be here. I just came from Pixel 2 XL after my phone died from hardware issues and I needed to upgrade!
Anyway, here's a script that I put together for my own use, but still develop occasionally; tuned especially for our Coral / Flame devices.
Enjoy!
The Back-Story:
I helped some good guys out with developing the awesome Franco.Kernel tuning parameters "back in the day" (Franco's Dev Team - you can look us up, the great osm0sis still hosts the original file set - but they won't even run on Android Pie or later). What is still applicable to Android 12 is in this file; trimmed and consolidated into a single script, along with some other goodies I've come across since.
Philosophy:
- I don't write untested BS or questionable crap in my scripts. If a given tweak doesn't show an objective improvement in benchmarks or battery life or a subjective improvement in performance that can be turned on or off by running or not running the script in a blind test - it doesn't get added.
- If I do not believe a given tweak is safe to run on everyone's daily driver device, I also won't include it my script, regardless of the benefit.
- This script is biased toward increasing performance - but it takes advantage of battery saving opportunities that don't affect performance.
Notes:
- This script is lean and mean, but it's not rocket science.
- I didn't invent anything here. Feel free to use it (or not), distribute, alter, whatever; to your satisfaction, giving credit for redistribution only to "Franco's Dev Team", and maybe me if you're feeling generous.
- I have verified it works well on my personal Pixel 4 XL, and is compatible with all Android versions, Kernels, and Magisk versions applicable to the device.
- It won't make your phone run any worse, and it should make it feel a bit "snappier", but YMMV.
- Most benchmark scores improve marginally (1% - 4%) on my device with stock or EX kernel. Again, YMMV.
- I do not plan to do heavy maintenance on this, but I will keep it up to date so it at least safely runs on the Pixel 4 / 4 XL as long as I own one. I will post updates with a minimal change log (it's a script, you can read it!). If I stumble across something that helps the community, I'll share it!
Disclaimer:
I can't see how this could possibly cause irreparable harm to any Android device on which it is run.
However, I suppose untested configurations may (rarely) have slow-downs, reboots, or other effects.
REGARDLESS, it is offered as-is with no warranty, and you choose to run this at your own risk.
If you do encounter issues, let me know and stop using the script. I may ask you for further help with debugging.
Requirements:
Root
BusyBox installation (I recommend the Magisk module by osm0sis)
Knowledge of how to execute a linux script and/or where to place it and allow permissions to run on boot
Usage:
Download the linked file to your device
Copy it to /data/adb/service.d
Ensure permissions are correct (0755)
Reboot and wait a three minutes
NOTE: The script will generate a text file called "pksp4_script_result" in the base of your "external storage" directory (/storage/emulated/0). This file will state either "Success!" or "Failure..." indicating if the script completed at the last execution attempt (it will over-write each time the script is run - check the date/time stamp on the file properties) .
Credits:
Franco's Dev Team, esp. osm0sis
Others as noted in the script file header
94pksp4v16.sh
Shared with Dropbox
www.dropbox.com
94pksp4v17.sh
Shared with Dropbox
www.dropbox.com
Change Log
V17 (use for A13)
- Audited script against A13 to ensure compatibility
- Script timing edits to support successful execution on A13 with Magisk 24 (especially ZRAM)
V16 (use for A11 and A12):
Fixed V15!
- Delayed and slowed ZRAM change to enhance the reliability of it "taking" on each boot
- Made Adrenoboost and power-efficient work queues contingent on those modules actually existing in the user's kernel
- (Did the same with the wakelock blocker while I was at it)
- Fixed a script typo that was the likely root-cause of V15 not running to completion or outputting "failure" for some users.
V15:
Enabled power-efficient work queues by default (most kernels have this functionality built in)
Enabled GPU Adrenoboost module by default, set to low boost (many kernels have this available, on/low seems preferred for a slight / smooth gaming boost without battery life detriment)
Changed vm.vfs_cache_pressure to 50 (was 200, wrong-direction from 100, I now believe after more testing)
Changed vm.dirty_ratio to 10 (from 20; avoids latency when having to write-out data to disk asynchronously by halving the amount of data needing to be written; this could reduce occasional "hang-up's" you may have experienced on this device regardless of kernel or mod - including stock!)
V14:
Increased ZRAM capacity by 50% to 3 GB
Turned off TCP timestamps to reduce overhead
Adjusted VM settings for having more memory
Added a couple minor VM tweaks
Added a minor kernel scheduler tweak
Minor code clean-up and re-ordering
V12:
Small core schedutil up/down rate limit tweaks, making small cores more responsive to increasing frequency and maintaining higher frequencies a bit longer. This should keep more load on small cores / reduce offloading to big cores unless big core utilization is truly necessary. I noted a little less latency and a little better battery life in my testing.
V11:
REMOVED.
V10:
Welcome to 2021.
Minor update - now bbr2>bbr>westwood (depends on what your kernel offers) for TCP congestion control algorithm. As an aside, I reconfirmed txquelen of 512 is still optimal for modern wifi and lte networks.
V9:
Happy holidays!
Added some TCP and kernel cfs tweaks that reduce device latency.
V8:
Stable, slightly improved Android 11 release.
Minor CFQ tunable tweaks that very slightly improved IO in benchmark testing.
Now blocks a single wakelock: qcom_rx_wakelock (if your personal philosophy is to never block any wakelocks, feel free to comment that line out in the script).
Changed TCP congestion avoidance algorithm to BBR2 (if available in kernel) - else, Westwood; based on network speed testing (BBR2 > Westwood > BBR).
V7:
Removed mount tweaks - they no longer do anything useful
Increased DBR slightly
Modified write-out file to not list time/date (for some reason it was being written twice on R). Just look at the file properties in your file manager to see when it was last written, if needed.
V6 is deprecated: Use V7 for R, V5 for Q
V6:
- Updated for Android 11 B1, verified to run without outputting any errors and is 100% stable.
- Removed one schedutil tweak that is no longer available on A11.
- Reverted kernel entropy settings to stock; tweaked settings were no longer increasing entropy pool.
- Users on A10 may use v6 without any issues, but v5 will still provide very slightly better performance on A10.
V5:
- A minor kernel overhead reduction from scheduler statistics
- Force CFQ as scheduler (just in case non-stock kernel isn't already set that way)
- Two CFQ tweaks, one that eliminated backward seeking penalty (makes no sense on non-rotational storage) and one that my testing showed sped up throughput and in theory should also reduce latency (so a true win-win!).
V4:
- Reverted foreground app schedtune boost, swappiness, vfs_cache_pressure, and dirty_ratio to stock
- Reverted IO scheduler to CFQ
- Removed wakelock blocking - verified no / minimal effect on deep sleep (I got 0.12%/hr idle drain overnight)
(for all of the above, thanks to @Freak07 for the advice / education!)
- Re-verified tx_queue_len (512) and tcp_congestion_control (westwood+) are optimized for WiFi and LTE networks
V3:
- Remove fstrim commands for /data and /cache since device is F2FS and fstrim doesn't apply (thanks to @woundman for pointing this out to me)
- Changed to Deadline scheduler with Franco Dev Team tunables - I just verified still benchmarks better after all these years
- If your kernel does not have Deadline available (e.g. stock kernel), the script will still keep you on Noop, as before.
V2:
- Reduce schedutil downrate limit to increase battery life.
- Block some safe wakelocks to increase battery life.
- Oh yeah, and a magic trick to turn off vm dirty write back timer (it still happens, just memory based and not every 5 seconds), to also increase battery life.
V1:
- Initial Pixel-4/XL release.
ooh interesting! would this play nice with the blackened mod found in this forum?
pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:
I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk
Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out. ?
I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.
Welcome brother... Nice to see another Taimen dev jump into the pool here!
I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks
Running great on fsociety!)
Stock ROM only? Or will it work in pixeldust too.
pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
It should. My script runs after BlakenedMod, so you'll get most of xFirefly93's battery savings, with a little bit of the PK snappiness.
xFirefly93 said:
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:
Click to expand...
Click to collapse
See above. Should be fine to run both... might even be best for some users! Let us know if it doesn't work!
MarcoG: said:
I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk
Click to expand...
Click to collapse
Glad to hear it!
Curiousn00b said:
Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out.
Click to expand...
Click to collapse
Thanks. Hope you like it!
2WildFirE said:
I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.
Click to expand...
Click to collapse
Glad to hear it - it should...
CyberpodS2 said:
Welcome brother... Nice to see another Taimen dev jump into the pool here!
Click to expand...
Click to collapse
Thanks! Great to see you again, too. Athouth, technically, I'm not a Dev
bl4dy_pt said:
I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks
Click to expand...
Click to collapse
Probably won't help much, but I'm working on some improvements for V2 (probably tomorrow or the day after!)
FlatOutRU said:
Running great on fsociety!)
Click to expand...
Click to collapse
Thanks for letting me know!
chopt51 said:
Stock ROM only? Or will it work in pixeldust too.
Click to expand...
Click to collapse
Any ROM!
New Version - V2
A little Sunday night treat!
V2 available in OP, change log in 2nd post.
Better battery life as I tune this in for Pixel 4/XL...
Any testing with kirisakura's kernel? You said not to mix things
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
tlxxxsracer said:
Any testing with kirisakura's kernel? You said not to mix things
Click to expand...
Click to collapse
It should work on any kernel... I've used on on stock and EX on Pixel 4, but I used it on kirisakura on my previous Pixel 2 XL device. If there are any issues, let me know.
woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
Thanks for the heads-up. Running the fstrim command doesn't return any errors, so the script is "safe" to use, but if it's not actually doing anything on the device, I'll remove it in a future release.
woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..
xFirefly93 said:
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..
Click to expand...
Click to collapse
Looks like you're right.
That said, I stopped trimming /System to be safe once Android went SAR, and /Cache is sym-linked to another partition anyway. So, I don't think the commands are actually doing anything anymore - at least not anything useful since /cache isn't really used for much on newer Android versions.
I'll be removing the fstrim commands starting with the next version. In the meantime, it's not really hurting anything.
Thanks for the mod. How can one confirm if this is actually running?
sharpz811 said:
Thanks for the mod. How can one confirm if this is actually running?
Click to expand...
Click to collapse
Look for the log as in the pic. Then view it with your text viewer. It should say script successful :good: