Database Info

[NIGHTLY][ROM][GWK74] CyanogenMod 7 for vendor Bravo (HTC Desire GSM)

This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Device specific ChangeLog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

cm7 is in a development stage and for the first installation i recommend to:
1) install rom
2) reboot, skip setup wizard and setup your access point
3) reboot recovery and install gapps
4) start and follow setup wizard, when requested select desired gapps to be downloaded from market
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
RIL issue:
Switching RIL is cause of know network problem:
* Unable to make a network scan
* Data connection die on asleep (only for some carrier)
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD Addon:
CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
Bootloop free: bind mount do not cause bootloop
Zero Maintenance: no maintenance required after ROM update
Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
By default only App will be moved on SD
Optionally Cache and Data can be moved to SD, but is not recommended (guide)
Require GB Nightly #7 or newer
It's recommended to set the install location to "Internal" under Settings -> CyanogenMod -> Application Settings -> Install location
Before install check if /sd-ext is mounted, "quick system info" under A2SD Storage should report Total and Free space, if it report "information not available" format sd-ext from recovery.
r3: improved installation process (i hope)
r2: added data2sd and cache2sd as options
r1: first release
General App2SD Q&A:
Q: A2SD is recommended?
A: Internal storage perform better than SD, install A2SD only when low disk space warning happen
Q: How to check if is working?
A: run:
adb shell
df -h | grep /dev/block/mmcblk0p2
output should be
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /sd-ext
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app-private
Q: I have installed a2sd addon but now i get low space warning again, why?
A: by default a2sd addon move only app, this is fine for most user but some user with more application have to move also cache and/or data.
Cache2SD can be enabled with
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
reboot when prompted
HBOOT
All alpharev's hboot are compatible except the oxygen version
CM7 version is recommended ~270MB for app (stock 110MB, N1 195MB)
HowTo
Perform automatic backups of files in /system/ while (re-)flashing CyanogenMod
useful link
http://goo-inside.me/google-apps/
md5:
18ef81c567398a93183aff65a41a1565 cm7_legacy_a2sd_r3-signed.zip

murdock's semi official nightly replacement drugs
update 31.05.2011: buildbot is down due to hdd crash. might take a few more days to return - so here is an interims nightly for you:
mirror1: cm_bravo_full_teamdesire-20110601-1925.zip size: 84M (88037737 bytes)
mirror2: cm_bravo_full_teamdesire-20110601-1925.zip md5sum: 38591bab5df5d8f57e714f7888567bdb

Kali- said:
CyanogenMod is a free, community built distribution of Android 2.3 (Froyo) which greatly extends the capabilities of your phone.
Click to expand...
Click to collapse
You mean Gingerbread not Froyo - pedantic I know!
Great work though by the way - excellent ROM!

sykomaniac said:
You mean Gingerbread not Froyo - pedantic I know!
Great wrok though by the way excellent ROM!
Click to expand...
Click to collapse
C&P fail
10 char

andQlimax said:
I was waiting for this thread lol
Any Radio / RIL recommended?
Click to expand...
Click to collapse
no
any 5.x should work

Nice looking forward to follow this thread

Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.

Niiiceee, great work team !

rover.prince said:
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Click to expand...
Click to collapse
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report

before someone ask
Oxygen HBOOT do not work, system is too small (cm7 require other 20mb)
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested

not sure if this is a market issue or titanium backup but my apps don't appear as installed on the market after a restore. btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.

Kali- said:
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
Click to expand...
Click to collapse
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?

MrDevil said:
btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Click to expand...
Click to collapse
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review

Kali- said:
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
Click to expand...
Click to collapse
I am using it personally, I have done the installation what I did.
1. Installed CM7.
2. Installed G.Apps
3. Started Phone, Installed All Apps
4. Restored Some Apps via Titanium Backup ==>Ended Up via Low Storage
5. Installed DT
6. Executed CacheSD
7. Phone Rebooted (Took Some Time to Boot)
Voilla I am happy.

cTrox said:
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
Click to expand...
Click to collapse
we are working for something like 5MB or less
the problem is about download and market.
for sure tmp file are stored on cache and if file size is bigger then free space download fail, not sure if there are other issue

rover.prince said:
Voilla I am happy.
Click to expand...
Click to collapse
this is the most important thing

Kali- said:
this is the most important thing
Click to expand...
Click to collapse
Kali I Love U and CM Team. Great Work with all thumbs UP.

Kali- said:
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Click to expand...
Click to collapse
thanks for the info. looking forward to a rc.
will try to reflash later and restore apps with mybackup and see if it's a market or titanium issue.

How long will it take before CM7 is released in stable mod?
I'm getting tired of using Oxygen 2.0 and its bugs

🔥 READ ME FIRST [FAQ][HTC][PICO/EXPLORER][a310e]🔥

"Those, who fail to read history are bound to repeat its mistakes"
People here have and did and will fail to read the things here and many did and many probably will have to lose their devices. You don't have to lose a device to get knowledge inbetween your ears.You don't have to be stupid. You surely can learn from your mistakes. But There's a better way. You can learn from others mistakes. This thread is a compilation of such mistakes ,that I personally have done and many others ,who did and their solutions aka The easy ways.
So, officially I congratulate you for finding this thread and reading Upto here. So, even if you don't read the whole thread, these are the main stuff you must know is
1. Rooting is a dangerous process -done by developers only. If you did root your device, you assume full responsibility for your device. So, if you can't think like one of the developers at least partly, I suggest you don't root your device ,coz when you mess up, the one who deviced the procedure or Rom will not help you. And everything you find here is in "AS IS " tag.
2.If you have rooted, next thing you must do is backup-
Go to recovery,
go to backup and restore
click backup.
I find it strange that this is not included in the root procedure. This surely would've helped a lot of Picos out there.
3.NEVER DO A RUU
-It unanimously holds the number ONE title for the major causes of bricking of Picos.
Trust me -Surely you can save your device, without the ruu. And with ruu, you're bound to fail without proper knowledge and research.
The only time you are suggested by experts to do a ruu is when you have already done a ruu "and" bricked it.
4. Overclocking here may cause burnt nand. -know what Rom you're using-it may have built in-overclock .
However, overclocking doesn't necessarily produce burnt-nand for all devices.
5.Finally, Not all answers you receive in the question and answer thread are good. Some answers will kill your device. So please judge the credibility of the answerer before you follow the answers. Generally, you could track back their previous answers and their working. Thanks meter is a good source of credibility -but not always -Not all who have big thanks record are helpful neither are they knowledgeable-There are spammers, who trick people into giving thanks.Do your home work before you trust a stranger. Recognized developer title is a good source of credibility.
The above five should save you a lot of trouble.
Ever in trouble? Drop by and read.
Do your googling,if you don't understand anything here.Have a great time !

Re: [faq][newbies only][mini edition]
��To start, this thread is only for newBies,who have rooted thier Rom and have a custom recovery. If you haven't, click here
Alright, this thread aims to answer all the frequently asked questions by newBies. The section this thread aims to answer will consist mostly of custom Roms especially cyanogen.
To start, we'll start with basics
Our phone consists of the following five partitions
1.Boot/kernel
2.Recovery
3. System/Rom
3.1What's not working
3.2 Latest links
4. /cache- error /last log
5.Data
5.1Scripts
6.Common issues after flashing Rom, scripts/GAPPS/PLAY STORE /
Ram
7. USB and CPU ,screen and power button-2/7/13
8. About developers and members
9. ��Burnt nand*recovrecovery 25/6/13 *��
10. STILL CAN'T FIND THE ANSWER ��
10.1LOGCAT
10.2ADB
11.MINI TIPS AND TRICKS
11.1CM9/10 themes
11.2.FONT CHANGING AND language तदधा ಥಮು support adding
11.3.DID YOU KNOW?
12. Recommended apps
13. BATTERY LIFE AND PERFORMANCE
14 .http://forum.xda-developers.com/showthread.php?p=38098604
BUILD. PROP TWEAKS
We'll discuss the faq in each.
All links are here
Index:
http://forum.xda-developers.com/showthread.php?t=1754876
This is the best link you'll ever have
Thanks hrkh83
Guides
http://forum.xda-developers.com/showthread.php?p=36057579
Guides for everything
Thanks hpsgill
Make yourself useful by akshat
Seen it before,
Just read this now
http://forum.xda-developers.com/showthread.php?p=37805872
Stock Roms instead of bricking ruu
tk immortal yash
http://forum.xda-developers.com/showthread.php?p=39101954

