{
"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 an FAQ/tips/troubleshooting thread for the CM9 ICS AOSP ROM being developed by epsylon and quarx. Many thanks to the devs for spending time and effort to bring us ICS goodness. Defy devs totally rock, we have a stable working ROM within weeks of the drop. If you can, donate a few bucks to the devs for their work and to encourage them (donate links and details at the end of this post).
Do not post bug reports here - use this thread for it instead.
GUIDELINES:
Know fully well what you are doing: this is a pre-alpha ROM, very early, and does not include much of device-specific optimizations. It might be buggy, battery life might not be great, there may be broken apps and random force-closes. If you are comfortable (or excited to) handle all the above, proceed. Else, wait for a more stable beta or RC version of ICS before trying it out.
Start with a full battery charge.
Some things might be referred to, without being given proper explanation. I expect that you know them already. If not, use either XDA search bar on top or use Google. This is because including explanations for everything will make this FAQ lengthy and less readable.
If you are completely new to custom ROMs, rooting etc, read up and educate yourselves(I did 3-4 days of reading before I even got my Defy!) well so you don't make costly mistakes. Links are provided at the end of the post.
And of course, the standard disclaimer applies: the ROM developers, me and others on this thread are not responsible if you brick or damage your phone. All steps will be posted after personally testing, though, so if you follow them properly, you will be fine.
STEPS TO INSTALL ICS/CM9:
Prerequisites: Defy, rooted and with 2nd init installed.
Backup your apps using Titanium Backup, Root Explorer, Astro File Manager or similar (to restore to the ICS ROM you will flash).
Get the latest CM9 zip file (links at the end of this post).
Copy into your SD card.
Disable USB debugging.
Reboot into recovery (switch on the phone and hit volume - button when the LED turns blue; CM7 and similar custom ROM users can press and hold power, select recovery).
Make a backup of your current ROM.
Do a factory reset/wipe data, then install the CM9 zip file.
Immediately after, flash this 2.3 kernel zip.
Flash GApps zip file.
Clear Dalvik Cache (this is IMPORTANT!).
Reboot. It takes some time for Dalvik Cache to be built, be patient.
While it is possible to flash CM9 on top of CM7, many users have reported hangups and slowdowns. Also, this is a pre-alpha (very early!) build, so do not take any chances, do a fresh install.
STEPS TO UPDATE ICS NIGHTLY:
If you flashed CM9 already, and want to update to a newer nightly (which comes out almost daily), follow these steps:
Download and copy the CM9 zip file to your SD card.
Ensure that USB debugging is disabled.
Reboot and enter recovery.
Wipe cache(NOT wipe data/factory reset).
Go to advanced > wipe dalvik cache.
Install the CM9 zip file in your SD card.
Reboot.
Note: Some newer nightlies might be less stable than the previous one, for example, I found 08/12 to be more stable than 09/12, and had to go back to 09/12. Keep this in mind when updating.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Q: I installed ICS. How do I go back to stock 2.2/2.3 OR CM7 or other custom ROM?
Use either a full sbf of stock rom (flash with rsdlite) or a fixed SBF+nandroid backup to go back to stock. Wipe data, flash the fixed SBF from recovery, then restore its corresponding nandroid. Now, clear dalvik cache and reboot.
For CM7, wipe data, install CM7 zip file (which must be copied to SD before booting to recovery), then restore the nandroid that you have. Wipe dalvik cache and reboot.
If you do not have a nandroid backup, and/or use other software like Titanium Backup, flash the stock or custom ROM, clear dalvik cache, then reboot and restore using the specific app.
Q: Syncing does not work.
Reflash Gapps in recoveryy.
Q: I see only a Defy+ zip file in the download server, is it safe to use it on Defy too?
Yes, the 'Defy+' in the filename merely indicates that it should be used with the Defy+ GB kernel. It can be used safely with both Defy and Defy+.
Downloads:
Cyanogenmod 9 ICS builds
GApps zip file (for builds 20/12 and newer)
GApps zip file (for builds 13/12 and older)
CM9 2.3 kernel
CM7 2.2 kernel (to go back to Froyo etc. if you need)
Useful links:
Understanding Android mods: rooting, custom ROMs etc. (also included on the page are instructions for rooting, and unbricking Defy, among other things).
Donate:
All the hard work is being done by the devs, Epsylon and quarx, and they deserve any donation you can make.. If you can donate, send them a few bucks, it helps encourage them, and is a small reward for the CM9 goodness they are bringing to our beloved Defys.
Epsylon3:
PayPal: [email protected]
http://forum.xda-developers.com/donatetome.php?u=803131
Quarx:
Moneybookers: [email protected]
WebMoney: USD:Z319203344726
Yandex money: 4100188263979
If you found this thread useful, please consider hitting the thanks button. Of course, it does not hurt if you donate to me any spare change left over after donating to devs
Suggestions for improvement, critique, new questions and tips are always welcome.
Nice!
Add this...
If user is having problem with Google sync,Calender sync...just reflash gapos.zip
Sent from my MB526 using xda premium
cant we flash full sbf
you just mentioned fixed sbf...
@nogoodusername: thanks, and I will add your tip.
@maxxxxx: yes, you can flash full sbf of your stock rom, I w go back toill add that. Though I reckon most won't go back to stock, but cm7 or the like!
u have mentioned that we are supposed to flash 2.3's kernel, u mean we have to flash it on our defy and not defy+ [although after thinking about it i feel stupid asking this coz why would you flash 2.3's kernel on 2.3, but still asking coz i dun wana end up doing something foolish]...or do u mean we have to flash the kernal ONLY if we use 08/12 or newer cm?
thanks for the help..
@abysstheking: Thanks for reminding me of that, I've edited the question to make it clear about Defy+.
I have Defy green lens. As I can install CM9? So that, 2init?Please details more the process for not expert users as I. Many thanks again.
Cool thread, nice and simple
Camera won't work
manoloto said:
I have Defy green lens. As I can install CM9? So that, 2init?Please details more the process for not expert users as I. Many thanks again.
Click to expand...
Click to collapse
Your camera will not work, everything else would work fine. This is an early build, devs are trying to make green lens camera work. They will get it done sooner or later, like they did on CM7.
very useful....thx
which one to download ?
Nightly Server (EU/FR)
Nightly Mirror & ICS (EU/RO)
Nightly Mirror & ICS (EU/LT)
ICS Nightly Mirror (AM/BR)
Grab the latest build from the last link.
Hope i didnt birck my phone completely
First: the ics builds were...
lets say...
AAWWEEESSOMMEEE...
Second:
My Problem:
Tried to get back to cm7 with a nand backup.
didn't work out, so stupid me restored the boot.img, caused a bootloop...
now i'm not able to get my phone to start.
this is horrible...
hope i'll find a way...
maybe you could help me...
Read the post carefully, the first Q answers precisely what you are looking for. You need to flash the cm7 kernel and reboot, it should work fine.
ICS
When will be the Stable Ics Cm9 RElease date and when will be the camera works
flashed successfully
but no options to import contacts from SIM CARD
yeah camera doesn't work but who need it
my girlfriend will eat my ear ,if i flash a buggy rom
anyway ,thank you
esok44 said:
First: the ics builds were...
lets say...
AAWWEEESSOMMEEE...
Second:
My Problem:
Tried to get back to cm7 with a nand backup.
didn't work out, so stupid me restored the boot.img, caused a bootloop...
now i'm not able to get my phone to start.
this is horrible...
hope i'll find a way...
maybe you could help me...
Click to expand...
Click to collapse
use rsd lite and go back to froyo....
erics_lu said:
my girlfriend will eat my ear ,if i flash a buggy rom
anyway ,thank you
Click to expand...
Click to collapse
Then ask her to buy a new phone
Hi to all.. Currently i am on defy+ 2.3.4 nandroid backup walter79 ROM - and would like to install CM9 seeing that everything apart from the camera works..
also i currently do not have internet access.. so reinstalling the bootmenu will not be possible.
so::
1- do i just enter 2init,wipe data, clear cache and dalvik and flash 2.3 kernel?
2- do i flash froyo ,root and then step 1?
3- is there anything else which i have to do??
4-will i be on defy+ and no chance of downgrade if i install CM9 ??
Pl help i really want to get on CM9..
thanks again
Related
Credits for: Cotulla, M-deejay, tytung, dandiest, darkstone 1337, crawlingcity
Click to expand...
Click to collapse
Thanks: M-deejay, Dandiest, tytung, womo, Erkin Ay, cao thanh hai, chucky, MrbrOTP2, Ancola66, Vdakov, codecinqueror, robert Neri, chappy, Clauswl, dioxda2, Dungphp, Sklar, Badbullet, BerreZ
Click to expand...
Click to collapse
Post 1: Galaxy S Ginger CM7 V2 (19.July)
Post 2: Galaxy S MIUI V2 (14.May)
Click to expand...
Click to collapse
BOYPPC-SHIFTPDA GALAXY S GINGER 2.3.4 CM7 HoneyComB
BOYPPC-SHIFTPDA GINGER 2.3.4 CM7 Sense.s
{
"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"
}
BOYPPC-SHIFTPDA GINGER 2.3.4 CM7 HoneyComB
BOYPPC-SHIFTPDA GINGER 2.3.4 CM7 Go EX
Rom for GT-I9000, Flash rom by recovery
http://ul.to/folder/2y8pqk
How to install Rom
1 download and copy rom to phone
2 root phone by GalaxyS_One-Click_Root_All_Models
3 Flash cm7-galaxys-initial-kernel.tar by Odin
4 Flash boyppc-shiftpda rom by Recovery
Click to expand...
Click to collapse
Features:
Custom apps, honeycomb themes, honey comb livewallpaper, new market for android 2.3.4, new file manager, nemo music, ll apps included that come stock with CM7, 3G / Data, Audio,
Bluetooth, GPS, Wi-Fi, Phone, Camera (5MP), Camcorder (800x480), 720P video playback, -Hosts file to stop most web ads, FM Radio, New Market, USB File Transfer, -ADW Launcher, LED Notification, CyanogenMod CPU Performance Menu.
Click to expand...
Click to collapse
base and App: stock rom CM7
Mod: honeyComB lock screen, flip animation, boot animation, fix system.
Add app: MIUI music, task manager, qick office, yahoo mail and chat, root explorer, HoneycomB themes, coloriza widget, GL 3D weather clock widget.
Click to expand...
Click to collapse
Change log
V2 (19.July) update CM7 base 59, add MIUI camera, fix system.
Click to expand...
Click to collapse
Old rom
Click to expand...
Click to collapse
[14.May] BOYPPC-SHIFTPDA GALAXY S MIUI 1.5.6_GINGER 2.3.4
BOYPPC-SHIFTPDA GALAXY S MIUI 1.5.6_GINGER 2.3.4 V2 (14.may)
Rom for Galaxy S GT-I9000. flash rom by recovery mode
http://ul.to/folder/241yy2
How to install Rom
1 download and copy rom to phone
2 root phone by GalaxyS_One-Click_Root_All_Models
3 Flash cm7-galaxys-initial-kernel.tar by Odin
4 Flash boyppc-shiftpda rom by Recovery
Click to expand...
Click to collapse
Base rom and App: MIUI 1.5.6 Ginger 2.3.4
Language: WWE
Mod: Lock screen, Flip Animations, mod DefaultThemes honeycomB style, add hy5.8 & Hive V0.3 themes.
Add App: Facebook, twitter, yahoo mai & yahoo chat, quick office, Spare parts.
Click to expand...
Click to collapse
Change log
V2 Fix boot, fix power menu, add new boot animation, add honeycomb live waalpaper. remove Facebook, twitter, yahoo mai & yahoo chat, quick office, Spare parts (you can download from market)
Click to expand...
Click to collapse
Thank to deadey3
Make sure you have the pc drivers for you phone (download kies, thats about all its good for...make sure its closed when following the instruction below)
1. Factory Reset
2. Pull battery out, replace
3. Get into download mode, 3 button combo
4. Open odin
5. Put stock froyo files in odin (from samfirmware.com) I use JPU froyo rom !
6. Tick repartion
7. Plug in USB cable (yellow sign saying added)
8. Hit start
9. wait till phone reboots..
10. Shutdown phone
11. Get into download mode again
12. Open odin
13 Put speedmod kernel file in odin (froyo speedmod !) Put the file in PDA and UNTICK auto reboot and repartion...Important..
14. Hit start
14. Pull USB cable out after flash....should say reset in Odin
15. Use 3 button combo to get into recovery (no need to pull battery)
16. Flash galaxys-efsbackup.zip
17. Pull battery
18. Get into download mode
19. Open odin and put cm7-galaxys-initial-kernel into PDA, again UNTICK repartion and auto reboot.
20. Pull out USB and get into recovery....(DO NOT PULL BATTERY OUT TO DO THIS)
21. Flash MIUI/Cyanogen ROM
22. Get into download mode again
23. Open odin and put cm7-galaxys-initial-kernel into PDA, again UNTICK repartion and auto reboot.
24. Pull out USB and get into recovery....(DO NOT PULL BATTERY OUT TO DO THIS)
25. Go under "mounts & storage" and format /system, /cache, /data, /datadata.
26. Flash GalaxySense ROM
27. After first flash and boot and intial setup always reboot your phone.
Thank to Kaik541 (for CM7)
Q: Which devices does CyanogenMod support from the SGS family of phones?
A: The supported devices are only the GSM variants, including the international I9000, I9000M, I9000T, Captivate (SGH-I897 and SGH-I896), and Vibrant (SGH-T959). If your model number is NOT one of the above phones, including I9000B, Fascinate 3G+ (SGH-T959D), and Vibrant 4G (SGH-T959V), then your device is not supported and these builds will not work on your phones. Please do not attempt to flash any builds as we cannot guarantee that it won't potentially turn your phone into a brick. Look on the wiki for a more complete list of supported and unsupported devices.
Q: How do I root my phone?
A: Please follow the instructions available on the wiki.
Q: How do I install/update CyanogenMod 7 on my Samsung Galaxy S?
A: As we have no stable builds, every nightly comes with the risk that it will not install, will not boot, or will not scratch your eyes out in your sleep. Until a stable build arises, the best chance of getting CyanogenMod is download the latest nightly from the buildfarm, place it on your internal SD card and install through ClockworkMod Recovery (you do not need to use ROM Manager and you will have ClockworkMod Recovery through the root process listed above).
Q: I'm about to update to the latest nightly, what can I expect?
A: Every nightly will likely come with several changes which can be tracked here. Before updating, it is considered a good idea to backup your last known, good configuration. The process for booting into recovery and creating a nandroid backup is covered on the wiki. You are then free to install the latest nightly.
Q: I have installed the latest nightly, but my phone never finishes booting, what do I do?
A: Nightlies come with the expressed possibility that they may not work. If you encounter this, please reboot into ClockworkMod Recovery and restore your last known, good nandroid backup.
Q: How do I restore a nandroid backup if the phone doesn't boot properly?
A: Boot into recovery mode and then follow the instructions from the wiki. Once it's complete, reboot your phone and you should be back to where you were before you attempt to install.
Q: After installing CyanogenMod, I don't have the Android Market or GMail applications, how do I get those on my phone?
A: CyanogenMod does not ship with Google's proprietary apps due to a licensing issue. The latest version of the Google Apps can be found here. Place the zip on your internal SD card and install with ClockworkMod Recovery.
Q: I don't like the default radio that ships with CyanogenMod, where can I find a replacement modem?
A: More modems can be found here. Place the corresponding zip on the SD card and install with ClockworkMod Recovery.
Q: What are some tips for preserving battery life on this ROM?
A: 3G seems to be one of the larger battery drainers, as well as GPS, bluetooth, and wifi. Disabling these will help your battery get through the day.
Q: I tried to disable 3G but the phone enters a loop of force closes that make the phone unusable, how do I fix or prevent this?
A: Because of a bug in the 2G/3G toggle code, this isn't possible without first disabling any active data connections and then enabling them after toggling 2G/3G. If the phone is already force closing, the quickest way to fix it is by performing a factory reset from recovery (you will lose all your apps and settings, unfortunately).
Q: When will third party features like "Voodoo Sound" and "Voodoo Color" be integrated into the kernel?
A: The Voodoo Control App is now compatible with the stock kernel and appears as sound driver version 9. Voodoo color will not be merged, but more pleasing color temperatures have been added to the stock kernel.
Q: I don't like the softkeys along the bottom lighting up whenever I have a notificiation (aka LED notifications), how do I disable them?
A: Open Settings, CyanogenMod settings, Interface, LED notifications, Miscellaneous, and then select the apps you want to disable LED notifications for and select "None" as the flash color option.
NOTE: This has been disabled on any nightlies after nightly 15, until a more favorable global solution can be found, as we do not have an RGB notification LED and just a simple on/off LED.
Q: I think I found a bug, how do I report it?
A: Short answer, you don't. Because we have no stable builds, we run what are called nightlies. Bug reporting for CyanogenMod does not allow the reporting of bugs on nightlies as they are considered unstable at best (and phone destroying at worst). Basically, you will "have to live with it" until we have a stable build.
Q: I see a lot of people running different themes, where can I get these?
A: CyanogenMod ships with the T-Mobile Theme Engine integrated, search the Android Market for "theme engine" or browse the forums for themes. Install the application and run the "Theme Chooser" application and select the theme you'd like. Reboot the phone to fully apply the theme.
Q: I miss the video player/music player/contacts/phone/launcher application from Samsung ROM's, how can I install these?
A: You cannot. Many (if not all) of those applications have specific hooks into Samsung's framework which do not exist on this ROM. There are plenty of market alternatives available.
Q: I want to go back to another ROM, but when I try to restore a nandroid backup of another ROM, it doesn't boot... what did I do wrong?
A: Because this ROM is set up to use the MTD partition layout instead of Samsung's BML partition layout, you must use ODIN or heimdall with a full firmware including a PIT file and repartition.
Q: Why can't I see the latest nightlies on ROM Manager? Will I always have to download manually to install updates?
A: Access to nightlies requires a ROM Manager premium license for the convenience (you should consider buying the license anyway, as Koush had a strong hand in helping us merge to mainline). These are the same files from the link earlier, ROM Manager is just a convenience. Once a stable release is available, you can download without a premium license from the "stable" section. Be sure to update ROM manager to say your recovery is Galaxy S (MTD) with ClockworkMod 3.x (it will give you a warning about it not being supported, ignore it and say ok) and then reboot your phone. Check under "Download ROMs" and the nightlies should appear.
Q: The phone turns on whenever I plug it in, is there any way to prevent this?
A: For now, unfortunately, no. Low power mode isn't supported in the kernel right now, and may be implemented in future builds.
Q: How do I get GTalk to work with the Front Facing Camera?
A: Video chat requires a specific version of GTalk which is only available in a Google Apps package with a date of 05032011 and later. This version of Google Apps is not shareable through the mirror system as it only works on neon boards (aka Galaxy S/Nexus S). A quick google search will yield the results you need.
Q: How do I enter download mode?
A: The use of the "adb reboot download" command isn't functional yet. The only method to enter download mode right now the standard "three finger salute" (or a USB jig).
Q: I inserted my external SD card and CyanogenMod tells me the card is damaged or corrupt and needs to be formatted, what should I do?
A: Some cards (especially 16 GB and larger) seem to be behaving oddly and are incompatible with the current builds. Please try another card and be careful formatting through android. Android/CM7 is hard-wired to think there is only ever one SD card and may actually format your internal SD card, this will hopefully be resolved sooner rather than later.
NOTE: This should be fixed by nightly 15 and later.
Q: I can't seem to find the files from the external SD card on /mnt/sdcard/external_sd, where are they located?
A: Because of how we have implemented it, the external SD card is located at /mnt/emmc now. This allows it to still be scanned by the Media Scanner.
Q: Where can I get the Nexus S drivers for use with adb? (Windows Only)
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK.
Q: Do I really need to be on Froyo to install this ROM?
Q: I'm already on Gingerbread from Samsung, why do I have to downgrade before installing?
A: Samsung included new bootloaders in the Gingerbread updates that are incompatible with CyanogenMod 7. They break a number of things including, but not limited to, graphical distortion at boot time and broken external SD card. To fix this would require reworking the entire kernel to be based off of Samsung's code drop instead of the far more open (and better written) Nexus S source code. If you don't like it, complain to Samsung for introducing new bootloaders.
Q: I have a Bell Vibrant (I9000M), where can I find modems that support my radio frequencies?
A: The Captivate and the Bell Vibrant use the same radio frequencies, as well as several other Galaxy S devices, and therefore any modem designed to work with the Captivate will work with the I9000M. All of the Captivate modems available here should work without any issues (with the exception of KB1, which should not be used except on a Captivate for a number of reasons--in short, it is broken and only there for people with a hardware defect that does not exist in the I9000M).
some app for Android
well this looks interesting!
hmmmmm it is
@ boyppc
its nice to you on Galaxy S forum
I have always loved your work on HTC HD2 Forum
THANKS a lot for the ROMs
Cheers
boyppc-shiftpda galaxy MIUI V2 update
i couldn't download with both your links !!
now it's ok
but what is the diffrence between tow links in miui v2 ? clean ?
prerequisites
I am on doc kitchen ROM version 2.3.3 xxjvk. To install your MIUI ROM on galaxy S do I need to flash a different firmware first or just install it through recovery?
if only this can play divx encoded mkv files, i would definitely use this rom.
thanks though.... looks awesome!
First of all...Wow. Just from the screenshots I am inpressed.
I have been looking for a customized CM7 and hopefully your Rom is the answer to my quest.
One other thing I noticed while having a quick look. You say that FM is working in your features? If this is based on CM7 then this is one huge step forward for the people asking for it (I never use it myself so...).
Downloading the CM7 version and will give both of them a try.
K.
OMG mennn this rom is really really da bomb, i've been using it for a few hours and nothing but respect for you!!!! Thank you very much
I hope this thread get a lot of interest cuz the work looks good thanks dev!
Sent from my GT-I9000 using XDA Premium App
sir ahmed said:
now it's ok
but what is the diffrence between tow links in miui v2 ? clean ?
Click to expand...
Click to collapse
miui Clean remove some App
Nice !
but flash in recovery ?
exelent work m8,also flashable under CWR
awesome job
I will try it now
kar200 said:
First of all...Wow. Just from the screenshots I am inpressed.
I have been looking for a customized CM7 and hopefully your Rom is the answer to my quest.
One other thing I noticed while having a quick look. You say that FM is working in your features? If this is based on CM7 then this is one huge step forward for the people asking for it (I never use it myself so...).
Downloading the CM7 version and will give both of them a try.
K.
Click to expand...
Click to collapse
yeah,
I'm interested in this, too
does FM radio work ?
if yes, please contribute back & work with the devs to get this working on CM7, too
Frequently Asked Questions
CyanogenMod 10
Android 4.1.2 Jelly Bean for Motorola Defy and Defy+
The FAQ has been updated with some information about the 2nd Boot builds with custom kernel thanks to the collaboration of the user sa3e1 who rewrte some parts of the FAQ. If you have any suggestions, corrections or some information to add, please send me an MP. For more information about JB please visit the Motorola Defy Wiki With JB Status
Click to expand...
Click to collapse
Before doing anything:
►Always start the procedures with 80% - full charge battery (if your battery die during the process, you can still go Mcgyver)
►Make a backup of your apk's (using Titanium Backup for example) and a nandroid backup from recovery.
►If you have any problem, don't blame CyanogenMod Team, Quarx, Epsylon3, the FAQ or whatever. This ROM works (except the known bugs), if it's not working for you, it's mostly because you used wrong versions or are doing something wrong.
► INDEX
- Where can I download all that I need?
- NEW What builds are "2ndBoot"?
- NEW Is this ROM for Defy or Defy+?
- NEW I don't have CM10 and I want to install it, how can I do that?
- NEW I already have CM10 and I want to upgrade to a newer nightly, how can I do that?
- NEW Is this ROM stable and ready for daily use?
- NEW What's the difference between Quarx and Epsylon3 versions?
- Can I flash an Epsylon3's build over a Quarx's one without wiping data?
- What is HWA? Is this a good thing?
- So, CM10 have HWA? How can I enable it?
- I'm on CM10 and a lot of apps give me FC and don't work properly
- Why Google Now doesn't work for me? Why I just get regular google search?
- Why are some apps duplicated?
- Why can I use Defy+ (MB526) builds on Defy (MB525) with red lense and what are the advantages?
- I lose my data connection every time, is this error related to this rom?
- I've just installed a new rom, and my battery indicator suddenly drops, is this a bug? Do I have to re calibrate it?
- How can I overclock and undervolt my Defy? And what are the advantages?
- I have problems with WiFi connections, my network get disconnected.
- NEW How can I change the DPI and keep play store compatibility?
► Where can I download all that I need?
Download Link (Quarx's builds) | Mirror | Official Thread
Download Link (Epsylon3's builds) | Mirror
Kernels | Battery Fix for red lens | New Battery Fix | Gapps (Use the last gapps-jb-2012XXXX-signed.zip)
► What builds are "2ndBoot"?
24.09 builds and before ► Normal Builds
10.10 builds and after ► 2ndBoot Builds
► Is this ROM for Defy (MB525) or Defy+ (MB526)?
For 2ndBoot Builds:
Both, since Quarx’s "2nd boot” builds we have a universal build with custom kernel supporting all Defy variants (Defy Green Lens, Defy Red Lens and Defy+). This means that the same .zip file works on the Defy green lens, Defy red lens and Defy+.
For PRE 2ndBoot Builds:
Defy Green Lens ► Froyo Kernel ► CM10-2012XXXX-NIGHTLY-mb525.zip
Defy Red Lens ► Gingerbread Kernel ► CM10-2012XXXX-NIGHTLY-mb526.zip
Defy+ ► No Kernel Needed ► CM10-2012XXXX-NIGHTLY-mb526.zip
Don't know if you got green or red lens? Click here.
► I don't have CM10 and I want to install it, how can I do that?
Pre-steps:
► Your phone has to be roooted.
► If this is the first time you install a custom rom (if you have stock froyo) you'll have to root your phone, install 2nd init (custom recovery), and some other things.
If you aren't familiar with this concepts, these posts will be useful for you:
All-in-One Defy Beginner's guide
FAQ | Guides |Tutorials for Defy
[FAQ] Cyanogenmod 7 by Quarx
► Download all the files that you need and put them on the sdcard.
► Charge your phone until you have 80-100% battery.
► Make a backup of your apps and a nandroid backup of your rom (everything you have on your phone will be deleted).
For 2nd Boot Builds
1) Go to Custom Recovery.
2) Wipe data/factory reset, wipe Cache and go to Advanced ► Wipe dalvik.
3) Go to install zip from sdcard ► Choose zip from sd card.
4) Flash CM10-********-NIGHTLY-mb526.zip
4b) Install kernel update if available (for instance the update_for_11.10_v2.zip for 11.10 nightly)
5) Flash Gapps.
6) Wipe Cache and Dalvik again (recommended).
7) Restart.
Note: Sometimes you'll have to remove the battery and restart the phone.
For MB526 and PRE 2ndBoot Builds
1) Go to Custom Recovery.
2) Wipe data/factory reset, wipe cache and go to advanced ► Wipe dalvik.
3) Go to Install zip from sdcard ► Choose zip from sd card.
4) Flash gb Kernel (JUST FOR DEFY RED LENS USERS).
5) Flash CM10-2012xxxx-NIGHTLY-mb526.zip.
6) Flash Gapps.
7) Flash Battery fix (only for red lens)
8) Wipe Cache and Dalvik again (recommended).
9) Restart.
For MB525 and PRE 2ndBoot Builds
1) Go to Custom Recovery.
2) Wipe data/factory reset, wipe Cache and go to Advanced ► Wipe dalvik.
3) Go to install zip from sdcard ► Choose zip from sd card.
4) Flash froyo kernel
5) Flash CM10-2012xxxx-NIGHTLY-mb525.zip.
6) Flash Gapps.
7) Wipe Cache and Dalvik again (recommended).
8) Restart.
A little FAQ extracted from the Wiki for some 2nd Boot Builds doubts:
Where is the Package for Defy (MB525) ?
From 2ndBoot Release there is only 1 package for both Defy & Defy+.
Do I have to install the Custom Kernel separately ?
No, the Nightly Zip already includes the Custom Kernel, but there might be a newer kernel released without nightly. i.e. there is a never kernel (update_for_11.10_v2.zip for 11.10 build)
Must we change the Boot sequence to 2ndBoot in 2ndInit ?
No, the Upgrade does this for you.
Is a Data Wipe required ?
Only if you are coming from builds other than CM10 (Quarx's). There is no harm in doing a Data Wipe otherwise also.
My phone lags after Boot up.
Its a bug in the Custom Kernel. To solve just turn off Wifi/Internet, Screen Lock & keep idle for a couple of mins.
► I already have CM10 and I want to upgrade to a newer nightly, how can I do that?
Automatic update: (Using Defy ROM Updater)
1) Go to Settings ► About phone ► Additional system updates OR open Defy ROM Updater directly from the app drawer.
2) Tap Check for updates.
3) Select the newer version.
4) Select Start Download.
5) When the download finishes, install it.
Manual update:
1) Go to Recovery
2) Wipe Cache and Dalvik
3) Flash the last .zip file.
4) Flash gapps (just if you have a newer version of gapps, otherwise, this step is optional)
4.1) (ONLY DEFY RED LENS WITH PRE 2ND BOOT BUILDS) Flash battery fix (if you don't, the battery meter will display 1%)
5) Wipe Cache and Dalvik (this is also optional)
6) Restart.
► Is this ROM stable and ready for daily use?
Yes. In fact it's stable as CM7. Make a backup and try it by yourself.
► What's the difference between Quarx and Epsylon3 versions?
The new "2ndBoot” builds with custom kernel are avaible only from Quarx.
There weren’t recent updates from Epsylon lately, so if you want recent updates, and custom kernel improvements use Quarx’s builds.
NOTE: Always use the last version!
► Can I flash an Epsylon3's build over a Quarx's one without wiping data?
Yes, you can. Just follow the steps as if you were upgrading from a previous nightly. I didn't test coming from Eppy's to Quarx. EDIT: You can also flash Quarx builds over an Epsylon one without wiping data.
► What is full HWA? Is this a good thing?
This article explains everything:
"...Contrary to what we’ve always heard, Android has had some hardware acceleration for drawing 2D UI elements since before 1.0. Many of the animations we see every day on Android have been hardware accelerated the whole time. All “window compositing” is done using GPU-based hardware rendering.
Since Android 4.0 we have “full” hardware acceleration. All UI elements in windows, and third-party apps will have access to the GPU for rendering. Android 3.0 had the same system, but now developers will be able to specifically target Android 4.0 with hardware acceleration. Google is encouraging developers to update apps to be fully-compatible with this system by adding the hardware acceleration tag in an app’s manifest.
But hardware accelerated drawing is not all full of win. For example on the PVR drivers of devices like the Nexus S and Galaxy Nexus, simply starting to use OpenGL in a process eats about 8MB of RAM. Given that our process overhead is about 2MB, this is pretty huge. That RAM takes away from other things, such as the number of background processes that can be kept running, potentially slowing down things like app switching..."
► So, CM10 has full HWA? How can I enable it?
Thanks to the work of our developers on CM9, we have full HWA since the first alpha of CM10. HWA is enabled by default on CM10, so you don't have to do anything. However, you can select in which apps you want to enable it, with the HWA Selector, this app is preinstaled in all nightlys and it's easy to use.
► I'm on CM10 and a lot of apps give me FC and don't work properly
Make sure you have done a correct and clean instalation. Try wiping cache and dalvik.
► Why Google Now doesn't work for me? Why I just get regular google search?
That's related to the country you come from
USA ► pictures, knowledge graph, etc.
All the rest ► only normal google answers you also got from the website.
One solution is: In the search app, press Menu ► Go to Settings ► Privacy and accounts ► Search on google.com (activate this) and Location & Google search (deactivate this).
If this doesn't work, set your phone language to English.
► Why are some apps duplicated?
Make sure you flash the lastest Gapps or use a file explorer for root (as Root Explorer), go to system/app and delete duplicated apps (gallery and camera are more common)
► Why can I use Defy+ (MB526) builds on Defy (MB525) with red lense and what are the advantages? thanks to G00fY2
Because Defy+ has same camera as normal Defy with red lense, you can use its Gingerbread kernel and the MB526 builds. With green lense Defy you have to use Froyo kernel and MB525 builds to have working camera. But beside the use of 4 instead of 3 Vsel CPU steps there are no real advantages in using GB kernel. Both are based an 2.6.32.9 Linux kernel. Also you have to install a seperate battery fix, when using Defy+ build with normal Defy, because it has different battery size.
► I lose my data connection every time, is this error related to this rom?
No, it's a common bug related to others roms too. Check this post.
► I've just installed a new rom, and my battery indicator suddenly drops, is this a bug? Do I have to re calibrate it?
That's not a bug. Battery always show wrong percentajes when you flash a new rom. Wiping battery stats will not make any difference.
The solution is simple: You don't have to do anything. Charge your phone to 100% and wait one cicle of charge. Your battery stats will correct automatically. Your system always automatically "wipe" the stats when you charge your phone.
► How can I overclock and undervolt my Defy? And what are the advantages?
You can make your phone faster and your battery last longer. Check this article.
► I have problems with WiFi connections, my network get disconnected.
Make sure you don't have the "Avoid poor connections" option enabled. Go to Settings ►WiFi, press the menu button ►Advanced and uncheck Avoid poor connections.
► How can I change the DPI and keep play store compatibility? NEW
You'll need an file explorer. I recommend Root Explorer
1) Open Root Explorer
2) Go to /system and make sure that in the top says "Mount R/O". That means that the /system is mounted as R/W.
3) Long press on build.prop
4) Open with ► Text Editor
5) Scroll down until you see this line
Code:
ro.sf.lcd_density=240
and change that number for anyone that you want. You can try different numbers, I recommend 220, or 200.
This is how the line should be:
Code:
ro.sf.lcd_density=200
6) Menu ► Save changes.
7) That's it, when you reboot the resolution will be changed.
IMPORTANT: In order to fix the market compatibility, go to stable recovery and flash the right patch. DOWNLOAD
I'll keep updating this thread with your contributions, please feel free to correct me or suggest new questions.
I appreciate your work, but there is a similar thread, started a while ago.
vap_66 said:
I appreciate your work, but there is a similar thread, started a while ago.
Click to expand...
Click to collapse
yes, but the op of that thread just have the instalation instructions. The idea is post here the same questions that are asked over and over in the development thread.
I did this for helping some users, and i'm sure some of them will find this useful.
cdlq456 said:
yes, but the op of that post just have the instalation instructions. The idea is post here the same questions that are asked over and over in the development thread
Click to expand...
Click to collapse
{
"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"
}
Very nice!
Just some corrections:
5) Flash CM9 Kernel (JUST FOR DEFY RED LENS USERS)
5) Flash CM7 Kernel
Click to expand...
Click to collapse
Never flash a kernel after the ROM, Epsylon said this long time ago, because you can revert some changes made in the ROM. You just have to flash the kernel BEFORE the ROM.
- Why are some apps duplicated?
Click to expand...
Click to collapse
This happens when you flash and old version of Gapps, if you flash latest versions this bug is not present.
And something i want to add to the OP:
If you flash this ROM on Multiboot (on your SD card) you WILL experience lag, flash it as main system before come here to complain about that.
Thank you for your work!
mato_d007 said:
Very nice!
Just some corrections:
Never flash a kernel after the ROM, Epsylon said this long time ago, because you can revert some changes made in the ROM. You just have to flash the kernel BEFORE the ROM.
This happens when you flash and old version of Gapps, if you flash latest versions this bug is not present.
And something i want to add to the OP:
If you flash this ROM on Multiboot (on your SD card) you WILL experience lag, flash it as main system before come here to complain about that.
Thank you for your work!
Click to expand...
Click to collapse
Thanks for your help! I'll edit the op in a while
2) Wipe data/factory reset
Click to expand...
Click to collapse
Arrrrrgh do I really have to?
In no case I want to lose my messages. Is there any other working possibility?
Or does that mean no JB for me? :/
Heidegeist said:
Arrrrrgh do I really have to?
In no case I want to lose my messages. Is there any other working possibility?
Or does that mean no JB for me? :/
Click to expand...
Click to collapse
When you want to flash from CM9 you can try without data wipe . It wordek for my very well Just wipe Cache and Dalvik Cache.
Heidegeist said:
Arrrrrgh do I really have to?
In no case I want to lose my messages. Is there any other working possibility?
Or does that mean no JB for me? :/
Click to expand...
Click to collapse
you can make a backup of your messages with sms backup and restore
xolo7 said:
When you want to flash from CM9 you can try without data wipe . It wordek for my very well Just wipe Cache and Dalvik Cache.
Click to expand...
Click to collapse
On the other hand, when I tried to do it without the data wipe, the OS was very slow and applications stopped responding often. After wiping it completely, it's fast and snappy. So YMMV a lot, and I recommend using SMS Backup and Restore[ and doing the factory reset.
cdlq456 said:
F.A.Q. for CM10 Jelly Bean on Motorola Defy and Defy+
- How to update from previous nightly's?
1) Go to recovery
2) wipe cache and dalvik
3) flash the last .zip file
4) flash gapps
5) wipe cache and dalvik
6) restart
Make sure you flash the lastest gapps or use a file explorer for root (as Root Explorer), go to system/app and delete duplicated apps (gallery and camera are more common)
Click to expand...
Click to collapse
no need to flash gapps every time update the nightly
or put a (....) and write "only you have an update for it"
a noob will flash a gapps every time update the nightly
ps. to many wipe cahe and dalvik
one on the begining is enough
Anyone knows why my wi-fi does not work properly?
I just do everything that the first post says but but I only managed to connect once. It took about 30 minutes to connect and disconnect after 20 minutes.
Maybe got somethin' with WPA2.
vaserbanix said:
no need to flash gapps every time update the nightly
or put a (....) and write "only you have an update for it"
a noob will flash a gapps every time update the nightly
ps. to many wipe cahe and dalvik
one on the begining is enough
Click to expand...
Click to collapse
i will clarify that, but that's the process that i've followed since my first cm7 builds (wipe before restarting) and NEVER have any problem with fc or bootloops or anything like that.
Another thread for this? I'm confused now, where are the BUG REPORTS supposed to be reported? under this thread? under the [support] thread?
leandeganis said:
Another thread for this? I'm confused now, where are the BUG REPORTS supposed to be reported? under this thread? under the [support] thread?
Click to expand...
Click to collapse
this is just a faq, if you have a question that's not answered here, post it.
vaserbanix is right, no gapps needed. Never hearded about this when just updating to new build, cause the will stored in \data not system.
Also you should add links Epsylons download link and links to kernels, battery fix and so on. Maybe the best way, is to just link to [Support] - [JB] CM10 Android 4.1.1 for the Defy(+) for questions about installation.
Maybe an other good point for FAQs:
Why can I use Defy+ (MB526) builds on Defy (MB525) red lense and what are the advantages?
Because Defy+ has same camera as normal Defy with red lense, you can use its Gingerbread kernel and the MB526 builds. With green lense Defy you have to use Froyo kernel and MB525 builds to have working camera. But beside the use of 4 instead of 3 Vsel CPU steps, and possibility for 720p recording there are no real advantages in using GB kernel. Both are based an 2.6.32.9 Linux kernel. Also you have to install a seperate battery fix, when using Defy+ build with normal Defy, because it has different battery size.
G00fY2 said:
vaserbanix is right, no gapps needed. Never hearded about this when just updating to new build, cause the will stored in \data not system.
Also you should add links Epsylons download link and links to kernels, battery fix and so on. Maybe the best way, is to just link to [Support] - [JB] CM10 Android 4.1.1 for the Defy(+) for questions about installation.
Maybe an other good point for FAQs:
Why can I use Defy+ (MB526) builds on Defy (MB525) red lense and whats the advantage?
Because Defy+ has same camera as normal Defy with red lense, you can use the same Gingerbread kernel and the same builds. With green lense Defy you have to use Froyo kernel to have working camera. But beside the use of 4 instead of 3 Vsel CPU steps, there are no real advantages in using GB kernel.
Click to expand...
Click to collapse
thanks. i'll add it to the OP
Thanks, but I habe edited my post and improved my answer. So please use this for first post.
G00fY2 said:
Why can I use Defy+ (MB526) builds on Defy (MB525) red lense and whats the advantage?
Because Defy+ has same camera as normal Defy with red lense, you can use the same Gingerbread kernel and the same builds. With green lense Defy you have to use Froyo kernel to have working camera. But beside 4 instead of 3 clock-steps, there are no real advantages in using GB kernel.
Click to expand...
Click to collapse
porhaps is only my opinion but the GB2.3.6 kernel is most stable on overcklok than froyo kernel
froyo kernel was made for Defy red/ green and cloked to 800mhz and it run to1000mhz
up on that value it give more restarts then GB2.3.6 wich i took it to 1.3ghz without problem
maybe is wrong my opinion but i test its with many rom's
G00fY2 said:
Thanks, but I habe edited my post and improved my answer. So please use this for first post.
Click to expand...
Click to collapse
done!
KangXperiaProject
bringing AOKP to Xperia
{
"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"
}
AOKP is an awesome custom Android firmware. (just like MIUI and CyanogenMod).
AOKP is based on AOSP and looks as vanilla as possible, and focusses on lots and lots of user-friendly features. What makes it different from CM is that there are many more user-customizable features.
KANGXPERIAPROJECT
This ROM is a combined work of all members of KangXperiaProject.
AOKP is not officially supported on any of the Xperia smartphones. So we made a Kang XperiaProject team comprising
Supervenom , Championswimmer, Pikpok, mikegapinski
We maintain sources from which we build (not winzip porting) AOKP for all the Xperias.
We are not any great developers (all teenagers). We are just trying to provide users with more ROM options
Our work is not possible without using sources from FreeXperiaProject.
Code:
==beta1==
merged latest sources
fixed toggles
==alpha2==
fixed FC com.android.phone
BUGS / NOT-WORKING
everything working !!! (except HDMI)
To report issues/bugs or make feature requests please go to
http://code.google.com/p/kangxperia/issues/entry
ROM downloads
beta1
http://hotfile.com/dl/177659340/7940512/aokp_aoba-ota-eng.championswimmer.zip.html
GAPPS download
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Copy ROM zip and Gapps to sdcard
If coming from stock, flash kernel that has recovery using fastboot (not needed if you have kernel with recovery)
Boot phone, go into recovery (press vol-up(2012) or back(2011) when led is purple)
IF COMING FROM SOME OTHER ROM, make factory wipe then go into mounts/storage and format system
install zip from sd card then flash gapps if you want them (kernel is flashed automatically with zip for 2012 models, for 2011, fastboot flash the kernel)
reboot and enjoy
Sources are hosted at
www.github.com/KangXperiaProject
Gerrit code review is present at
http://smartdev.com.pl:8080/
To participate in development read this
http://code.google.com/p/kangxperia/wiki/Gerrit
We all spend countless hours working with thousands of lines of code to be able to bring these ROMs to you. It needs us to devote our precious time, and often we need to spend money to maintain the build machines, hosts and other stuff. So if you like this ROM and if it makes your phone look cool, please consider donating to us.
KXP Team Members (we bring you these builds)
Donate to Championswimmer
Donate to Pikpok
Donate to Supervenom
Donate to mikegapinski
FXP Team Members (without whom no custom ROM on Xperias would ever be possible)
Donate to FXP
Donate to Kali-
Donate to Bin4ry
Team KANG Members (who have made all these awesome features on AOKP)
Donate to Stevespear426
Donate toRoman
Donate to Whitehawkx
Donate to Jonathan Grigg
Donate to Zaphod-Beeble
Donate to ProTekk
Donate to Sethyx
CREDITS
Other than the people mentioned above, we want to thank all developers working Xperia devices like
DoomLord, Keiran, Achotjan, Sirkay, Blagus, NobodyAtall, Androxyde, Kamarush, Paxchristos and many many more. And the various CM devs like cyanogen, koush, codeworkx, rmcc ....
All the respective ownerships of commits are maintained on the gerrit/github and you can see what fixes are ported from / contributed by whom.
did the on screen button LED light working? And how is the sound.....im lazy to test it first...i need both of that so i can stay to the rom...
This is awesome.
Many thanks to The FXP team.
@faiisfaizal
Do you need to quote the whole post for your one liner.
ganeshbiyer said:
This is awesome.
Many thanks to The FXP team.
@faiisfaizal
Do you need to quote the whole post for your one liner.
Click to expand...
Click to collapse
im on phone sory...i cant see the quote so long....Re-edit hhahhahaha sory
So far so good! I'm using the FXP kernel and the install went smoothly. Now getting it setup and playing around. Nice!
mroach said:
So far so good! I'm using the FXP kernel and the install went smoothly. Now getting it setup and playing around. Nice!
Click to expand...
Click to collapse
Im on my way to download....sound?Led button light?
Im confused, you probably cant use this unless your bootloader is unlocked, but in the steps you say "If coming from stock, flash kernel that has recovery using fastboot (not needed if you have recovery)". So does that mean i can install this along as i have access to CWM?
faiisfaizal said:
Im on my way to download....sound?Led button light?
Click to expand...
Click to collapse
Sound is great. LED button lights don't work, but I don't care since they're useless in the dark anyway. It'll probably be fixed at some point!
---------- Post added at 02:24 PM ---------- Previous post was at 02:21 PM ----------
fcb13 said:
Im confused, you probably cant use this unless your bootloader is unlocked, but in the steps you say "If coming from stock, flash kernel that has recovery using fastboot (not needed if you have recovery)". So does that mean i can install this along as i have access to CWM?
Click to expand...
Click to collapse
You need an unlocked bootloader. The installer needs to be able to flash a kernel, and you can't do that with a locked bootloader.
fcb13 said:
Im confused, you probably cant use this unless your bootloader is unlocked, but in the steps you say "If coming from stock, flash kernel that has recovery using fastboot (not needed if you have recovery)". So does that mean i can install this along as i have access to CWM?
Click to expand...
Click to collapse
how could you possible FASTBOOT A KERNEL without unlocking bootloader
Make your steps more clear...it says you dont need to fastboot, unless you dont have recovery. It just says you need a kernel that has recovery and we have recovery without a custom kernel, so just make your steps more clear.
fcb13 said:
Make your steps more clear...it says you dont need to fastboot, unless you dont have recovery. It just says you need a kernel that has recovery and we have recovery without a custom kernel, so just make your steps more clear.
Click to expand...
Click to collapse
sorry
i have edited one word in that makes a hell lot of a difference now
basicaly the instructions were written at a time when recovery was possible only with custom kernel thus if you had recovery it implied you are running a custom kernel (which means you had an unlocked bootloader)
anyways people on the forum should have realised by now that aokp/aosp/cm will never be available on locked bootloaders
There are some custom roms that port over CM9/AOKP to work with the stock kernel.
fcb13 said:
Make your steps more clear...it says you dont need to fastboot, unless you dont have recovery. It just says you need a kernel that has recovery and we have recovery without a custom kernel, so just make your steps more clear.
Click to expand...
Click to collapse
I guess the instructions could be a little more clear, but they're just saying you need a functional recovery so you can flash the ROM. The fact that it says the installer flashes a kernel is your key that you need an unlocked bootloader.
Basically you're never going to be able to run a ROM that is not based on stock because non-stock-based ROMs will need their own kernels which can only be flashed with an unlocked bootloader. So any of these ROMS based on CM, AOSP, AOKP: You can't run them.
could u reupload the file on mediafire.....the hotfile lunk doesnt work....i wait for the timer to go off so i can download the file....however i get redirected to the same page ....
Sent from my rooted and deodexed Xperia Ion LT28h using tapatalk 2
XperiaIonLT28H said:
could u reupload the file on mediafire.....the hotfile lunk doesnt work....i wait for the timer to go off so i can download the file....however i get redirected to the same page ....
Sent from my rooted and deodexed Xperia Ion LT28h using tapatalk 2
Click to expand...
Click to collapse
you can get everything you need inside
http://icxperia.com/championswimmer/aokpics
Like I just said, some devs have made a CM9/AOKP rom to work with a stock kernel...look at jjdoctors work for the arc/ray
fcb13 said:
Like I just said, some devs have made a CM9/AOKP rom to work with a stock kernel...look at jjdoctors work for the arc/ray
Click to expand...
Click to collapse
never mind
the instructions are clearer now i guess
Get the hdmi working and I'm in
Sent from my LT28h using xda premium
mroach said:
I guess the instructions could be a little more clear, but they're just saying you need a functional recovery so you can flash the ROM. The fact that it says the installer flashes a kernel is your key that you need an unlocked bootloader.
Basically you're never going to be able to run a ROM that is not based on stock because non-stock-based ROMs will need their own kernels which can only be flashed with an unlocked bootloader. So any of these ROMS based on CM, AOSP, AOKP: You can't run them.
Click to expand...
Click to collapse
championswimmer said:
sorry
i have edited one word in that makes a hell lot of a difference now
basicaly the instructions were written at a time when recovery was possible only with custom kernel thus if you had recovery it implied you are running a custom kernel (which means you had an unlocked bootloader)
anyways people on the forum should have realised by now that aokp/aosp/cm will never be available on locked bootloaders
Click to expand...
Click to collapse
OP does need to edit the steps involved in flashing this rom.
Also, alot of people do not know that aokp,cm, aosp. roms use kernels that are other than stock. your statement in this matter really is kind of ignorant. Like you knew this before you started messing with phone software and ccreating / porting roms.
Think of it, (no disrespect to any one), as everyone is new to the process. your steps should be clear and concise and reflect how to flash and what steps are required to make sure a fresh clean install is what the user experiences...
Just remember you were a noob at one time as well and even though you may be an experienced user or modder / creator, you will eventually run into a problem as well, and would be more apt to learning to correct the issue if steps are explained clearly to you. show others the same courtesy.
As for me, i have a locked bootloader so flashing this and fxp kernel is still out of reach for me. it will probably be another year like it was for the x10 before bootloader is unlocked...
i keep getting the status 7 error whenever i try to update...could u pls help me....
Sent from my rooted and deodexed Xperia Ion LT28h using tapatalk 2
WELCOME TO OptiBean RC1 for LG LU6200
RC2 Link is on post # 4
Below are the details of this ROM.
NOTE: I am not responsible for bricking your android phone for installing this customized ROM.
Use it at your own risk but rest assured that this has been tested thoroughly to avoid such errors.
Just post an error report on this thread for further development of this ROM. I also consider DONATIONS.
ROM DETAILS:
Pre-installed Apps:
Holo Launcher HD 1.0.6
XDA Assistant
Airdroid
Flash Player [May not Work on some Apps]
Movie Studio
Rebooter
Torch
Youtube
And some Inverted GAPPS by JustinBean
Tweaks:
Ported from CM10 latest build 4.0.1 JB
Running 3.0.8 Hi1Jason Kernel
Mms app [bubble style tweak] - Created by DeNitE
Build prop tweak
-Internet Speed
-VM Heap size increase
-Better battery life
-Buttery Smooth [Depends on Units sometimes]
-Better Camera/Video Decoding & Encoding
-Faster Reboot
-Faster Application Loading
-And many more
Customized Boot Animation [Droid Razr New]
Beats Audio Modification [For Sound Quality] [Removed}
And many more... I cannot remember All.
{
"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"
}
Code:
[URL="https://www.dropbox.com/s/fpcc1i4fxguhll3/OptiBean_RC1_LU6200_2.zip"]https://www.dropbox.com/s/fpcc1i4fxguhll3/OptiBean_RC1_LU6200_2.zip[/URL]
Installing This ROM?
1. First make a back-up your current ROM. And make sure your phone is rooted and CWM is installed.
2. Wipe data/Factory Reset
3. Wipe Cache
4. Wipe Dalvik Cache
5. Wipe Battery
6. Install from SD Card then Select the File
7. Wait till it is complete then Restart.
8a. For those who backup their contacts in their SD card w/ a VCF file,
if you want to restore it after then you must NOT sign in on your google account or just
click "Not now" then proceed to finish the initial config then restore first the contacts before doing anything else.
8b. For those who backup their contacts using Google Auto Sync and want to restore it,
just follow the on screen instruction and make sure you have internet connection.
9. Enjoy the ROM! Press thanks if you like it and DONATE if want more of it.
Note: After the ROM boots up completely, wait for it to properly scan the SD card as it is still loading.
And there is a possibility that the Camera App will lag at first use but after using it for a while it will be as smooth as butter [based on my experience]
Please Support My Work By Simply Donating to my Account if You like It.
It's not easy for me being here in the Philippines to upload such a file because of slow internet connection.
That is why I need to pay an expensive Connection just to do my work and projects.
Thank you in Advance.
Credits For the Following Persons:
Hi1Jason - For Everything Esp. for the Kernel
JustinBean - For Some Inverted Apps
Astrix from s3forums for the tweaks and tutorials
And for the Testers for risking their phones for using this ROM
Sceen Shoots Already Posted!
NOTE: I don't have my Optimus LU6200 anymore. I upgraded to LTE 2 so I cannot test my new ROM for this Unit, Sorry for cutting you here.
CM10 Screen Shoots
;
;
;
;
;
;
tks!
[ROM] [CM10 port] OptiBean RC2 for LU6200 (JB 4.1.2) Now Available
OptiBean RC2 Intsructions:
1.)First make a nandroid backup
2.) I recommend that you use Hi Recovery v1.0 for LU6200
Link:
http://forum.xda-developers.com/showthread.php?t=1951554
Click to expand...
Click to collapse
3.) After changing your recovery to Hi Recovery,
4.) Wipe System, Wipe Data, Wipe Cache, Wipe Dalvik
5.) Flash ROM [Link Below] and lates JB Gapps [link below]
6.)Restart Phone
Note: You can flash 2 or more file in just a single flashing using Hi1 Recovery,
You can download latest Jelly Bean Gapps Here: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Happy Flashing. Enjoy.
Release Candidate 2 Link: [Download]
http://d-h.st/WY4/
Click to expand...
Click to collapse
Release Candidate 2 Changelogs:
-Latest Stable Build of CM10 JZO54K [JB 4.1.2]
-Latest Baseband
-Latest Kernel build from Hi1Jason [3.2]
-Faster Internet Speed
-VM Heap size increase
-Better battery life
-Much Smoother
-Better Camera/Video Decoding & Encoding
-Faster Reboot
-Faster Application Loading
Fixes:
Long Charging Time Issue Fix
Boot Animation Fix
Some Apps FC fix
Annoying Vibration on Dialer Fix
More APN list support
Bugs:
Please report to me if you found anything on this ROM. I'm happy to work with you guys.
Can we REALLY format the external disk with that rom? I've tried Hi1jason's CM10 v3.0 rom but sim toolkit is not working and has a few bugs. One thing I like with his rom is a longer battery life. More power kababayan!
Hi1jason's CM10 v3.1 is out. Will try it soon.
SIM Toolkit is not Working on CM10 on our phone
devcon69 said:
Can we REALLY format the external disk with that rom? I've tried Hi1jason's CM10 v3.0 rom but sim toolkit is not working and has a few bugs. One thing I like with his rom is a longer battery life. More power kababayan!
Hi1jason's CM10 v3.1 is out. Will try it soon.
Click to expand...
Click to collapse
Well based on search here, Currently, SIM Toolkit will not work on our phone. Maybe on some other countries it'll work. I have used Hi1Jason's kernel for this ROM and I have tweaked it to make it more battery saving. I'll be posting in a while the details of this ROM.
wow wow wow i wanna eat jelly bean....can't wait!!!!
Where is d link?
Thanks in advance.
Sorry for the Delay. I have found some minor bugs while on my final test. I have canceled the upload for some changes.
Awesome Beats will be deleted for some conflicts in the ROM. But I'll post the link of it later if you wish to flash it on your phone.
Meanwhile, this will just be a RC1 version.
Thank You for the Support.
LU6200
How is the battery life, bro?
Read Carefully
BinCanCook said:
How is the battery life, bro?
Click to expand...
Click to collapse
Please Read carefully on my post.
It is already stated on the ROM description.
Thank you.
I'll be posting it tommorow...
JB for LU6200
your dropbox account is locked.
Is there any mirror?
Thank!
Sorry for the inconvenience
BinCanCook said:
your dropbox account is locked.
Is there any mirror?
Thank!
Click to expand...
Click to collapse
I would like to apologize for what hapened. It seems that too many members downloaded my OptiBean RC1. But dont worry, the next link that I will be posting is the RC2 Already.
Please Donate Guys if you like my work.
First of all, thank you for your hard work. It's go great to see someone from the same country I live in developing a rom for this phone! (Im not Filipino though).
By the way, the rom is huge in size. (320mb!) Is this because of Gapps included in the rom? AFAIK, it is against Google's policy to include Gapps in a custom rom. You may have to remove the apps from your rom and link a set of gapps from Goo.im or something similar.
I'm downloading the rom now. Will report back after testing it.
Gapps
pins2u said:
First of all, thank you for your hard work. It's go great to see someone from the same country I live in developing a rom for this phone! (Im not Filipino though).
By the way, the rom is huge in size. (320mb!) Is this because of Gapps included in the rom? AFAIK, it is against Google's policy to include Gapps in a custom rom. You may have to remove the apps from your rom and link a set of gapps from Goo.im or something similar.
I'm downloading the rom now. Will report back after testing it.
Click to expand...
Click to collapse
Actually those are inverted Gapps that I have included. And in my next release it will be based from the latest cm10-M2 from cyanogen MOD... It will be packed with latest features of cm10.
It's just for testing. Because some of the GAPPS are not compatible with it so I have to select those that works.
Don't worry my Boy, I will seperate it once everything is in order. So for now, it will be included since it is not really released by google itself. It has been modified by some devs here so no worries.
mac20dnangel said:
Actually those are inverted Gapps that I have included. And in my next release it will be based from the latest cm10-M2 from cyanogen MOD... It will be packed with latest features of cm10.
It's just for testing. Because some of the GAPPS are not compatible with it so I have to select those that works.
Don't worry my Boy, I will seperate it once everything is in order. So for now, it will be included since it is not really released by google itself. It has been modified by some devs here so no worries.
Click to expand...
Click to collapse
Okay. it was just my 2 cents.
Anyway, I've been running the rom for past 2 days and it looks fine.
Here are just a few things that I want to address...
- Led flashlight toggle cannot be enabled for the notification bar.
- Can notice very minor graphical glitches found in UI animation.
- There seems to be some battery drain. I'm not sure what causes this. (Could be wifi?) It's not just for your rom, but prevails all other roms for this phone. For other devices that I had (see my signature), 1% or less per minute with WIFI on was very normal. but I'm getting at least 3 to 5% per hour now which is not satisfactory at all. Do you have any information on this?
RC2 os Coming
pins2u said:
Okay. it was just my 2 cents.
Anyway, I've been running the rom for past 2 days and it looks fine.
Here are just a few things that I want to address...
- Led flashlight toggle cannot be enabled for the notification bar.
- Can notice very minor graphical glitches found in UI animation.
- There seems to be some battery drain. I'm not sure what causes this. (Could be wifi?) It's not just for your rom, but prevails all other roms for this phone. For other devices that I had (see my signature), 1% or less per minute with WIFI on was very normal. but I'm getting at least 3 to 5% per hour now which is not satisfactory at all. Do you have any information on this?
Click to expand...
Click to collapse
Thank you by the way for your support. Your donation is a big motivation to me... Im currently working on the latest cm10-M2 build by cyanogen and Im in my half way... Im just kind of busy in my work and school.
Your feedback is much appreciated.
Wifi issue is caused by the tweak that I have made to its wifi connection.. Maybe I'll try to make fix it with the latest tweaks..
RC2 build info:
Latest JB build 4.1.2
Latest Superuser
Latest Recovery 6.0.1.5
System Apps updated
S3 camera app ported
Better sound/music app
And more...
Need all your support.
Please have some donations.
Thank you..
Sometimes i can't make system menu appear (which has pover-off, reboot, bootloader)
I thought it's maybe not a problem resulting from my hardware
still observing
((I have resolved it via installing a apk, rebooter
Your rom let me abandon MIUI ( ´ ▽ ` )ﾉ
THX!!!!!!!
Sent from my LG-LU6200
Thank You
wildsky said:
Sometimes i can't make system menu appear (which has pover-off, reboot, bootloader)
I thought it's maybe not a problem resulting from my hardware
still observing
((I have resolved it via installing a apk, rebooter
Your rom let me abandon MIUI ( ´ ▽ ` )ﾉ
THX!!!!!!!
Sent from my LG-LU6200
Click to expand...
Click to collapse
Thank You for your Support.!!!!
Im currently working on my next version of OptiBean.
It's now more stable than the first release.
Made some customization.
Remove some apps and added new ones.
Running 4.1.2 - Updated JellyBean Version
And Powered by the latest kernel made by hi1jason
All thanks to him.
Watch out for the next Release Candidate of OptiBean ROM for Lu6200!
If you like my work. Don't forget to drop coins on my account. It will help me do more projects.
Press thank if you like it.
GUYS,
GOOD NEWS. I'M DONE WITH MY LATEST BUILD OF OPTIBEAN AND ITS BEEN ON BETA-TESTING STAGE AND CURRENTLY RUNNING SMOOTH.
HOPEFULLY I COULD POST IT AS SOON AS POSSIBLE.
JUST DONATE IF YOU WANT TO, BUT IF NOT THEN YOU ARE NOT FORCE. BETTER TO SHUT YOUR MOUTH IF YOU DON'T HAVE ANY GOOD THINGS TO SAY.
CHANGES:
Latest JB Build (CM10) 4.1.2
Latest Recovery 6.0.1.5
Latest Hi1Jason 3.1JB Kernel
Latest Apps
Remove/Separated GAPPS
More tweaks and fix
New Boot Animation
Added new apps
Ported SG III Camera
and more....
SOON TO BE RELEASED (",)
No harsh feeling here but donation should be pure giving. What you are asking starts to look more like selling as you emphasize the word "donation" in every post you make.
If you really need funds to continue, better monetize your rom. Create some locked features, and make an app that unlocks them and sell it on Play Store.
Sent from my GT-P6200 using xda app-developers app
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you will find everything you need to know about SlimRoms.
Slim Downloads - Download the ROM, GApps and other Addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequently asked questions with answers.
Kernel Source - The source of your device's kernel.
See Post #2 for Known Issues and Installation Notes.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Special thanks to (in no particular order):
The Slim Team
CyanogenMod
prbassplayer
wantowan2
kintwofan
Disclaimer: SlimRoms are not responsible for any damages to your device.
I do not own the SGH-T989, but I do have 3 SGH-i727 Skyrockets, and the Hercules is almost identical. My time is limited, but due to several requests for this, I wanted to share. Please help each other out, and keep the thread friendly and informative.
Installation:
Install a 4.4 compatible recovery, and reboot to recovery afterwards.
Format /system, /data and /dalvik cache.
Flash a compatible radio (see below).
Flash the ROM.
Flash GApps.
Reboot and enjoy!
Known Issues:
Power-off charging animation not working.
You tell me...
Reporting Issues:
Do NOT report issues here if you're running a non-stock kernel, Xposed and/or modules, or any other non-stock mods.
For bug reporting (stock Slim ROM/kernel/GApps only), please use the Slim Bugreport tool, accessible through Settings > SlimCenter > Bugreport to produce a zip file in the phone's storage which you then can upload to the SlimROMs Hercules Subforum for review. Please see Reporting Bugs on the Slim web site for more information.
Any issues please explain with specific details, how to reproduce the problem, and provide a Slim Bug Report (preferred, in the ROM), or a logcat. Good feedback is ESSENTIAL.
Installation Notes:
Radios: Make sure you are running a JellyBean radio or newer (T989: UVMC6 | T989D: TLMC4), and follow the installation instructions linked to in post #1. A thread for flashable radios is here.
Recovery: Recommended recovery: CWM or TWRP.
Superuser: The Slim Team has made it so the Superuser App is not enabled by default, requiring users to intentionally turn on Root access. To enable it, navigate to Settings > Developer Options > Root Access and choose Apps and ADB (even though it may appear selected). For this to work, you need to first go to Settings > About Phone and tap on Build Number several times to gain access to the Developer Options.
Also see here: http://slimroms.net/faq/slimbean/441-how-do-i-enable-root
Kernel: The kernel is based on the Moretz CM-11.0 kernel, but overclocking has been disabled to enhance stability. For sweep2wake, fast charge, and CPU freq/governor control features, I'd recommend [ROOT] Kernel Tweaker from the Play store.
Wi-Fi: Wi-Fi connection dropping issues? Check your region code in Settings > Wi-Fi > (menu key) > Advanced > Wi-Fi region code. It may be set to Europe by default, which uses a different set of Wi-Fi channels than the United States or Canada.
DPI: For information on changing the screen DPI, see here: How to change the screen density (DPI). Beware that some apps may not play nice with custom values, although normally the Slim GApps are modified to tell the Play Store and a couple of other apps that the phone's DPI is always 240.
Enjoy!
(reserved)
Initial test build: http://www.androidfilehost.com/?fid=23578570567714111
Welcome to the Hercules forum and thanks for bringing this ROM back to us. I will be testing this later this evening after work. Also I will get the word out on G+.
big fan of slim cant wait to see what this brings
Initial Impressions
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
ArtfulDodger said:
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
Click to expand...
Click to collapse
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
NoSpamDan said:
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
Click to expand...
Click to collapse
Yeah I was afraid you might bring the logs up, and rightfully so. Reason that I did not use the built in kernel is that I have NEVER had good experiences with stock kernels from CM. Plus with the limited governor availability, I was hoping Wild! would eliminate that problem. I was also unaware of Bootlog Uptime or I would have used it to help with this situation.
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup. After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
ArtfulDodger said:
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup.
Click to expand...
Click to collapse
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Click to expand...
Click to collapse
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
Click to expand...
Click to collapse
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
NoSpamDan said:
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
Click to expand...
Click to collapse
Well thing is, on other ROMs like PA or Beanstalk 4.4 builds I get about 40% an hour charge. I use two different chargers at home & work, both Samsung with no issues. The slow charging issue is one I've only encountered with official CM (especially 4.4 nightlies), an old Beanstalk 4.3 ROM and unofficial Carbon 4.2 build back from last fall.
On TB it really is both a blessing and a curse sometimes!
Only issue is found is SD card usage. I don't have external SD card btw
{
"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"
}
smokenbiskits said:
Only issue is found is SD card usage. I don't have external SD card btw
View attachment 2858649
Click to expand...
Click to collapse
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
NoSpamDan said:
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
Click to expand...
Click to collapse
Yes to wipe everything except internal SD.
I will try a dalvik/cache wipe/battery stats and see if it helps.
Don't have either of those email clients installed.
Clicking on SD card entry in battery just shows cpu uptime for SD Card, not specific process.
I'll remove juice defender after the wipes above work/don't work, don't want too many variables changing while trying to troubleshoot. :angel:
LOL, yes, one step at a time is good. else you can end up with no clue at all
Oh, I just saw "battery stats"... and wiping those has no effect in Android 4.4. Google debunked that some time ago. See here. Recharging the device will reset the battery usage stats in Settings > Battery.
I used to wipe the battery stats myself, and I honestly didn't know there were still recoveries that still had that built in (TWRP maybe) since I've been on PhilZ Touch CWM recovery myself for a long time. No Fix Permissions either, wouldn't you know (not a bad thing, actually)...
I sure did like my placebo effect, though. I still miss it, lol.
The Dalvik/cache wipe fixed SD card issue... Thanks
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
ive been on this all day today without any problems! slims as good it was before
HipHopAnonymous3 said:
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
Click to expand...
Click to collapse
Thank you much for the feedback.
1) You have to enable Superuser through Developer options. See installation notes in post #2, with a link to Slim's FAQ on it.
2) Good!
3) I've seen this before, and will look into it, although as you said, if you drill into the Wifi > Advanced > Region code settings, you can change it to whatever. So, low priority.
4) I'll look at the assert script for the radio version. Can you link the radio thread please?
5) I haven't heard of this. I don't believe it affects the Skyrocket...? Does this happen on the recommended radios?
I have a new build compiling with a "stock-ish" version of the Moretz kernel (no over clock/undervolting).
It has sweep2wake, fast charge, more governors, and reportedly better Bluetooth support (with SR users).
I'll post it for testing when it's ready for those interested...
I don't have any volunteers for testing (yet). . If you want to volunteer, you should be able and willing to clean flash at times 3-4 builds in a day, be able to capture logs and send them. Normal testing would be occasional builds, unless there was a major issue.
Looking for 3 or so testers to help possibly get this into the Slim weekly cycle.
Cheers!