Re: [faq][newbies only][mini edition]
/BOOT(4 MB Max )
1.what does this partition contain?
It contains your kernel
2.what is kernel?
It's a in betweener between ROM (/system ) and your hardware.
Basically, a software, which connects the main software (your Rom gui) and the hardware
3 .what is the stock kernel version?
2.6
4. Is there a update available?
Yes. You can update it to 3
3.4 is currently being worked on
5.what are advantages of kernel 3 ?
Nothing much that you can feel
Basically related to stability, security, and future Android Os updates can easily be done for a310e
5.where are the links to kernel 3 ?
Look down
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
With cm9
1.Firewall
2.USB tethering
3. Wi-Fi hotspots
4.Vpn
Anything related to iptables
With cm10
Known issues
Ext4 cannot be mounted?
Temple run 2 and subway surfers reboots*fixed in overclocked kernel *burnt nand *
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. I wanna make my own kernel?
Special thanks to bhargz16
http://forum.xda-developers.com/showthread.php?t=2114594
10.Is there a overclocked kernel?
Yes
http://forum.xda-developers.com/showthread.php?p=38098604
11. How to Flash kernel? Do I need to clean install?
No need to clean install
Copy zip to root of /SD card
Go to recovery
Install zip from SDcard
Choose the correct zip
Install
Reboot
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/Recovery(5 MB Max )
First thing to do after root is to make a nandroid backup.
Go to backup and restore and select backup
1.what is this partition?
It contains your recovery
2.what is recovery?
It's a specialized partition for Android, which is used when something goes wrong.
We use it to change (flash) Roms, change kernels and mostly everything in xda. Make nandroid before you mess up
3. What are the recoveries available for a310e ?
1 .yannou90 (cwm5) recovery
2.Twrp 2 .3 by cute prince
3. twrp 2.2 by oblikas
4.cwm6 by sakindia
5.*OFFICIAL *The latest TWRP by bhargz16( http://forum.xda-developers.com/showthread.php?t=2123503 )
6.cwm6 by nihar.g
Links .check index link in top post
4. Are all of them stable?
The 1 and 5 are pretty stable.
What's not working:
cwm6 by sak let me down big time .
http://forum.xda-developers.com/showthread.php?p=38734554
Except 1,all other recoveries will not show charging animation, when you are charging your phone after switching it off ~instead of charging animation ~you'll be going to recovery
twrp official - some problems with ext4 partition has been reported and also reported to have been fixed. -I never had the problem before and after and I recommend this one 2.5 present here in xda.
twrp cute prince has issues restoring backups (problem with symlink )
5.what's the difference between them?
cwm5 - complete backups of all partitions
twrp - support compressed backups /file manager and other great things
cwm6 - your SD ext partitions will not be fully backed up during subsequent backups,but only the changed files greatly reducing the size of subsequent backups
6. Can you explain more about cwm ?
http://forum.xda-developers.com/showthread.php?p=38100620
7. Recommended apps.?
Recovery file manager aroma 1.8
8. How to flash a recovery?
Two methods described in detail in link above by bhargz16 ~ fast boot
Flash from phone:
Required:
Flash_image binary
You can flash any recovery
From terminal using
Code:
su
flash_image recovery /sdcard/recovery.img
You need recovery.img (renamed like that ) present in /sdcard itself
9. Error while restoring .Androidsecure /sdext ?
http://forum.xda-developers.com/showthread.php?p=39874898
10. Cannot go to recovery /burnt recovery /unable to flash recovery?
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/SYSTEM (235 MB Max )
1.what is it?
Here's where your Rom resides
Any cyanogen /ever/miui roms all go here
2. What are system apps
Any app in /system /app is system app and they have special permissions
2.1 how to make a app system app?
Uninstall the app with titanium backup and copy it's apk to system/app(normal delete apk will not delete. Dex and lib files ) ~reboot ~
Some apkS need it's library file also in /system /Lib (copy from /data /Lib to /system /lib )
3.what is binary?
These are executable ~very important files in /system /bin. (or /xbin in recovery)
Your root su is here
4. What are the roms available?
Many roms are available in xda
Main line ones are
CYANOGEN 7
CYANOGEN 9
CYANOGEN 10
Cyanogen 10.1
Miui
5.What is cyanogen 7 ?
It's a cyanogen version of gingerbread
9 is ics
10 is jelly 4.1
10.1 is jelly 4.2
5.1 what's the development going on?
cm7 *camera was unable to be fixed *development stopped
cm 10*active development now *
cm 10.1 *thread closed *
6. How to install a new Rom? Cyanogen for example?
Download the latest build. Zip and put in the root of /sdcard.
Go to recovery
Factory reset data
Wipe cache
Wipe dalvik
Wipe SD ext
Choose install zip from /sdcard and choose the build. Zip
Wait
Reboot
Go back to main ^|^

The nothing really bugs list
Welcome to THE "NOTHING REALLY" BUGS™
This is the official nothing really bugs Pico web post at xda. Its name implies that the bugs present are really nothing to some people. But to the rest, it may bother a lot. So, this post.
Here you'll find most of the nothing really bugs. All statements having "Nothing really " in bugs list directs here. This is to inform new flashers of what they'll get and what they won't. To make the facts clear,so that you won't have to flash every Rom to find out all the nothing really™ bugs. After all, this is a newbie friendly thread.
Please note that though every effort has been taken to ensure an exhaustive list of all the bugs .Some may not have been stated here .If you do find a bug, which isn't stated here, please feel free to mention it here and I'll add it after being personally confirmation by me or two to three renowned senior member witnesses. Further more, some bugs here may have been fixed. You can take a look at the last edited day of this post to make sure this post is up to date. And you can mention it here,if any of the information found here is wrong.
1.What doesn't work in cm10 4.1 Jelly beans ?:
1video (video recording with some third party apps~Skype video messaging, zoom camera ,camera magix and a lot more)(S. ucam works fully)
2Bluetooth headphones can't be used during call(try using sound about )✘
2.1 Bluetooth stereo headphones ✘
3vsync
4.stock camera force close often and unstable (S. Camera 360/ucam)
5.Wi-Fi unable to turn on ~from settings /notification bar. (s:Flash kernel 2.6)
6.burnt nand
7. Wi-Fi direct (native )causes reboot. (S. 3Rd party app ~fast file transfer)
8.some VOIP~{ex:gtalk(even after normal gapps),and many more}
9.Most streaming video{not flash, but those, which open in mx} doesn't work. Most TV apps don't work (not flash using tv apps)
10. mobile data may fluctuate for some(timedo app to turn on and off airplane mode for every hour)
11. calls robotic call for some
http://forum.xda-developers.com/showthread.php?p=32997468
12. Unofficial adobe flash is flickering too too much. (Only Firefox actually works with flash..which flickers unbearably ~the rest don't even work )
13. Headphones volume control during in call✘
14.USB tethering (native)✘
15. Wi-Fi hotspots work only as open source ✘
16.Bluetooth A2dp streaming ✘
17.Firewall rules don't stick, when put in init.d. Somehow the Rom process overtakes the firewall rules during boot and during some process. My intuition directs the blame at bandwidth controller| throttle service~|Data usage settings|which wasn't implemented properly, but using dirty hacks
18. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting. (s.flash kernel 2.6 with USb mass storage fix here. )
19. Multi mount SD app doesn't work [s.flash kernel 2.6]
OTHERS
1. Battery drain
2.Phone heating
3.WiFi toggle
Total :22[Because, I used this Rom for a long time,so the large number]
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
2.What doesn't work in cm9 ?
forum.xda-developers.com/showthread.php?p=35756952#post35756952
2VIDEO PLAYBACK doesn't work as well as stock
3 Wi-Fi toggle in latest RomS
4 Bluetooth stereo headphones ✘
Experienced by some:
A. Encryption doesn't work (crypt)✘
B.robot call http://forum.xda-developers.com/showthread.php?p=32997468
C.mobile data flickering
Note: video playback is much better in cm10.
Language rendering is also much better in cm10.
3.what doesn't work in Original HTC STOCK ROM?
A. if you ever click "reset to default" in the Camcorder settings..,all future video recordings will overwrite already taken videos and all previous videos will be lost(use ucam)
B. sending a more than 150MB file on Bluetooth file manager app through Bluetooth will reboot your device.
(use stock transfer)
3.1 what's not working in a rooted stock Rom?
(make a nandroid backup first to protect you)
Optimize storage in storage settings
Factory reset will put you in bootstruck.
4.What doesn't work in cm10.1 ?
Camera and lot more minor/major
Too long list
Will update when usable
5.what doesn't work in cm7 ?
Camera
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
3.Wi-Fi toggle from notification bar /from settings
4. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting.
5. Multi mount SD app not working.
With cm9
1.Firewall
2.USB tethering ✘
3. Wi-Fi hotspots ✘
4.Vpn ✘
Anything related to iptables
With cm10
Known issues
Some partitions [?Ext4] cannot be mounted
*burnt nand *
With latest cute prince kernel [power management fix ]:
Mounting of SDcard on some devices
Multimount SD app
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. Sense4 Roms
1.Burnt nand ~most common ✘
2.Random reboots ✘
3. WiFi direct. ✘
4.Bluetooth headphones ✘
Go back to main ^|^
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
S - probable third party solutions
Solutions for burnt nand -Please go to burnt nand section.

[COLOR="RED"]Welcome to [b]▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀[/B][/COLOR]
Welcome to ▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀
Not sure whether it'll be updated,but galaxyfreak released a app on latest Roms ~ http://forum.xda-developers.com/showthread.php?p=38913186
Why this post ?
Because index has only thread links and sakindia123 never updates op
If he does, then this post will not be updated anymore. Other than that, here are some kernel links as well. Other than the main line ones, the others are not updated. Sense4 links are already present in op and here as well http://forum.xda-developers.com/showthread.php?p=40111838 . Any link that's not present in op will only be updated.
1.what's the latest build on cyanogen 9?
Build 13
http://forum.xda-developers.com/showthread.php?p=36626369
#14*beware of burnt nand *
http://forum.xda-developers.com/showthread.php?p=38770875
2.what's the latest build on cyanogen 10 ?
Build 3.2.2.use with kernel 2.6
http://forum.xda-developers.com/showthread.php?p=38183817
Liverpool fan latest 3.2
http://forum.xda-developers.com/showthread.php?p=38447868
Beta 5~beware of burnt nand ~
Video fix by bhargz*liverpl 4 beta5*
http://forum.xda-developers.com/showthread.php?p=39124906
http://forum.xda-developers.com/showthread.php?p=39090779
Beta6~beware of burnt nand ~
http://forum.xda-developers.com/showthread.php?p=39166124
+
http://forum.xda-developers.com/showthread.php?p=39804373
(Flash this to prevent overclock)
Lock screen fix for both beta 5 and 6 .
http://forum.xda-developers.com/showthread.php?p=39043840
2.1 Aokp build link
http://forum.xda-developers.com/showthread.php?t=2208242
3.what is the latest build on cyanogen 10.1 ?
Alpha 3
http://forum.xda-developers.com/showthread.php?p=38094629
Alpha 4
http://forum.xda-developers.com/showthread.php?p=38325531
4.what's the latest build on kernel?
Old Kernel 3
http://forum.xda-developers.com/showthread.php?p=36572115
Kernel 3 v2 only for sense
http://forum.xda-developers.com/showthread.php?p=38466559
http://forum.xda-developers.com/showthread.php?p=39730163
Kernel 3 v2 for cm10
http://forum.xda-developers.com/showthread.php?p=39737920
http://forum.xda-developers.com/showthread.php?p=39804373
5. Is there a overclocked kernel?
http://forum.xda-developers.com/showthread.php?p=38098604
kernel 2.6=garudav5kernel
6. Kernel 2.6 for JB ?
http://forum.xda-developers.com/showthread.php?p=37649737
http://forum.xda-developers.com/showthread.php?p=36303556
7. Kernel 2.6 for ics?
http://forum.xda-developers.com/showthread.php?p=35797210
http://forum.xda-developers.com/showthread.php?p=36526379
http://forum.xda-developers.com/showthread.php?p=37550173
8. Side effects and solution of using kernel 2.6 on a kernel 3 based Rom:
http://forum.xda-developers.com/showthread.php?p=39452607
Basically, USB storage may not work.
To, make it work, Flash the fix attached with this post(don't remove battery @ any stage:sly-tested on my twrp 2.4.4 with cm10beta5.May not work with ics.
Alternatively, you can use multi mount SD app /root tool box lite app.
Attached zip md5: 8216eaf4a357b9cddc5cfd29b8d05a50
Attached zip sha-1: 408a075479745fe1713f8c55a968801f7f6160dd
Some more links :
http://forum.xda-developers.com/showthread.php?p=40964578
Super wipe zip
http://forum.xda-developers.com/showthread.php?p=38338418
Nand recovery procedure:
http://forum.xda-developers.com/showthread.php?p=38098622
tk to akshatshenoy.
Flashing an older ruu:
Not recommended @ any stage
http://forum.xda-developers.com/showthread.php?p=38694608
Even if it works,you might have problems data, battery drain etc.. if you Flash a wrong radio
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
http://forum.xda-developers.com/showthread.php?p=40035607
How to install kernel? Clean?
http://forum.xda-developers.com/showthread.php?p=38098513
QUESTION NUMBER 11 ABOVE
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/DATA (150 MB )
1.WHat's this?
It is the internal memory
2.Why is it important?
Because this is the place where all the apps go
No /data = no more apps
3.what's our available internal memory?
150 MB
User available 90 MB
4. Any way to increase internal memory?
By scripts
5 .Recommended apps to diagnose application not installed
Diskusage app
Log cat
6. What does a app contain?
App when installed splits into apk dex,and data(lib+data) files
Go back to main ^|^

Re: [faq][newbies only][mini edition]
SCRIPTS
Before we start, a app when installed takes space as three parts.
They are apk,dex and data (lib+app data)
All scripts work by symlinking
1. What are the scripts available for our explorer?
Partial scripts
A.Link2SD app
Moves apk,dex,lib~doesn't move app data
B.Root data2SD app
Need ext partitions
Moves application data2 ext
Full scripts--Need init.d support able to move fully /partially as per requirements
Links available in index
1.Mount2SD
Download from play store or from here check index
Famous for it's stability and frequent updates
Issues +
2. Int2ext
As per script, moves partially /fully .
Has a large user base
issues ++
3.s2e
Moves fully.
Issues +++
NO official version for jelly beans.
4.a2sd darktremor
Issues ++++
However works pretty well with stock Rom and jaggy Rom
Discontinued
5.ungaze script
Issues +++++
I don't recommend it.
Why not?
Because
http://forum.xda-developers.com/showthread.php?p=33750812
http://forum.xda-developers.com/showthread.php?p=31915607
1.1 mount2SD doesn't work? Script not executed fully @ boot?
Flash kernel 2.6 from above and you should be good to go.
2. How do I increase internal memory (literally ) from 150 MB to 2GB(for example SD ext )?
Use mount2SD reverse mount
Use int2ext
Side effects:
As per Android rules, 10% of internal memory will be unavailable
So, 200 MB out of 2GB SD ext will be unavailable
Mount2SD also has normal moving methods ,which will make Android think you'll have 150MB but you can fill up 2GB inside of 150 MB (Here 10% would mean 15 MB)
3. I installed d2ext/similar ,I'm not able to install more apps ,even though I have more SD ext space?.
A. First make sure you don't hit 10% data limit described above
B. Use diskusage app to determine,which partitions are full
For example- some scripts don't move dalvik and so dalvik will fully accumulate in /data creating no space.
C. Fix permissions from recovery, wipe cache and dalvik and reboot.
4. My Rom doesn't have init.d support /I'm using stock Rom?
Check index
You can add init.d support by
Flashing custom kernel (cranium)
Flashing scripts to make init.d support (or pimp my Rom app[not tested])
5. Where to add scripts before flashing Rom?
Add it in /system/etc/init.d (permissions are rwx rwx rwx ,if you're adding this in recovery after flashing )
For mount2SD add configurations folder in /data/m2sd.
6. How to migrate from link2SD to mount2SD?
http://forum.xda-developers.com/showthread.php?p=38840247
7. Is there a full script so that I can use both my internal memory and SD ext?
A bit complicated, but this what I use...
Configure mount2SD
To move both apk and dalvik
Don't move data.
Then open titanium backup to move app data
@First move one app data to create data2SD directory.. then you can batch move whatever apps you think fit.
But please make sure you have at least 10 to 30 MB in /data and in/SD ext (SD ext not necessarily ) before a nandroid backup. Otherwise restoreS will not work.
Go back to main ^|^

Re: [faq][newbies only][mini edition]
Common issues with scripts:
0. Device stuck @ HTC logo with 4 error icons on all four corners
Since you flashed an ruu and failed user data fail etc.
Unlock bootloader if possible
Flash twrp recovery again
Code:
fastboot flash recovery.img
Then go to recovery with this command
Code:
fastboot boot recovery
Now that you're in recovery wipe everything, format everything .
If flashing failed /you can't enter recovery, do this keeping twrp recovery.img in /SDcard
Code:
fastboot boot /sdcard/recovery.img
Do cute prince recovery procedure shown in burnt nand section
Flash erase mtd3 as well
Now Flash your Rom and boot
If it doesn't boot, repeat the whole procedure above and now
Do ruu.
If all the above failed,
http://forum.xda-developers.com/showthread.php?p=39181288
Read the above thread fully. That's the last resort.
Moral : Don't ever Flash an RUU (if you haven't already )
You can Flash stock Rom ~safer
1. Device struck in HTC logo
Wait for 15 minutes
Try pulling out battery and reboot
Update busybox and try installing scripts again
Convert your partition to ext3
Change your kernel to 2.6
2. Mount2SD ~apps update after every boot?
Turn cache off in app
Turn safe mode off
Clear cache and dalvik ~fix permissions ~reboot
Common issues after flashing:
1. I get status 7 error?
Open archive with Bluetooth file manager and check archive integrity
Try different compression method(thanks hpsgill)
Delete system apps
2. I get status 0 error?
Update binary used is different
Exchanged update binary from a working zip to this one
Other errors can be cured by changing recovery .
http://forum.xda-developers.com/showthread.php?p=38469360
Common issues after flashing Rom:
1. Always do a clean install
To wipe everything except /sdcard.
Even in /sdcard delete Android /data after backup
2. No I won't listen. I want to do you a dirty install. Show me how?
Your choice
http://forum.xda-developers.com/showthread.php?p=35903694
3. I get force closes of all apps?
Dalvik problem.
Clear cache and dalvik cache and reboot
4.I get force close of a specific app?
If it's a paid app, then you need to change your Android id to your original Id with Android id changer /titanium backup
Not a paid app?
Clear cache and data of that app and reboot
Fix permissions
5.reboot after reboot?
Thanks bhargz16
Kernel problem. Change kernel
GAPPS:
1. This gapp always force closes?
A. If it's a gapp found on play, just uninstall that gapp from system using titanium backup and then reboot and install from play store.
B.if not found on play, then try flashing a different gapps version from goo.im .
Make sure you have enough space on /system and on /cache before flashing and then flash. If not delete unused apps like stock keyboard ,etc
2. RPS5~AEC0/927/any other error while downloading apps from play?
A. Clear data cache of play store app
Reboot
B. Clear data of google services framework
Reboot
C. Remove your google account and re add it. Reboot.- this worked for me.
3. All my apps are missing from installed apps in play?
Wait for some time,if you've flashed a new Rom
Clear data and cache of play store
Reboot
Download app eric market fix *use @ your own risk *
Repeat the solution of questions 2.
Go back to main ^|^
Part 2 on next page :thumbup:

Re: [faq][newbies only][mini edition]
CPU:
1.Can you overclock?
IMO,
All overclocking burns nand.
It's just a matter of sooner /later.
Read this post before attempting anything
http://forum.xda-developers.com/showthread.php?p=38445346
Burnt nand recovery procedures here ~~the third post below this post
http://forum.xda-developers.com/showthread.php?p=38098622
The links below are old. All latest Roms come with overclocked burning kernels.
cm10:
http://forum.xda-developers.com/showthread.php?p=38189883
cm10.1:
http://forum.xda-developers.com/showthread.php?p=38336080
gpu oc
http://forum.xda-developers.com/showthread.php?p=38331698
cpu oc
2. Governors ~what are they?
As the name says they govern when the cpu should go to higher speed and when they should sleep
Performance governor always keep your phone at Max
Powersave keeps your cpu always at low
USB :
1. Flashed kernel 3 and USB doesn't work.?
Flash kernel 2 back.
2. I want to know how to fix USB +kernel 3?
Don't know
3. Can I have usb otg ?
No, not yet.
SCREEN AND POWER BUTTON and soft keys:
1.SCREEN turns on after turning off ?
A. Some apps are trying to make screen on. After screen turns on, go to settings immediately and open running applications, you may be able to find the culprit. It's probably the app, which is restarting. Some apps like lock any app screen etc. Logs could be helpful.
B. Some users reported it could be a hardware problem -look below for power button issues.
C. Some users reported it could be a script problem (rare )
2. My home screen button and /or search buttons doesn't work?
A. Did you do a dirty install of new Rom
Clear cache and dalvik and fix permissions and reboot
B. Copy com.Android.providers.settings /databases from your previous nandroid backups(use yaffs file manager /nandroid manager)and paste it in it's respective location now (paste it using file manager in recovery )
C. If that doesn't work, clean install again
Tech savvy? ~search for device provisioned 1 in cyanogen forums
http://forum.xda-developers.com/showthread.php?p=38633404
3. Power button doesn't work properly ?
A. If it's not a software problem(try the above solution first),then you broke it.
If you broke it, avoid using the power button anymore-use attached scripts indeed.
There are apps in market to simulate power keys.
Or
http://forum.xda-developers.com/showthread.php?p=38633404
Go back to main ^|^

Re: [faq][newbies only][mini edition]
Miscellaneous topics:
Subject to change without prior notification
Developers:
1. Who are the developers that make these roms?
1. Cute_prince
2.sakîndia123
3.derefas
4.lirokoa
5.liverpool fan
6.bhargz16
7.nihar.g
8.ngolralph
And many others. The above are the developers of the roms that I used and present in no order.
2. Why doesn't sakindia123 update the OP ?
Disclaimer: Since it is one of the most faq by newbie,I'm forced to discuss here. I personally do not know sakîndia. If you still want more info, contact senior member hpsgill
You see.. He does nothing without reason. If he doesn't, then the last build present in op will be more /less equal to the latest build. There are other reasons ,which if I had to speak of them all, time wouldn't let me and I would have to deal with flaming members and mods and deleted posts and locked threads . Furthermore that question is well out of the scope of this thread. You are instructed not to ask this question any where.
YOU HAVE BEEN WARNED.
3. How can I contact these developers?
You can by studying Android development and codes, bccms,404s,tr2s and then talking to them. You'll have better luck talking with non recognized developers than the rds.
And try discussion threads .
4. Why doesn't a developer answer my question? (I'm being polite here)
Because the developer doesn't know the answer
w.r.f to http://forum.xda-developers.com/showthread.php?p=38095857
Or your question has already been answered. Try searching for your question at the least 10 pages back.
or your question is too silly to answer
Or your question is not seen ,because they don't have time .
5. Why do they do this ?
For passion of development, addicted, and for learning purposes.
So, that means they don't work for you. They don't help you. They do what they want.
6. I feel a emptiness around forum members. Was there a developer who worked here, yet left without goodbye?
Well not sure about goodbye, but yes his name is jaggyjags.
sakIndia123 came only late and his first work his cranium kernel, which he abandoned like it was nothing.. buried it along with jags. Cruel things did happen before you were here.
Go back to main ^|^
Members:
1. Why won't members answer my question?
Again, thanks to bhargz16
http://forum.xda-developers.com/showthread.php?p=38095857
Or question has already been answered over and over again. Try searching for your question and read at the least 10 pages back.
Or they don't want to help you
Or may be you aren't polite
Or they want thanks
2. Why do they want thanks?
You see.. you should hit thanks for them in order for them to reply
3. Why hit thanks?
Because they are thankaholics .
This addiction
Some call it want,
For some it's need
Some call it greed
And some call it hunger
And some childish foolishness
Never hit thanks, unless you mean it. Never sell yourself short. Mean it, then hit it.
http://forum.xda-developers.com/showthread.php?p=32867800
My first thread closed by mods
:crying:
Having said that, please do be grateful for what you receive. Hitting thanks is like giving a eternal reputation mark on them rather than just saying it. Saying just makes a temporary mark. Get it. 
4.what is spam?
Spam is going out of topic . It never should be done in dev threads unless thread is dead.
Some do the work of mods pretending to be mods.
5.who are mods?
They are moderators who have power to ban anyone at will (in short )
And they are losing patience
http://forum.xda-developers.com/showthread.php?p=37950595
6.Can I spam here?
Feel free to speak what you want..
7. If I feel something wrong is going on /flaming /threatening, who should I report to?
You can use the report system~that (!) mark over every post. Click it and your issue will be resolved within a hour(probably ).
Go back to main ^|^

[color="red"] [b]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1
0. What's burnt nand?
It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.
Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings
A case of burned /system partition in cm10 beta6 running overnight:
Uploaded with ImageShack.us
A late case of burnt nand of /data :
Uploaded with ImageShack.us
1 &2:Not applicable anymore. Peace!
3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?
Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.
Sources:
http://forum.xda-developers.com/showthread.php?t=1847002&page=400
http://forum.xda-developers.com/showthread.php?t=2243719
http://forum.xda-developers.com/showthread.php?p=39985385
http://forum.xda-developers.com/showthread.php?p=39799173
http://forum.xda-developers.com/showthread.php?p=39439861
http://forum.xda-developers.com/showthread.php?p=39428922
http://forum.xda-developers.com/showthread.php?p=39402187
http://forum.xda-developers.com/showthread.php?p=38941663
http://forum.xda-developers.com/showthread.php?p=39216556
http://forum.xda-developers.com/showthread.php?p=38945489
http://forum.xda-developers.com/showthread.php?p=39197918
http://forum.xda-developers.com/showthread.php?p=39169697
http://forum.xda-developers.com/showthread.php?p=38657723
http://forum.xda-developers.com/showthread.php?p=40616272
http://forum.xda-developers.com/showthread.php?p=39331139
But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.
http://forum.xda-developers.com/showthread.php?p=39196574
THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.
4. What are the symptoms of burnt nand?
Early symptoms:
You'll notice a strong drop in your free space in /data
Late symptoms:
/data free space is Nil /below 50%of what you saw before
Error in /cache /recovery/log.
Error in /cache/recovery/last log.Not readable.
No apps can be installed
Rom lags like hell
No Rom can be flashed /boots
Previous nandroids ,which are successfully restored before fails to restore now.
Really abrupt and fast restores with twrp
RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)
5. How can I diagnose burnt nand early?
If you suspect burnt nand ,
1.Watch out for free space in /data and watch out for sharp reduction.
2.Download this app Disk Usage and watch out for increase in system data in /data
http://forum.xda-developers.com/showthread.php?p=39464989
3.Make a dmesg and look for these errors
http://forum.xda-developers.com/showthread.php?p=36834988
4.Definitive method is this :
shahrooz_ra said:
hello
is there any linux terminal command for check badblock on nand memory?
Click to expand...
Click to collapse
1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW
2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]
3.Open terminal emulator on your phone
4.type or copy and paste this code and press enter
Code:
su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh
5.if it doesn't work first time, paste twice.
6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!
And Now you'll see the number of bad blocks you've got.
You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.
6. What are the parts affected by burning?
Proved to affect
/Data
/system
/cache
/recovery
Rest is unknown
7. Ok I managed to burn my nand What are the recovery procedures available?
I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.
Other long procedures:
Cute prince recovery procedure:
http://forum.xda-developers.com/showthread.php?p=36868966
I think Cute prince missed this .Just add this at the end
Code:
./flash_erase -N /dev/mtd/mtd3 0 0
7.1 I GET FLASH ERASE NOT FOUND?
Flash the flash_erasemadeflashablebyBANNED.zip
Derefas recovery procedure:
derefas was the one who actually gave the idea of recovering nand
http://forum.xda-developers.com/showthread.php?p=36867557
Sachin Thomas recovery procedure
Developed lately *can be done on phone itself */if it didn't involve recovery /*
http://forum.xda-developers.com/showthread.php?p=38941897
Recovery recoveriNG procedure (bhargz16)
http://forum.xda-developers.com/showthread.php?p=39198068
8. I can't find my answer here?
Go to official burnt nand discussion thread
http://forum.xda-developers.com/showthread.php?t=2183130
Or you can ask your questions here.
9.can I Flash any other kernel to prevent overclocking?
You can Flash garuda2.6
Link in latest links post page 1.
http://forum.xda-developers.com/showthread.php?p=38098567
Side effects:
http://forum.xda-developers.com/showthread.php?p=39452607
10. Some more links:
Unknown recovery procedure
http://forum.xda-developers.com/showthread.php?p=36836090
MTD status report:
http://forum.xda-developers.com/showthread.php?p=36837173
11. Cannot go to recovery /burnt recovery /unable to flash recovery?
Not sure of the exact command,but will work.
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
12. GPU OC ?
gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.
12.1 is it safe?
I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.
12.2 do you recommend it?
"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".
12.3 How to remove gpu oc ?
Its present in kernel. Flash another kernel. Or modify source and compile yourself.
Present at arch/arm/mach-msm/msm7x27a.c- kernel source.
Try here
Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.
13. Was there anyone unable to recover and lost thier device for ever?
AFAIK,
"The lost thier device for ever list RIP "
Ghostking
Hawk378
And May be many more
Legend *:
Attachment list:
***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************
Provided "AS IS"
1- script to detect badblocks by banned.
2-flashable zip to detect badblocks by btfb0
3-Terminal method to detect bad blocks by banned .
4-flashable zip to detect bad blocks by banned.
5- Recovery procedure to delete bad blocks- Made flashable by BANNED.
All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.
*USE AT YOUR OWN RISK*

Re: [faq][newbies only][mini edition]
I have a question not answered here?
Post your question in the q&a section after making sure that your question hasn't already been asked.
Please use search button on the top right to make sure that your question hasn't already been asked. And it'll help you to find more answers.
Follow detailed instructions here
http://forum.xda-developers.com/showthread.php?p=33608527
And post with logcat increases your chances of resolving the problem
ADB
What is logcat and ADB?
Special thanks to akshat.shenoy
http://forum.xda-developers.com/showthread.php?p=37805872
He'll explain things better
Basics of ADB:
http://forum.xda-developers.com/showthread.php?p=9936674
Partition and wipe SD ext with ADB:
http://forum.xda-developers.com/showthread.php?p=38706881

Re: [faq][newbies only][mini edition]
reserved

Re: [faq][newbies only][mini edition]
MINI Tips and tricks:▶?
1.How can I apply cm9/10 themes?
http://forum.xda-developers.com/showthread.php?p=35530897
Download the zip from here, read instructions there and flash it in recovery
Now you can use any HDPI themes on your Pico
Thanks ngoloralph
2. How do I change fonts?
Download Rom toolbox lite and go to font installer;
A. If you're on stock, the rest is automatic
B.if you're on cyanogen 9/10/11,if you change the droid sans /others as recommended by app, you'll end up in boot loop (possibly because of symlinking of robot sans & droid sans )
In such a case go to preferences and click to overwrite only roboto regular font and everything will be fine.
Take a look
Uploaded with ImageShack.us
3. How do I add a new language support to my device?
Note: no new language gui can be added by this method. This only adds support. Instead of seeing boxes, you may see your language. If you want full language support, you can go to this abandoned thread.?? http://forum.xda-developers.com/showthread.php?p=40890599 ??
Language support can simply be added by adding a Android supported language font file in /system /fonts and give it permissions rw r. r.(font files can be found all over xda )
Step 2. Open system /etc /fallbackfonts.xml...
There should be a lot of font file names there.. just delete a font name that you don't want and add your font file name (the name of the file which you put in /system /fonts)
In there.
Practice makes perfect.
This method however doesn't work /only partly works for complex languages /script like Hindi Arabic etc.
DID YOU KNOW?
1. Long pressing reboot button (in the menu after pressing power key) will get you into safe mode
2. Long pressing power keys and volume keys + and- for more than 30 seconds will reboot your device (tk to hrkh83)
3. Repeatedly pressing certain options(like Android version) in the about menu in settings(on cyanogen ) will take you into different settings (tk liverpoolfan)
Go back to main ^|^

Battery drain
BATTERY DRAIN
Of course, we're gonna talk about drain.
Before we start, I want to disprove some prevalent concepts
1. Battery calibration
It is supposed to increase Battery capacity and increase Battery life and it makes your phone to show the correct Battery on the notification bar.
FALSE
It doesn't do any of those. Calibration is just deleting Batterystats.bin file. That file holds info about how many seconds each apps were running for.typically it's blameometer. It shows the information you see in the battery chart in your settings. Nothing more.
Source: article
2. Cycling your battery life from 0 to 100 and 100 to 0 will typically increase Battery life. Further more you should make sure it comes to zero by turning on the phone,every time it got switched off on it's own.
FALSE AGAIN
Nothing could destroy your Li-On Battery than extreme low voltage. You can be sure that this will destroy your battery life more than anything. During storage it's recommended to keep the battery in cool place with 40%Battery.
So, don't use any battery draining app from market.
Ok, since we took out the false foundation, it's time to put some true working tips to save your battery during usage and it's overall life
1. It's recommended to charge as often as possible ~every time you get a socket. Though not to keep @100 all the time. Overcharging theoretically may damage your battery, but your phone comes with various safety mechanisms to prevent charging after that.
2. Limit the number of apps. Definitely would produce good Battery.
3. Limit the number of apps, that run in background all the time.
Typical example would be facebook.
PERFORMANCE:
4.Disable autostarts for all apps, that you don't use much~using autostart manager.
Disabling autostarts for the clock app will make you get up late. Use common sense.
This alone should drastically improve your performance
5.Use lightweight launchers ~Nova.
Go (any go products) is not advisable
6.Post ICS, Disable media scanner receiver.
You can use elixir app to disable media scanner receiver. This will scan your SDcard over and over again resulting in Battery drain,which is significant, if you use a bigger SD. Use media scanner root to enable and disable.
As far as the usual ones,
7. Disable autobrightness
8. Keep screen @ minimum brightness
9. Disable autorotation
10. Disable location services.
GAPPS:
11. Disable GSF (google services framework ) receivers ~the ones with gtalk on it.
12. Disable auto sync
You can use timedo /timer Android to turn on sync twice /thrice daily.
13. Reduce number of accounts. Better to keep single than three accounts.
14. Good internet connection. Amount of energy taken to re connect is supposed to be far more than amount needed to keep a connection.
15. Undervolt/with underclock
RECOMMENDED APPS:
1.BETTER BATTERY STATS ~free for xda.
2. Onepower guard
I haven't found satisfying results with this app, but still try it out
3.greenIFY
I haven't used this @ all.
4. Any app, that is used to reduce /increase heartbeat sent to google servers.
Well, that's all I've learnt as of now.

Re: [faq][newbies only][mini edition]
Recommended apps section (only free)
Top apps
0. Superuser by koush (Clockworkmod)
1. Titanium backup
2. Efficient backup
3. Floating logcat ~logcat extreme
4. Catlog
5. Aroma file manager (recovery use only)
6 .Es file explorer
6.1 es file explorer v2
7. Yaffs file manager
8. App extractor
8.1 nandroid manager
9. Loaderdroid
10. Xda app
11. Elixir (much useful to disable app components than it's actual use)
12. Android pro widgets(similar to HTC friendstream)
13. Nova launcher
14. Timedo
15. Live logcat lite
16. Rom toolbox lite
17. Screen stand by root(turn off screen without making phone to sleep)
18. Disk Usage
Launcher:
1. Nova
2. Apex
Downloaders:
Loaderdroid
Multimedia players:
Video
mx
bs
qq
Audio
Ttpod
Equalizers
NOOZOXIDE REWIRE PRO
Walkman sound enhancements
Awesome beats
Cyanogen Dsp(better than stock )
Equalizer from market.
Cam/corDer /video recorder:
Camera:
Camera 360
ucam
spycam
Video recorder
ucam
Zoom camera
Camera magix
Browsers:
Fast and server based
Uc browser mini
Opera mini
Opera mobile
uc browser
Puffin browser
Full fledged browsers
Firefox
Dolphin
Google chrome beta
Chrome
KEYBOARDS ?
Touchpal keyboard
mĺ has internet permisn wid emoji
Office apps:
Kingsoft office(better than paid apps)
Zip extractors:
Zarchiver(ant-one)
Screen off(w/wake lock):
Screen stand-by
File managers:
ES explorer
Fx file explorer
Call recorders:
No known call recorders are working.
Stocks:
Personal finance
Superuser:
Superuser by koush ~open source&free
Super su ~made pro free after the release of prior~closed source ~
⇧Go back to main ♠
THE END.
© All rights reserved 2013?

Autoramdisk exchange alpha
MINI ADVANCED SECTION:
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.071 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Update:
I have got it to work and complete
http://forum.xda-developers.com/showthread.php?p=40035607
Old post: too lazy to delete
Present condition:
Hi. I cannot get it to work on HTC Pico yet .It may work on other phones. If someone can, please feel free to complete it provided you give proper credits And you do not make money out of this.
What's this?
It's a procedure (wip) to Flash any kernel without the need to change ramdisk.
As new kernel gets released, you don't need to change ramdisk to suit your Rom.
Automated procedure:
Open any kernel.zip with any zip extractor on your phone
Copy the script below and paste it in updater-script present in meta~inf/com/google/Android
(delete any other things written there. )
Code:
package_extract_dir("bin","/tmp");
set_perm(0, 0, 0755, "/tmp/busybox");
set_perm(0, 0, 0755, "/tmp/unpack-bootimg");
set_perm(0, 0, 0755, "/tmp/mkbootimg");
set_perm(0, 0, 0755, "/tmp/dump_image");
run_program("/sbin/dump_image","boot","/tmp/oldboot.img");
run_program("/tmp/unpack-bootimg", "-i","/tmp/oldboot.img","-o","/tmp");
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/busybox", "mkdir","/tmp/boot");
run_program("/tmp/unpack-bootimg", "-i","/tmp/boot.img","-o","/tmp/boot");
run_program("/tmp/busybox", "rm","-r","/tmp/kernel");
run_program("/tmp/busybox", "mv","/tmp/boot/kernel","/tmp/kernel");
run_program("/tmp/mkbootimg", "--ramdisk","/tmp/ramdisk.cpio.gz","--kernel","/tmp/kernel","-o","/tmp/newboot.img");
write_raw_image("/tmp/newboot.img", "boot");
delete_recursive("/tmp/newboot.img", "/tmp/boot", "/tmp/oldboot.img", "/tmp/kernel", "/tmp/ramdisk.cpio.gz","/tmp/boot.img", "/tmp/busybox", "/tmp/unpack-bootimg", "/tmp/mkbootimg");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Download zip files from the source link below
Extract it and copy the bin folder from there to your kernel folder directly.
There should be 3 folders in your kernel folder ~bin folder, meta inf folder, system folder and boot.img
Now compress it and Flash
Note that this is only applicable to change ramdisk. If the boot. Img needs more work than that, it won't work. Essentially, it won't work on sense4 compiled kernels and vice versa
Manual terminal emulator method:
Alright guys, one last tutorial from me making my last mark here .This tutorial is not tested fully and probably never will be due to lack of time. And it will work for sure ~but May have syntax errors.
Credits:
1.trevd for arm executable binaries.
2.Xda university.
Requirements:
1.Any Android 2.3+ rooted
2.Android terminal emulator
3.arm executable unpack-bootimg binary and mkbootimg binaries (find it below )
History:
I wanted to change ramdisk for kernels for a long time on phone itself ~probably for a year or more . But anyone who tried to unpack using normal unzip apps would've noticed that other data.img and even system.img in clockworkmod could be unpacked easily, but not the boot.img and recovery.img. When I searched to unpack, it was easy with computers using the unpackbootimg binary for Linux. Problem was it wasn't cross compatible with our phones . So, I was searching for quite a while,until I found trev on xda university and he had made arm executable binaries for unpacking, repacking. Actually the main reason these binaries were created was for far greater and more advanced purposes i.e. to use apply patch functions in update binary and update script to Flash ramdisk on phone without flashing the kernel itself or vice versa (AFAIK)[ The apply patch functions are used in normal ota updates for any Android phone ]. Anyway I took those binaries to unpack kernels on our phone to change ramdisk. I write this for those, who want to change ramdisk on thier phone, but had no experience in PC whatsoever. And also by doing this, I share the unpack boot image binaries by trevd for Android phone ,so that any advanced member May use it for kernel updater scripts~think about it ~one zip for all cm9/10/10.1. Ofcourse the rest is up to you. Thanks for reading
Procedure:
1.Download the zip given in source below
2.Unpack it
3.Find these two binaries in /system/bin
Unpack-bootimg and mkbootimg
4.Copy them to /system/bin and give them full execute permissions in es explorer and read/write permission for user.
5.For easy remembrance,say, b1.img is your original boot image for your Rom(and Android,say cm10 ) and b2.img is the new kernel released for cm10.1
6.You want to change the ramdisk ofb2 cm10.1 to cm10 ,so that you can Flash the new kernelb2 for your cm10
7.Create new folder in SDcard named boot and put both b1.img and b2.img there
8.Open terminal.
9.type the following code one by one
Code:
su
cd /sdcard/boot
mkdir /sdcard/boot/b1
mkdir /sdcard/boot/b2
unpack-bootimg -i /sdcard/boot/b1.img -o /sdcard/boot/b1
unpack-bootimg -i /sdcard/boot/b2.img -o /sdcard/boot/b2
rm /sdcard/boot/b2/ramdisk.cpio.gz
mv /sdcard/boot/b1/ramdisk.cpio.gz /sdcard/boot/b2/ramdisk.cpio.gz
mkbootimg --kernel /sdcard/boot/b2/kernel.img --ramdisk /sdcard/boot/b2/ramdisk.cpio.gz --base 12C00000 -o /sdcard/b2new.img
rm -r /sdcard/boot
Note: the last rm command will delete all your old kernels ~don't execute it, if you don't want to have it deleted.
10.Now you have new kernel boot image with your ramdisk in /sdcard/b2new.img
11.Put it back in the zip with it's modules and
12. Flash
13.Hoping it'll work.
14.That's the end.
Source and binaries here:
http://forum.xda-developers.com/showthread.php?p=36931024
For dream and Sapphire models, you can use the binaries created by koush ~ which is found in his github ~any kernel project.
I'll probably be leaving soon
Kind of feel like working for xda. I guess sak and others would probably feel like it later. It's been great while it lasted. So this is probably my last project. If I did have some extra hardware during this period, things May have been different. It's good, while it lasted.
"The fantasy of a dream is that, it's still a dream, when it becomes reality, then it's no more a dream and the fantasy is lost. "
「Good bye xda」
So long:angel:

Re: [faq][newbies only][mini edition]
one more
The Infamous BUILD.PROP Tweaks :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
from
http://www.droidforums.net/forum/droid-4-roms/234899-examining-build-prop-tweaks.html
Guess that'll end this hoax for good.
One thing that was useful for me was this
http://www.modaco.com/topic/347274-guide-making-cm-utilise-both-cache-and-data-for-dalvik-cache/

[MOD] [All ROMS] F2FS for TF700T

******************* INFO&CREDITS *******************​
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************​
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************​
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************​
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************​
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************​
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************​
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************​
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button

Downloads
********************************************************* Downloads *********************************************************​
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************​
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch

Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.

Do you run into any issue with this f2fs so far?

LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5

Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?

deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk

I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk

berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5

Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!

Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET

yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...

_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.

_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go

CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...

I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353

sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk

Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.

delete please

sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.

[MOD] Int2EXTV2+ Optimised for the HTC Explorer

For tested and supported ROMs see post#2
As most of us may know from past @croniccorey's int2ext scripts have been the de facto standard for internal memory scripts (for mounting /sd-ext as /data) and also that the zips are notorious for throwing "error executing updater binary" errors for almost everyone. One specific problem i encountered while using @kirmaniarslan's unofficial CM 11 weekly build that when i flashed an ART Optimised version of the script it used to show internal memory full issues at 120~128MB usage but in the storage menu in settings it showed more than a gig free (my sdext measured 1.5 gigs). This hurt a bit since i had been enjoying the awesome (and aw3som3[emoji14]) ROM a lot. So I rigged together a modded version of the script to try and get rid of the error. the attached zip is a direct result of that effort. Try it out on other roms as well if you faced the same problem as me and report in the thread.
Instructions for flashing
INIT.D support is REQUIRED!!!!
It is recommended that you flash this over a clean ROM flash or after removing existing scripts and cleaning up cache and dalvik cache
Flash it using recovery mode no need to wipe data
ensure you have created an sd ext partition before using the script
done enjoy!!!
Download Link for flashable zip : http://d-h.st/ddxG

Supported ROMs
1. CM 11 Weekly Builds by @kirmaniarslan
2. Omni ROM by @thewisenerd
3. Carbon ROM KK by @7alvi
4. Evervolv BETA1 by @thewisenerd
5. PAC ROM Port by @MSF Jarvis
6. Omni ROM by @thewisenerd
7. SlimBean by @7alvi
8. ParanoidAndroid Beta 3 by @thewisenerd
More to be tested and added soon...
For those for whom INT2EXT doesn't work properly, use Mounts2SD from here : [URL=" http://forum.xda-developers.com/showthread.php?t=3162148" ]MOUNTS2SD App Tutorial[/URL]
Sent from my HTC Desire 616 dual sim using Tapatalk

Thread closed at OP's request.

[ROM-DISCONTINUED][SGH-I727][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Skyrocket

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is CandySiX. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @Cuzz1369 @rc420head @Flashalot @Venomtester @Darknites @javelinanddart @calebcabob @NoSpamDan
ROM
DEVICES/KERNELS
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
FEATURES
Choose from CMTE or OMS (RRO Layers is DEPRECATED)
Battery bar
LCD density options
Multi-window
Status bar customization
Quick setting customization
Quick setting pull down options
Force expand notifications
Time contextual headers in panel
Dark UI switch
Advanced power menu
Extra IME options
In-Call vibration options
Lockscreen customizations:
-Shortcuts
-Music visualizer
-Weather​Animations:
-Power menu
-List view
-System
-Toast​Navbar customization (CMTE only):
-SmartBar
-Fling
-Pulse​ Hardware Buttons settings:
-Slim Hardware key rebinding
-Long-press/double-tap actions
-Volume rocker​On the Go mode
Screenshot Crop & Share
Fully charged notification and toggle
CPU info overlay (Developer options)
Snap camera (Sultan's)
More to come, we are never done...
CHANGELOG
WARNING!
This is a Virtually Repartitioned ROM!
What this means is that you will need to take some special steps to flash this ROM. Don't worry, it's not that hard, and you will be able to return to stock with Odin at any time. The cool thing is that it will support a ton of apps and app data storage and will behave like a more modern device (but still has the inherent hardware limitations).
The basic idea with virtual repartitioning is that the partitions are renumbered from the stock numbering, but not resized. So the most important parts of this are (as an FYI, you don't need to know this ):
-The 2GB /data partition becomes a most adequate 2GB /system partition for the ROM and GApps.
-The 12GB Internal SD partition becomes /data, so you have that space to install apps.
It is strongly recommended to use an External SD card to store the ROM/flashing files and for backups, etc., however it is not mandatory. If you do not have an External SD and you need to format the /data and /Internal storage partitions, you will have to copy the files you need from your PC again. Easy peasy, right?
FAQ/NOTES:
When formatting the device, first go to the Mount menu and make sure none of the partitions you want to format are mounted. If they are, formatting will fail.
Make sure you have NOT selected Mount USB Storage, and that the MTP button says "Enable MTP", which means it is DISABLED. If either of these are enabled, then formatting may fail.
The /system partition is formatted as EXT4.
The /data and /cache partitions can be formatted as either EXT4 or F2FS.
The Internal Storage should be formatted as EXT4 or F2FS.
The External SD card (if you have one) would be best formatted as FAT, which you can do in your computer. When the ROM boots, it will detect the card and offer you one of two different ways to use it, as "Internal storage" that will only work with your device for security (requires formatting and encryption by Android), or as "Portable storage" that will work in other devices.
CAUTION: With Internal, you will have to entirely format your card if you have issues and it can not be used in ANY other device. In fact, it will become invisible in file managers because it becomes an extension to the Internal SD card storage. Format the ExternalSD card to Internal Format at your own risk.
When formatting /data, the default behavior is that /data/media is not deleted. In order to wipe /data/media, you need to either go to TWRP > Wipe > Advanced wipe > Format data, or delete the folder manually through the file manager in TWRP.
TWRP > Wipe > Advanced wipe > Format data is also needed if you plan to use device encryption, because this step allows for a space at the end of /data to contain the encryption information. Without this, encryption will fail!
IMPORTANT: If you have flashed a modified PIT file, flash back the STOCK PIT. You can also return to stock by using Odin and a Factory Image.
If you are trying to get back to the stock partitioning:
Flash a stock TWRP recovery ZIP or IMG file, or use Odin to push a TAR recovery over. After doing this you need to reboot your device into Recovery to load up the newly flashed version, and format each of the partitions to their defaults (ext4, for the most part). If you encounter errors formatting, reboot back into Recovery and try again.
Check SamMobile.com for stock ROM packages. (There is a Stock ROM version in my AFH account which should be used for recovery purposes only.) Odin should also find the device if it's in download mode and you can flash a stock ROM back on it if you want.
If you are not sure you used the correct recovery or you just want to check the partition structure (I may ask for this), you can run each of these commands from an adb prompt, and save the output to a file for linking in the thread for help/analysis:
blkid
cat /proc/mounts
df
INSTALLATION STEPS:
Here is what you need to do; please follow the below steps carefully!
Connect your device to your computer and FULLY BACK UP YOUR FILES from both your Internal and External Storage!
While you are backing up your files, download the following files to your computer:
A custom TWRP recovery for virtually partitioned ROMs (see Post 2).
The ROM zip file (see Post 2).
A 6.0 Gapps package, pico recommended for now. (optional - see Post 2).
Copy all of these files to your device's External SD card. If you don't have an External SD card, then you will need to copy them over from your computer after formatting your internal storage.
MAKE A NANDROID BACKUP!
Using your EXISTING RECOVERY, format /system, /data, /cache and /Internal Storage.
Flash a VIRTUAL REPARTITIONED RECOVERY.
REBOOT to Recovery to use the new one.
Select Wipe > Advanced Wipe > System, then press the "Repair or change file system" button. Choose "Change File System" and select EXT4. Swipe to apply.
Press the back button and verify the Size: and Free: values at the top. The System partition should be 2GB. Press the Repair button and swipe to apply.
For good measure, now press the Resize button and swipe to apply.
Repeat steps 1-3 for the Data partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Repeat steps 1-3 for the Cache partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Reboot to Recovery and wipe /system again.
Flash the CandySiX zip
Flash Gapps (nano or pico Open GApps or BaNks ones, etc.). You may have to experiment a little.
Reboot and Enjoy
Please give first boot a good several minutes. If you get stuck at the boot animation for a long time, try removing your ExternalSD card and reboot without it.
IMPORTANT - PROBLEMS/ISSUES:
If you have issues, I need the following:
Logs from you (logcat, last_kmsg, dmesg) linked to on pastebin.com or hasteb.in, showing the failure.
A clear description of the steps that I need to take to exactly reproduce the problem.
State what flavor build you are on: CMTE, Layers, OMS, etc...
Please DO NOT complain about problems and offer nothing to help fix it. I reserve the right to ignore you for not following insructions...
NO ETA REQUESTS!
Special thanks to @gimmeitorilltell, @bryan2894, CyanogenMod, SlimRoms, Omni and all the rest who make their source open, we can't do this on our own.
XDA:DevDB Information
[ROM-DISCONTINUED][SGH-I727][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Skyrocket, ROM for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
NoSpamDan, gimmeitorilltell
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.2
Stable Release Date: 2016-02-11
Created 2016-01-01
Last Updated 2017-01-05

Downloads
Make sure you have FULLY READ and FULLY UNDERSTAND the OP (Post 1) above before following any steps!
RECOVERY
BaNks just announced they aren't supporting TWRP versions below 3.0.
@bryan2894 has a Flashable 3.Xversion you can flash here:
https://androidfilehost.com/?fid=24545070682210374
(My previous TWRP 2.8.7.0 for Virtual Partitioned ROMs: TWRP_2.8.7.0.VP_skyrocket_NSD.zip)
Be careful, because "official versions" of TWRP for the Skyrocket may not be compatible with Virtually Partitioned ROMs.
TWO ROM VERSIONS: Effective 26July2016, choose from CMTE or OMS/Substratum!
(You can NOT flash one on top of the other... If you decide to switch and try the other one, you MUST Clean Flash!)
DOWNLOAD CMTE (CM Theme Engine based) ROM:
CandySiX-celox-3.2-OFFICIAL-0910.zip
DOWNLOAD OMS/Substratum themed ROM (Substratum app required - Guide to using Substratum):
CandySiX-celox-3.2.S-OFFICIAL-0910.zip
GAPPS
"Normal" BaNks Dynamic GApps
Open GApps
Your best bet is to flash a Pico GApps package made for Android Marshmallow which doesn't have an included keyboard or any keyboard modifications. Watch out for GApps that replace Gallery too!
EXTRAS
- If you want to remove the built-in SuperSU, flash this in recovery after the ROM: SuperSU_Root_Remover.zip
Previous ROM versions for convenience (can be found on my AFH account unless they are OTAs).
DO NOT FLASH a CMTE ROM on top of an OMS or LAYERS version. You must CLEAN FLASH if switching theme engines!
OMS/Substratum-based:
CandySiX-celox-3.2.S-OFFICIAL-0910.zip
CandySiX-celox-3.2.S-OFFICIAL-0902.zip
CandySiX-celox-3.2.S-OFFICIAL-0817.zip
CandySiX-celox-3.2.S-OFFICIAL-0808.zip
CMTE-based:
CandySiX-celox-3.2-OFFICIAL-0903.zip
CandySiX-celox-3.2-OFFICIAL-0817.zip
CandySiX-celox-3.2-OFFICIAL-0809.zip
CandySiX-celox-3.2-OFFICIAL-0807.zip
Layers-based (deprecated):
CandySiX-celox-2.3-OFFICIAL-0514.zip
Previous GApps versions can be found on my AFH account here.

Reserved

Let me know how this works out for you folks. I still need Mobile Data tested and please remember it's Alpha right now, so I need logs when things aren't working.

Some Logs for bug fixing
Unable to test mobile data atm since it seems to not recognize the sim card that was working on a lollipop rom before flashing. However while only using this rom, a pico gapps build from open gapps, and a viper4android flashable zip, the stock keyboard seems to be broken with constant messages of android keyboard has stopped. It would seem the libjni_latinimegoogle.so is causing the errors when I breifly looked at the logs. Hopefully these logs I've included can help you in fixing some bugs. Log is in a zip file since the txt is larger than xda allows.

Seguraf13 said:
Unable to test mobile data atm since it seems to not recognize the sim card that was working on a lollipop rom before flashing. However while only using this rom, a pico gapps build from open gapps, and a viper4android flashable zip, the stock keyboard seems to be broken with constant messages of android keyboard has stopped. It would seem the libjni_latinimegoogle.so is causing the errors when I breifly looked at the logs. Hopefully these logs I've included can help you in fixing some bugs. Log is in a zip file since the txt is larger than xda allows.
Click to expand...
Click to collapse
What ROM version are you on? Make sure it's the latest linked in Post 2, and says "OFFICIAL" on it.. I fixed mobile data in that.
If you're not running that one, you can reboot to recovery, wipe system, cache and dalvik, flash the updated OFFICIAL ROM and GApps and should be good.
Edit: Thank you for taking the time to provide a log.

Seguraf13 said:
Unable to test mobile data atm since it seems to not recognize the sim card that was working on a lollipop rom before flashing. However while only using this rom, a pico gapps build from open gapps, and a viper4android flashable zip, the stock keyboard seems to be broken with constant messages of android keyboard has stopped. It would seem the libjni_latinimegoogle.so is causing the errors when I breifly looked at the logs. Hopefully these logs I've included can help you in fixing some bugs. Log is in a zip file since the txt is larger than xda allows.
Click to expand...
Click to collapse
As for the keyboard issue, take those files out of your GApps zip. I used BanKs Dynamic GApps. I think there's something with how our older devices are detected in the new M GApps install scripts and it will be sorted eventually.
By removing these files, you will lose the swipe capability in the AOSP keyboard, but it will still work (no FCs) to log into Google and set everything up. Then just install Google Keyboard and you can have swipe typing back for now.
EDIT: I uploaded a modified BanKs Gapps package (one that I used) and linked it in Post 2...

Saw the thread and download the rom through whatever link I found at the time and got the unofficial one, I'll go download the new one and do some more testing, Thanks for all your work

New ROM version available in Post 2: CandySiX-alpha-skyrocket-OFFICIAL-0102-16.zip
This one has Quick Settings Tile Customization, Status Bar mods, Battery mods... more features to come in the near future!

New build up in Post 2 with working Navigation Bar and some other things - CandySiX-alpha-skyrocket-OFFICIAL-0103-04.zip. Things will be slowing down here shortly once I return to work...

Flashed new build, Calls and sim card works, the new reboot menu is a welcome feature, mobile data doesnt seem to work atm, included logs of me testing out the camera, calling, mobile data on and off, wifi on and off, and attempting to open play store with wifi off
Update: Seems like the bootanimation for me is a bit broken, only shows a black screen during boot then gets to lock screen fine. Also can't seem to properly access the external sd card in es file explorer or install any apks in the system file explorer off the external sd card.

Seguraf13 said:
Flashed new build, Calls and sim card works, the new reboot menu is a welcome feature, mobile data doesnt seem to work atm, included logs of me testing out the camera, calling, mobile data on and off, wifi on and off, and attempting to open play store with wifi off
Update: Seems like the bootanimation for me is a bit broken, only shows a black screen during boot then gets to lock screen fine. Also can't seem to properly access the external sd card in es file explorer or install any apks in the system file explorer off the external sd card.
Click to expand...
Click to collapse
Thanks for the log, I'll take a look at it. In the future, please upload to Pastebin or Hastebin and provide the link here. That way, it will be easier for others to take a look if I need any extra eyes...
Also looking into boot animation, which is indeed broken. You can flash this mod to replace it back with the stock one (found in the downloads section of the OP): M_480px_Stock_BootAni.zip
I need more information about your setup. You flashed Viper4Android and I'm not sure what else yet.
I need to know these things:
You clean flashed this ROM, wiping everything as instructed.
You are using only the stock included kernel.
There are no system mods installed (Viper might be OK, but...).
No data was restored from another ROM.
What carrier you have.
What APN you are using.
What modem you have flashed.
Wi-Fi and mobile data has been tested by myself and others already, and so far works perfectly. Not 100% sure, but it looks like you may have applied a tethering modification...
Did you enable Root (Privacy Guard) in Developer Settings? Move whatever system mods you like in recovery if needed. The ROM also includes native file browsing using System > Storage and USB. You may have to backup and format your ExternalSD card as FAT so Android can detect it and offer to format how it wants. Did it ask you to use the card as Portable or Internal Storage?

NoSpamDan said:
Thanks for the log, I'll take a look at it. In the future, please upload to Pastebin or Hastebin and provide the link here. That way, it will be easier for others to take a look if I need any extra eyes...
Also looking into boot animation, which is indeed broken. You can flash this mod to replace it back with the stock one (found in the downloads section of the OP): M_480px_Stock_BootAni.zip
I need more information about your setup. You flashed Viper4Android and I'm not sure what else yet.
I need to know these things:
You clean flashed this ROM, wiping everything as instructed.
You are using only the stock included kernel.
There are no system mods installed (Viper might be OK, but...).
No data was restored from another ROM.
What carrier you have.
What APN you are using.
What modem you have flashed.
Wi-Fi and mobile data has been tested by myself and others already, and so far works perfectly. Not 100% sure, but it looks like you may have applied a tethering modification...
Did you enable Root (Privacy Guard) in Developer Settings? Move whatever system mods you like in recovery if needed. The ROM also includes native file browsing using System > Storage and USB. You may have to backup and format your ExternalSD card as FAT so Android can detect it and offer to format how it wants. Did it ask you to use the card as Portable or Internal Storage?
Click to expand...
Click to collapse
1. Started out fresh, wiped everything
2. Just using the rom, your modified gapps, and a viper4android package that makes it work on marshmellow: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
3. Just using viper for audio usage
4. All testing done without restoring data
5. [email protected]
6. The stock apn that's enabled by default, havnt touched it, ATT (Phone)
7. The latest one available
8. I enabled root in dev settings for apps and adb
9. As for the external sd card, I formatted it in android but it spat out and error so i formated in windows to fat32, at boot it only gives me the option to explore, haven't seen the option to configure like other marshmellow roms i've tested, would you like a screen recording or some screenshots of the process?

Seguraf13 said:
1. Started out fresh, wiped everything
2. Just using the rom, your modified gapps, and a viper4android package that makes it work on marshmellow: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
3. Just using viper for audio usage
4. All testing done without restoring data
5. [email protected]
6. The stock apn that's enabled by default, havnt touched it, ATT (Phone)
7. The latest one available
8. I enabled root in dev settings for apps and adb
9. As for the external sd card, I formatted it in android but it spat out and error so i formated in windows to fat32, at boot it only gives me the option to explore, haven't seen the option to configure like other marshmellow roms i've tested, would you like a screen recording or some screenshots of the process?
Click to expand...
Click to collapse
Thanks for the feedback. If you can get both a logcat and a kernel dmesg log while trying to format and/or write to the ExternalSD it would be helpful.

Is doze built into this?

zappa41 said:
Is doze built into this?
Click to expand...
Click to collapse
Ambient Display is, but maybe not all configuration options are there... yet.

OK cool. Other than that, the rom is smooth. Good work!
Sent from my SGH-I727 using Tapatalk

New build with more features is in Post 2: CandySiX-alpha-skyrocket-OFFICIAL-0105-05.zip
Sorry, no time to outline the changes but should have Quick Unlock, new boot animation and several other updates...
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024

Testing it today, first I formated /cache and /data using F2FS and take a long time to install, after rom boot have to reboot when trying to call just got freezed, go back to TWRP 2.8.6.0 and format internal to vfat, /cache /data and /system to EXT4 (not sure if that is default format or if ODIN can change it), reinstal the new recovery to virtual repartition again and format this time in EXT4 and just go fine faster install no frezze at call and smooth.
NoSpamDan said:
The External SD card (if you have one) would be best formatted as FAT, which you can do in your computer. When the ROM boots, it will detect the card and offer you one of two different ways to use it, as internal storage that will only work with your device for security (requires formatting by Android), or as external storage that will work in other devices. It's your choice.
Click to expand...
Click to collapse
ROM boots but don't give me a choise to select how to use the sd only got acces through explorer built in, another one don't recognizes any card, maybe I do something wrong?

I got this successfully installed last night as well. I formatted all three (system, data, and cache) as ext4, and was pleased that everything came up with no issue.
I will say that I didn't get a choice on how to use the external SD card either. It is showing up, and I get a notification about it, but it doesn't appear to be mounted as an MTP device. I can (especially now that /data is huge) copy new zips to there and then move them, but it would be nice to have the SD card available via USB.
Also, I have noticed a tremendous amount of lag in the keyboard. I did switch to Swiftkey right before putting the device down, so I'll reevaluate tonight. Otherwise, it's looking pretty good, especially on such geriatric hardware.
Update: I noted that auto-rotate seems to not be working. I tried it in several apps, and it seems stuck in portrait.