Welcome to my new thread. Here I will post my various random optimus v stuff. I am not too experienced with this kind of thing and I really like to experiment, so expect periods of frequent updates with small changes followed by periods of few updates where I fix everything I broke and decide what to do next.
Now for what you came here for!
Roms:
iho magpie:
This is MY rom
features:
-launcher2
-my kernel
-fm.apk removed
-magpie apps2sd-ext (see below)
-backside updater (thanks jerry!)
magpie:
This is the way i think moving apps to ext should be done. There are no extra apps, no scripts, no flashing extra stuff, no breaking on rom updates. It is all built in to the ROM's framework.
magpie is a kang of the a2sd feature found in cm5, ported to cm6 and 7 by @firer4t. Just go into the manage apps menu, and there is now a button to move to ext right next to the usual move to sd one. it just works. moving apps back is as simple as pressing the move to phone button. simple, works.
pure build:
this is a nearly pure build of iho, only differences are the removal of fm.apk, and the use of bobzhome v3.7 kernel
note: gapps are not included in any of my roms. get that from your favorite place to find gapps
downloads:
https://github.com/inferiorhumanorgans/android_device_lge_thunderc_common/wiki/Binary
my kernel:
i took bobzhome's kernel and applied the -ck patchset to it, added the sio scheduler, and several other tweaks. the result is bobzhome's kernel, tweaked for responsiveness
for those who didn't understand a word i said, here you go: i took bobzhome's kernel and tweaked it to be more responsive and less likely to lag. enjoy
dl - tvall_kernel_v0.3.3.zip
source - https://github.com/tvall43/android_kernel_thunderc
Thanks goes to:
Blarf - for the awesomeness of iho
BobZhome - his awesome kernel which mine is based on
Jerryscript - the updater
Mrg666 - various patches and fixes
LeslieAnn - the forum, build server, and ftp server
Gannon - being awesome
Curiousnoob - laughs
My girlfriend - for putting up with my dev work and loving me despite the amount of time I spend doing this
/* reserved */
How to build my rom in 7 easy steps.
Step 1: set up a Linux or Unix (os x is supposed to work, never tried personally) box for building by following the directions at [ http://source.android.com /URL] and [URL=http://wiki.cyanogenmod.com]wiki.cyanogenmod.com
Step 2: for the repo init command, the url is https://github.com/tvall43/android.git -b gingerbread
Step 3: go watch TV or something while you're running repo sync. It WILL take a while.
Step four:
Code:
$ . build/envsetup.sh
$ lunch
(Select device, the optimus v is number 8 I think)
make bacon
Step 5: feed your cat(s)
Step 6: wait for the rom to build
Step 7: if it works, celebrate! If it doesn't, figure out what went wrong.
How to build my kernel in 3 easy steps (assuming you have followed the above or similar steps)
1: git clone https://github.com/tvall43/android_kernel_thunderc.git
2: cd into it
3: ARCH=arm CROSS_COMPILE=(path to toolchain. Ex. ../magpie/prebuilt/linux-x86/whatever..) make -j(# of CPU cores)
4: modify the build.sh script to save you time next time you build
How to build my fork of the tomato firmware for my wifi router in one easy step.
Step one: well... one, you are on the wrong site for that. Two, I haven't released any source or binaries of that. and three, there is no point to use it, ive only changed a few things
COPYING:
Android and linux is open source. feel free to do whatever you want with the sources (but be sure to keep within the terms of the licences. linux is gpl2, android is mostly apache2)
For the binaries I release, please ask before you use them as a base for other projects. I cannot think of any situation where i will say no, but its nice to receive a pm. (If I don't reply within 3 days, go ahead and do what you wish, but send me another pm quoting this post)
Launcher2 Options?
Tryin' out your ROM, but I'm having trouble finding any options to customize Launcher2... Any hints?
wilberfan said:
Tryin' out your ROM, but I'm having trouble finding any options to customize Launcher2... Any hints?
Click to expand...
Click to collapse
There aren't many. Launcher2 is light and fast (and some say better on the battery), at the cost of customization.
Google Play Store Force Closing
Trying to install apps from the Google Play website--but as soon as I click "install", Play force-closes on the phone...
wilberfan said:
Trying to install apps from the Google Play website--but as soon as I click "install", Play force-closes on the phone...
Click to expand...
Click to collapse
Never had that issue... what gapps are you using? Have you tried clearing cache and/or data for the play store?
tvall said:
Have you tried clearing cache and/or data for the play store?
Click to expand...
Click to collapse
Brilliant. I should have thought of that. Works like a charm, now! (I restored it from an old Titanium backup--that's probably why it was wonky until I deleted the cache?) Thanks!
wilberfan said:
Brilliant. I should have thought of that. Works like a charm, now! (I restored it from an old Titanium backup--that's probably why it was wonky until I deleted the cache?) Thanks!
Click to expand...
Click to collapse
That would do it. Glad you got it working. Enjoy the rom.
Your kernal is great! Amazing how responsive it is. Thanks for putting it together!
Sent from my LG-VM670 using XDA
Been flashing your kernel on everything as well.
Btw, how can you make Launcher2 faster?
Sent from my LG-VM670 using Tapatalk 2 Beta-5
Curiousn00b said:
Been flashing your kernel on everything as well.
Btw, how can you make Launcher2 faster?
Sent from my LG-VM670 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Launcher2 tends to he fast for me. What do you mean by "faster"?
Sometimes when scrolling homescreens, it gets a little sluggish, I suppose. Or chunky?
Sent from my LG-VM670 using Tapatalk 2 Beta-5
Curiousn00b said:
Sometimes when scrolling homescreens, it gets a little sluggish, I suppose. Or chunky?
Sent from my LG-VM670 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I don't see that issue.. but I tend to only use one or two homescreens. And I've been on ics so long my rom feels smooth as butter.
What settings do you have in cm performance settings?
Anyone here have the zv9 radio update and experiencing reboots an other issues you can only narrow down to the update?
I have a test kernel that some say helps with that, others say its the same as before. http://www.mediafire.com/?k6bka5rzoo37az4
Does ur from have mobile hotspot
Sent from my YP-G70 using xda premium
Stock settings, changed notifications toggles, lockscreen, widget settings, and overclocked to 600-806 Smartassv2.
Sent from my LG-VM670 using Tapatalk 2 Beta-5
Zachary droid said:
Does ur from have mobile hotspot
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
It should. Its an IHO rom
tvall the mobile hotspot is not working for me either i just get a error :-/.
Pushed a small update to my rom. Download via updater or wiki
Thanks For the update the Hotspot is fixed but im gettin the reboots from time to time still but maybe it's just me.
Related
Please note, I'm retired, and for the most part I don't visit XDA very often, I will respond if I happen to notice there's been a post, but don't send me angry PMs if I don't, personal life and finances has made it almost impossible to continue my work with android at all.
That being said, I'll still help where and when I can.
First and foremost, this is based on waydownsouth's trees, both the T20-common and the A100 specific trees with some updates and changes and additions from me.
I can't test anything, I don't have an A100.
These are not going to be nightly, daily, weekly, or whatever, these are now simply where I post test builds from working on the trees.
These are 4.1.2, and NOT 4.2! Use the 4.1.2 GApps packages!
Since I'm starting over, there are things that NEED to be tested, please:
BlueTooth
GPS
WiFi
Audio in general/performance
Audio specific outputs/inputs, such as headphones, headsets, BT, HDMI, dock, USB, whatever you can think of.
Video playback support/performance
Mounts, internal, external, swapped, whatever.
UI performance, I don't mean "It has a slight stutter for 1/4 of a second scrolling my 500 apps app drawer 2 seconds after it booted" I mean it either runs well or runs like crap over a day or two of use.
Cameras. I mean cameras in normal designed use, not photosphere or why it won't take clear pictures underwater at 8mp from the front camera.
Whatever else you can think of that needs testing
Please report them here, this is to take the random stuff out of the trees thread and keep here where it's more relevant.
As usual right off Hardslog has permission to use these as bases for whatever he wants, in a pinch, he can use them for toilet paper, anyone else please ask or let me know first.
Instructions
Coming from a previous pio_masaki build:
Make a nandroid backup of your current install, backup system, boot and data. Recovery optional.
Wipe Cache
Wipe Dalvik Cache
Wipe System
Install from zip (cwm) or install (twrp) and pick the cm10 zip you want.
CWM:
Hit yes (cwm)
Flash Gapps (cwm) *use a 4.1.2 GApps, not a 4.2 GApps*
TWRP
Hit the additional zip button, add gapps zip *use a 4.1.2 GApps, not a 4.2 GApps*
Slide to flash
Both
Reboot
Let ROM sit for 10 minutes
Reboot
Let ROM sit for 5 minutes, begin normal usage.
Coming from any ROM besides a pio_masaki CM10
Make a full nandroid backup
Wipe Cache
Wipe Dalvik
Wipe System
Factory Reset (optional, blackhole wipe, this will wipe internal SD as well!)
Install from zip (cwm) or install (twrp) and pick the cm10 zip you want.
CWM:
Hit yes (cwm)
Flash Gapps (cwm) *use a 4.1.2 GApps, not a 4.2 GApps*
TWRP
Hit the additional zip button, add gapps zip *use a 4.1.2 GApps, not a 4.2 GApps*
Slide to flash
Both
Let ROM boot, allow for up to 15 minutes.
Once the welcome screen appears, let it sit for 10 minutes. Don't do setup yet.
Reboot
Let sit 5 more minutes.
Proceed with setup wizard
Restore USER apps only. Restore data if needed, otherwise start fresh from the Play Store.
DO NOT RESTORE SYSTEM APPS OR DATA
Reboot after restore is finished.
Use as normal.
Downloads
Ok, goo.im went down, and pio-masaki.com is gone, so the files are effectively gone for ever. I have 1 single build, B3 TabUI Mod, which you can find here:
CLICKY CLICKY
Also a far older, dusty, ancient build is tucked away over on devhost, which is here:
GRANDMA CM10
I have no idea what works or doesn't with it.
If those don't float your boat, head over to the kuroikaze thread, there's some builds there as well, 4.1 and 4.3 based.
Feel free to use any gapps packages you wish, but please use 4.1, if you have issues with things like keyboard vanishing/crashing, play store or other stuff crashing, these ARE gapps related.
Change log:
B1 - 11-08-12: Initial updated 4.1.2 build. Addressed HDMI audio. Memory bar added to recent apps.
B2 - 11-25-12: Updated source build. Memory bar in recent apps removed, "kill all" button added to recent apps instead, upstream CM change.
B3 - 1-13-13: Updated source, built using Linaro 4.7 toolchain and -O3 and strict-aliasing in various areas. ROM only, kernel is still stock CM9. Basically just an updated build for you guys, haven't addressed anything in particular.
B3 - 1-13-13 Modded:
Acid Audio with Sony and Awesome Beats, new transition animations, slight dalvik tweaks. Just some of the stuff I've been working with on the Thrive added in for flavor. Untested.
B3.5 - 1-17-13: Updated source to B3, however is built with Tablet UI forced, otherwise stock build of CM10, no mods. Don't expect me to keep doing dual builds of CM10 for you guys =p
B3.5 Modded - 1-17-13: Updated source to B3, however is built with Tablet UI forced, same mods as B3 Modded.
B4 - 1-19-13: Addressed GPS issues, Trebuchet oddness and clock fitment (cutoff). Blind fixes, may fix everything or nothing.
B5 - 2-01-13: Nothing special, just an updated build as was asked about. Here's your friday night flash fix guys. Apparently broke external SD mounts somewhere.
B3 Tablet UI and B4 Phablet UI:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
20130715
Updated source
Trimmed the trees a little
Added prebuilt kernel and modules
Simply a test build that the changes didn't break anything.
20130731
Experimental 3G/RIL support for A101 devices!
Memory management, in a couple places now, to help with memory leak issues. While it may not prevent the memory leaks, it should prevent it from impacting the system so badly. Thank you, nVidia.
Dock settings added for those with the dock. Does anyone even have one?
BT DUN, WiFi P2P and WiFi Direct support added (experimental)
Rotation Lock Switch support added (back) in
Music Visualization overlay settings
Add large heap to launcher2
Tuning of the boardconfig and device files for UI.
Probably more I'm forgetting.
20130801:
Paths in init corrected, should fix mount issues from B5 to now.
Lockscreen rotation enabled even with switch in use by the ROM in overlay.
20130801-B2:
Redid init, should all be peachy again.
20130802:
Once again massive battles for no real obvious reasons besides I'm getting rusty.
Internal SD workd as it should
External SD works as it should
USB Storage ability added
Settings>Storage crash corrected, no longer force closes
Should now be back to a daily driver usable status, so please do further testing on audio, etc and report back your findings. @hardslog, this update may finally be good enough for an updated base lol
20140404:
Updated source
Trees are 99.9999% the same as last build, with one change:
Remove unsupported overlay
Won't, or shouldn't, have any apparent changes.
Built on request from our Russian cousins.
Thanks:
waydownsouth - for working with me enough to even begin to comprehend what he's done for the Iconia devices.
randomblame - for helping me getting jellytime up on the A100 and helping me out with random ideas and interesting conversations in IRC.
ntan97 - being my tester in IRC for the most random ideas I've ever had.
justjackyl - for being my go to guy for testing anything I do for the A100.
Cyanogenmod - for obvious reasons.
Google - for obvious reasons.
The team behind Acid Audio
The guy(s) behind Awesome Beats
Everyone who's donated, its appreciated
I'm sure I missed some, if I did it's nothing personal.
Hey pio_masaki,
I don't know what it takes to build a rom, but I have an A100 and would like to see this thing get some good 4.1/4.2 action going. I'm alright with a command line and I actually do QA for web programmers for a living. And I really want to learn more about android.
If you build em, I can test em and report back. On this CM10 build or your Jellytime Sosei. What do you think?
kiden said:
Hey pio_masaki,
I don't know what it takes to build a rom, but I have an A100 and would like to see this thing get some good 4.1/4.2 action going. I'm alright with a command line and I actually do QA for web programmers for a living. And I really want to learn more about android.
If you build em, I can test em and report back. On this CM10 build or your Jellytime Sosei. What do you think?
Click to expand...
Click to collapse
4.2 will not be an option from me, I don't have an a100 to even get it booting. Secondly, I don't feel like building a new twrp to handle an android version that may never be used on this device. Again, maybe if I had one, but its not worth the extra hassle right now.
Sent from my Thrive - Kuroikaze B18 - Balthesaur V2.71b
pio_masaki said:
4.2 will not be an option from me, I don't have an a100 to even get it booting. Secondly, I don't feel like building a new twrp to handle an android version that may never be used on this device. Again, maybe if I had one, but its not worth the extra hassle right now.
Sent from my Thrive - Kuroikaze B18 - Balthesaur V2.71b
Click to expand...
Click to collapse
Well if you want help with testing the 4.1 builds, I'd be up for it.
Have no fear
if you build it I'm gonna use it (ics or jb} am right proud of your work and enjoy using it.. thanks alot:good::good::victory:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
justjackyl said:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
Click to expand...
Click to collapse
I hear that
Sent from my vangogh using Tapatalk 2
billypoke said:
I hear that
Sent from my vangogh using Tapatalk 2
Click to expand...
Click to collapse
That's the beauty of a Nandroid!
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Lol nah
That's OK, you dev to your hearts content.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
justjackyl said:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
Click to expand...
Click to collapse
Yeah same here. Nandroid will help me decide and I can switch back if need be.
Sent from my A100 running Jellytime Sosei Bakedbean using xda premium
pio_masaki said:
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
B-b-but I like having choices!
Sent from my SCH-I535 using Tapatalk 2
First off thanks pio for making yet another rom for our device. I was able to load this up before work and play with it for a few minutes. It seemed very smooth and responsive. Two minor things I noticed 1.The bottom part of the clock was cut off in the status bar even when I expanded it and it happens in landscape and portrait 2. When switching apps in portrait mode the top 75% of the screen is grayed/dimmed for the background but the bottom is still normal. Unlike in landscape were the whole background is grayed/dimmed.
Neither of these issues are serious or deal breakers though just a couple minor things I noticed.
If this sounded confusing I will try to attach some screenshots when I get home.
Once again thanks Pio.
Sorry to ask, but must i flash b2 over b1 or can i just flash b2. Coming from a different rom.
rain987 said:
Sorry to ask, but must i flash b2 over b1 or can i just flash b2. Coming from a different rom.
Click to expand...
Click to collapse
You don't need to go in order, but follow the directions for coming from another ROM. In short, full wipe.
Sent from my Galaxy Nexus using Tapatalk 2
Battery... why are you always so low when I find delicious new builds...
Thank you from the bottom of my heart ..
nsmith4 said:
First off thanks pio for making yet another rom for our device. I was able to load this up before work and play with it for a few minutes. It seemed very smooth and responsive. Two minor things I noticed 1.The bottom part of the clock was cut off in the status bar even when I expanded it and it happens in landscape and portrait 2. When switching apps in portrait mode the top 75% of the screen is grayed/dimmed for the background but the bottom is still normal. Unlike in landscape were the whole background is grayed/dimmed.
Neither of these issues are serious or deal breakers though just a couple minor things I noticed.
If this sounded confusing I will try to attach some screenshots when I get home.
Once again thanks Pio.
Click to expand...
Click to collapse
I can confirm this report about the UI, it looks as though it is out of scale (status bar, notification bar). What I'm guessing is another side effect of this is that when you hold Home and slide up to open Google search, the Google Arc and button are offset about 150 or so pixels to the left.
Also, I'm experiencing that the back button becomes slightly unresponsive after a while, this can be fixed by going to CM Settings > Navigation Bar > Reset to defaults.
Guys reporting random bugs is really quite pointless, I can't fix what I don't have. These are basically a nightly cm10 build to keep you guys updated, I can't test or fix anything wrong with them, I don't have one.
Sent from my Galaxy Nexus using Tapatalk 2
Un-Official Evervolv AOSP
This ROM is still in testing phase but must say it works quite nicely. Most all features are working fine. Read below for description of ROM.
As you may or not know, Evervolv has been building quality AOSP for multiple devices. Recently we (Classicnerd) have had the pleasure of working with Preludedrew in testing, working out bugs, and joining together to bring a fantastic rom to everyone using HTC, HP Touchpad, Samsung, Asus Nexus 7, and many more devices.
What to expect? Expect a solid platform which to build from. They have been known for adding Evervolv Toolbox which allows status bar tweaks, interface tweaks (volume wake, volume music control, Custom display density settings, and customizable power menu settings), as well as a stable platform which we can bring this hardware to full usage. There is also a Performance section for memory management and processor changes. The Themes section in settings is not working but should be very soon. Su works fantastic and so does the 4-1 boot to recovery work flawless.
Why Un-Official? There are many bugs to work out in an AOSP ecosystem. With that said, these bugs won't hinder your ability to enjoy this great device what so ever. Mostly when people go to an official release, it's because all hardware and software function as if it was stock with no issues and then they move on to the next build (possibly the next update). As you all know, there will always be some sort of issue. But we have a slight advantage with the Nexus 10 device. It's straight up Google. With Google in full support of the Android Open Source Platform, this gives many developers the opportunity to bring customized settings, tweaked apps, and modded framework to bring to the general public and flashaholics something we felt the direction should go.
Now we give you Evervolv Stella. I will let you all guess why the name stella came about. hehe, it was chosen by me which I feel honored to help support this project for you guys. Please understand that everyone on this team have full time jobs as well as work countless (often unappreciated, but more often appreciated) working on source code to bring ideas to life, while having a family life. If you feel the urge to donate, please do. We are saving to bring a Nexus 10 to Preludedrew. His wife cut him off from spending money on devices...lol No worries, we'll get him one.
This ROM ROM is very fast and smooth. While there may be glitches associated with jb, they are being removed and pushing it to the limits.
We now bring you Stella
Release date 11/26/12
* init.d scripts to boost performance, battery, low men, net boost, trim, and much more
* Ramdisk mods
* quad scores above 5300
* BT file transfer for all file formats
* 4-1 boot menu
* Updated to 4.2.1
* Inline Kernel Build
* Fixed YouTube
* EVToolbox
* All Hardware functional
* Google backup support (flash GAPPS after flashing rom)
* Google locations support
* OTG support
* SU working properly
* And many source mods coming from ICS
What doesn't work:
* themes
* you tell us....we need ur help bring this rom to life.
Downloads:
Stella v3.2.0 b4 Un-Official Updated 2/16/13 to 4.2.2
Stella v3.2.0 b3 Un-Official Uploaded 12.06.12 with google locations fixed.
Stella v3.2.0 b2 Un-Official Uploaded 11.27.12
Stella v3.2.0 b1 Un-Official Uploaded 11.26.12
Gapps JOP40C
With many thanks to Evervolv (Preludedrew, drewis, MongooseHelix, and nikez), tommytomatoe, misfit, ewalk, MindSplit, Jzen, Chubbzlou, TMartin, MYN, Cyanogenmod, XDA, craigacgomez, our wives and children, and the many testers. This list will grow as time evolvs..
Evervolv Source Link
AOSP Download AOSP Link
Installation directions.
1) You need to be unlocked and rooted. If you don't have either, check out the Nexus 10 android developement section for many different ways to prepare you device.
2) Copy the ROM and GAPPS packages to your Download folder on your Nexus 10
3) Boot to recovery and factory reset your device
4) Flash ROM
5) Flash GAPPS
6) Boot and enjoy
If updated from previous installation of the Evervolv Rom, installation is much easier.
1) Boot to recovery
2) Wipe cache
3) Flash Rom
4) Flash GAPPS
5) Reboot
6) Enjoy
un-official mods and add-ons
Awesome!! And first!!
Sent from my Galaxy Nexus using xda app-developers app
darkstar765 said:
Awesome!! And first!!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Haha, you're in for a treat. Sucks it takes so long to upload. But, only 22 minutes left till we go live
Edit...just two minutes left
I think this is also a good ROM.
ok, Rom and GAPPS are uploaded
Looks great! I'm about to try. Thank you!
@Leoisright nice... good to see Evervolv here... used to use this on my Nexus One... my brother still does on his!!
This device is going to have the best ROMs... CM, AOKP, Evervolv & Paranoid are already here and it's been just a week!!!
i know, all the big dogs in the house. Ur rom is great tho. It held me over until we got this rolling. I know it's priority #1 to get the kernel inline due to the mods in settings to OV/UC and mess with some other settings too. Once we get it right, you'll be the first to see the changes.
I have a few things i'll show you to add some stuff if ur interested. only little things but good ones. After I get this all set up i can show you.
HuluPlus and Youtube are not functional. Love the speed and smoothness though:thumbup:
†††
FL0OD said:
HuluPlus and Youtube are not functional. Love the speed and smoothness though:thumbup:
†††
Click to expand...
Click to collapse
ok, great...didn't test either of them. will check out the issue
Leoisright said:
i know, all the big dogs in the house. Ur rom is great tho. It held me over until we got this rolling. I know it's priority #1 to get the kernel inline due to the mods in settings to OV/UC and mess with some other settings too. Once we get it right, you'll be the first to see the changes.
I have a few things i'll show you to add some stuff if ur interested. only little things but good ones. After I get this all set up i can show you.
Click to expand...
Click to collapse
Sounds good...
I was actually working on some of this stuff for my Galaxy Nexus and when I got my device I just built it from AOSP and slowly added a few basic things... I just learned a lot of this stuff a few months ago with my Transformer Prime... so I'm still pretty much a newbie!
craigacgomez said:
Sounds good...
I was actually working on some of this stuff for my Galaxy Nexus and when I got my device I just built it from AOSP and slowly added a few basic things... I just learned a lot of this stuff a few months ago with my Transformer Prime... so I'm still pretty much a newbie!
Click to expand...
Click to collapse
do you have app compatibility issues with ur rom? Ours isn't compatible with basic ones like dropbox, youtube, rootexplorer, etc
Yeah, i jumped head first in aosp about a year ago. be very carefull, it can burn you out...lol i had to take a couple months off and enjoy other people work before i wanted to do it again.
Did anybody lose root after flashing this rom? And Google Now won't run because of Location setting problem.
Itaintrite said:
Did anybody lose root after flashing this rom? And Google Now won't run because of Location setting problem.
Click to expand...
Click to collapse
i didn't loose root. Sounds strange, but check the time settings. Mine changed to 6 hours ahead the first time i flashed it
edit. my root is fine, but there is something messed up with location. I can fix that in the next update.
Leoisright said:
i didn't loose root. Sounds strange, but check the time settings. Mine changed to 6 hours ahead the first time i flashed it
edit. my root is fine, but there is something messed up with location. I can fix that in the next update.
Click to expand...
Click to collapse
Weird. I ran root checker and confirmed that device isn't rooted. Came from PA-2.99.3.
click on settings/toolbox/interface/change dpi by 1. you will see it takes root privies. If not, something else may be going on. let me know if you could. also, open superuser. mines shows the pasted two days of usage.
Leoisright said:
click on settings/toolbox/interface/change dpi by 1. you will see it takes root privies. If not, something else may be going on. let me know if you could. also, open superuser. mines shows the pasted two days of usage.
Click to expand...
Click to collapse
You're right. But doesn't work with any other app that requires root. I just tried Adaway and it failed.
Itaintrite said:
You're right. But doesn't work with any other app that requires root. I just tried Adaway and it failed.
Click to expand...
Click to collapse
ok, will add it to the list. I know drewis just updated it and will report the bug
thanks for letting me know. There is an apparent compatibility issue as well. Will get that fixed too.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs
Looking forward to this
Flinny said:
Files still uploading...
Click to expand...
Click to collapse
Could you please reply back when you've made the files available? Thanks!
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
Uploaded
Sent from my Nexus 7 using Tapatalk 2
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
http://andromadus.codefi.re/ and sort by 'Date'
Wooo! Trying this
Can I flash directly over 4.1.2 build 129?
or would you recommend a clean wipe : ]
or check the link to the new website on the OP
I would suggest doing a wipe as Gapps etc are all different... if you do try an upgrade then I would suggest backing up... flashing rom/new gapps/wipe cache/dalvik at least.. then most likely finding it didn't work and having to wipe anyway
Nick.
Thx so much. I will try it.
Just tried installing directly over 129, rotation broke so I'm going to try from a full wipe. ( everything else is hunky dory really, although took a quite some time for the phone to calm down and get back to it's usual pace)
By the by, I notice the kill all icon from 129 is gone, is there anyway I can add that myself rather than wait for an update? ( as it's super handy!)
Thanks again flinny and Andromadus folks! My phone is even more woosh woosh and fancy than ever before.
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
jspina said:
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
Click to expand...
Click to collapse
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Pantherx12 said:
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Click to expand...
Click to collapse
Thanks. I know what the differences between the two are. I was just wondering if thats all that differentiated the two. And after looking at the titles its obvious that they are.
haha took me a few mins to realise this is the new cm 10.1 anyways good work as usual flinny downloading now
Sent from my HTC Vision using xda app-developers app
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Flinny please make name theme more easy. It difficult to distinguish
Sent from my HTC Desire Z using xda app-developers app
rubin110 said:
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Click to expand...
Click to collapse
Its missing in the settings menu for me also. And wifi works but sometimes it doesn't connect, everything else seems to work
Sent from my HTC Vision using xda app-developers app
Go to about phone and tap build number until it tells you that your now a developer....
Sent from my Nexus 7 using Tapatalk 2
Thanks flinny~~
It's so wonderful~
But I can't find the CM's function, like "Performance",
If the CM 10.1 have some function not implement??
Some features have not yet been ported to 10.1 by the CM team yet. But performance and developer are hidden in all 4.2 builds until you do the tap build number thing
Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off
Thank you sir,
Dling now
Sent from my Galaxy Nexus using xda premium
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium
charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol
Thanks for this.
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta
Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta
The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.
Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.
WildKernel
for T-Mobile Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Battery w/ Good Performance at 96-1350mhz:
Intellidemand/SIO (personal choice)
Lazy/SIO
Badass/SIO
Ondemand/SIO
Wheatley/SIO
'lil more Performance at 96-1512mhz:
Smartass/SIO
Hyper/Deadline
Samsung/Deadlne
lulzactive/Deadline
Savagedzed/Deadline
Best Performance (worst battery): 384-???mhz
Gaming/Deadline
Performance/Deadline
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the T-Mobile Galaxy S II (hercules), Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-hercules-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-05-28
Last Updated 2015-02-01
Wow I'm glad I was up late tonight! Downloaded this installed... Working cam 100% plus we can overclock again! Ole herc still running strong!! Thanks for this!!!
Thanks bro for doing this. I will flash and report
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------
Emmanuel, do you recommend CPU tuner or trickster or just stock performance to tweak settings?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Just flashed it on Carbon 5/21. Initial thoughts are that it seems to get to the boot animation quicker than Uber. But initial reboot is long... I thought my phone was stuck in a bootloop... Also does not kill vibration after subsequent reboots after the initial reboot after flashing the kernel. It's just as quick as Uber and seems to work with Kernel Tweaker. This kernel also won't crash the phone playing 1080p in portrait... Love the fact that this kernel has sleep2wake as well. Will report back after using it for the day...
Any chance of a 2ghz version? And does this work with PAC outta the box?
Edit: Forgot to say thanks for giving us another kernel for the good ol' Herc. So, thanks.
Sent from my SPH-D710 using Tapatalk 2
Not sure if its kernel related but after rebooting my phone because of play store issues. After rebooting, I lost all of my widgets that I placed on 4 screens.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Emmanuel U said:
WildKernel
for T-Mobile Samsung Galaxy S II
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms.
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please wipe cache and dalvik cache to avoid any possible issues.
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Download Latest WildKernel for Android 4.4+
Mirror (HTTP) / (FTP)
View all public kernel releases (Mirror)
Changelog:
Code:
[B]May 27, 2014 - ver001[/B]
1. Initial Release (based off Diablo 3.1 & Merged with all latest CM vidc changes to fix camera/camcorder issues)
2. [B]Voltage Table Overhaul: All clocks have noticeably reduced voltages to improve battery life without compromising performance.[/B]
3. [B]Add More GPU Scaling steps to create a new 'low power' idle and more intermediate steps until an OC[/B]
4. Various FS, IRQ, MM, Mutex patches
5. Enable All tweaks for Badass (including low-bat powersave, allow bypass etc.)
6. [B]New 'Ultra low' CPU Idle steps (96-153mhz) - Low power idling[/B]
7. Mpdecision allowed to scale down to 96mhz
8. BadAss and SIO set as default gov/sched
9. Update all Ondemand based governors to upstream (Google)
10. Update LZO (faux123)
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultan
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
XDA:DevDB Information
WildKernel for the T-Mobile Galaxy S II (hercules), Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Emmanuel U
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 001
Beta Release Date: 2014-05-27
Created 2014-05-28
Last Updated 2014-05-27
Click to expand...
Click to collapse
I haven't tested this yet, but it is on my "to test" list. I'm going to download it on my lunch break and flash it sometime on the weekend. Had a quick question though: what is the recommended date of the ROM one should use with this Kernel? The ROM I'm running was last updated back in March so I am unsure if any new CM features were implemented or removed from the kernel since that time and I would rather not be stuck in a boot-loop or nothing. The kernel I'm currently sporting is "3.0.101-DIABLO-3.3". You say yours is based off of Diablo 3.1, so I THINK it should play nice with this ROM, but I'm nervous I'll soft-brick my phone.
Is there a reason you didn't use Diablo 3.3 as the base?
Also, your OP states there are screenshots, but none are included? I don't need them (kernels don't really need screenshots, eh?), but just thought I'd point it out.
Thanks for being one of the ones keeping the t989 alive.
EDIT: I'm dumb... just saw the screenshot tab at the top. 18 hours on battery is pretty good. I get about 10 with how I have things set right now, so getting an extra 8 would be awesome.
bmg002 said:
I haven't tested this yet, but it is on my "to test" list. I'm going to download it on my lunch break and flash it sometime on the weekend. Had a quick question though: what is the recommended date of the ROM one should use with this Kernel? The ROM I'm running was last updated back in March so I am unsure if any new CM features were implemented or removed from the kernel since that time and I would rather not be stuck in a boot-loop or nothing. The kernel I'm currently sporting is "3.0.101-DIABLO-3.3". You say yours is based off of Diablo 3.1, so I THINK it should play nice with this ROM, but I'm nervous I'll soft-brick my phone.
Is there a reason you didn't use Diablo 3.3 as the base?
Also, your OP states there are screenshots, but none are included? I don't need them (kernels don't really need screenshots, eh?), but just thought I'd point it out.
Thanks for being one of the ones keeping the t989 alive.
EDIT: I'm dumb... just saw the screenshot tab at the top. 18 hours on battery is pretty good. I get about 10 with how I have things set right now, so getting an extra 8 would be awesome.
Click to expand...
Click to collapse
It'll work fine with older KitKat builds.. And I don't think you'll have compatibility problems with using it with a ROM that came with a newer version of Diablo. I was at one point using older builds of Cl3kener's kernels on newer builds...
Sent from my Carbonized GS²
suaverc118 said:
Thanks bro for doing this. I will flash and report
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------
Emmanuel, do you recommend CPU tuner or trickster or just stock performance to tweak settings?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will always recommend the stock performance app as it's apart of the system so you know for a fact it won't be holding any child proccesses which may effect battery etc.
mp3deviant721 said:
Just flashed it on Carbon 5/21. Initial thoughts are that it seems to get to the boot animation quicker than Uber. But initial reboot is long... I thought my phone was stuck in a bootloop... Also does not kill vibration after subsequent reboots after the initial reboot after flashing the kernel. It's just as quick as Uber and seems to work with Kernel Tweaker. This kernel also won't crash the phone playing 1080p in portrait... Love the fact that this kernel has sleep2wake as well. Will report back after using it for the day...
Any chance of a 2ghz version? And does this work with PAC outta the box?
Edit: Forgot to say thanks for giving us another kernel for the good ol' Herc. So, thanks.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes it should work out of the box with ALL KITKAT roms. As for Jellybean and before I'm not 100% sure as they may and most likely use different ramdisks. Also I doubt you will see me push out a 2ghz version as I don't really like to OC, but when I do I like to stay in the OC 300-400mhz stage. Once getting above that you risk damaging your hardware overtime which can stunt it's life.
suaverc118 said:
Not sure if its kernel related but after rebooting my phone because of play store issues. After rebooting, I lost all of my widgets that I placed on 4 screens.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How many times did this issue occur to you? Did it happen right after kernel installation? Because it's sounding more like a rom related issue.
After about 12hrs into it, video recording added a nonstop buzzing sound in all video res. Reboot fixed the issue. See catlog. I am currently on AlpineRom.
Emmanuel U said:
Yes it should work out of the box with ALL KITKAT roms. As for Jellybean and before I'm not 100% sure as they may and most likely use different ramdisks. Also I doubt you will see me push out a 2ghz version as I don't really like to OC, but when I do I like to stay in the 300-400mhz stage. Once getting above that you risk damaging your hardware overtime which can stunt it's life.
Click to expand...
Click to collapse
I meant all older builds of KitKat ROMs. My bad. I didn't claify. I'll edit my post. And I thought I'd ask about 2ghz, it was nice when I had it...
Sent from my Carbonized GS²
woot
a wild kernal appears
Is Hyper supposed to stay a higher frequency on Core 0 when you are playing music or running an app and not doing anything else and with the screen on? I'm currently set at 1836/192 and the frequency settles more at 756 on Core 0. If I set minimum to 384 then it seems to settle more on 384. I couldn't find much info on how Hyper works so I'm just wondering if this is normal.
Sent from my Carbonized GS²
Something went very wrong....
About an hour after installing this kernel last night I picked my phone up off the table and noticed it was in a boot loop.
I went into recovery and wiped the cache and it eventually booted to the CM-11 Welcome screen asking me my language preference.
I rebooted back to recovery to restore from my backup and (long story short), I couldn't because the partition table on my external sd card has been destroyed. I don't know what would have done that I wasn't actually using the phone at the time.
Sorry I don't have logs, but if anyone knows how to recover an sd card with no partition table i'd love to hear about it. I tried gpart/gparted with no success. I assume the partition was some kind of FAT but I don't know for sure.
Last night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
sfleury said:
About an hour after installing this kernel last night I picked my phone up off the table and noticed it was in a boot loop.
I went into recovery and wiped the cache and it eventually booted to the CM-11 Welcome screen asking me my language preference.
I rebooted back to recovery to restore from my backup and (long story short), I couldn't because the partition table on my external sd card has been destroyed. I don't know what would have done that I wasn't actually using the phone at the time.
Sorry I don't have logs, but if anyone knows how to recover an sd card with no partition table i'd love to hear about it. I tried gpart/gparted with no success. I assume the partition was some kind of FAT but I don't know for sure.
Click to expand...
Click to collapse
That happened to me a short while back using A different ROM and kernel. For me, my sd card died and I sent it back under warranty.
Sucks cause you lose all the data and no way to recover but if you can warranty it,I would.
Sent from my SM-T310 using XDA Free mobile app
bmg002 said:
That happened to me a short while back using A different ROM and kernel. For me, my sd card died and I sent it back under warranty.
Sucks cause you lose all the data and no way to recover but if you can warranty it,I would.
Sent from my SM-T310 using XDA Free mobile app
Click to expand...
Click to collapse
Ya I suspect the card has failed based on how it is behaving in my computer. I will look into warranty but I'm not very good at keeping the paperwork for such things.
sfleury said:
Ya I suspect the card has failed based on how it is behaving in my computer. I will look into warranty but I'm not very good at keeping the paperwork for such things.
Click to expand...
Click to collapse
I'm not either, but if you know where you bought it from (online sources are usually the best as you will have an email receipt) AND you have an account with them, they MAY be nice and pull your receipt up for you. Sandisks warranty info though states that you need to have your original receipt AND the original packaging. When mine died they were happy enough with a photocopy of the receipt being emailed to them and they didn't need the original packaging.
It sucks when it does die because you lose your data and you don't know if it was due to the new stuff you were trying or simply a fluke. I've been meaning to try my new stuff again on my card (moving /data to external storage), but I'm nervous that that is what killed it. It gave me a nice performance boost (surprisingly), but I only got about 2 months before things died for me
Now I back up my SD cards roughly once every 2 months just in case one dies on me again. Well, unless I make no changes OR I only add stuff I can re-download easily.
Boot loop for me, using the latest Pac Man nightly...
ricthot said:
Boot loop for me, using the latest Pac Man nightly...
Click to expand...
Click to collapse
Same here dude.. Cannot change governor or phone will freeze and then go bezerk...boot loops etc. Will not work on alpine or carbon for me
Nice, new kernel. Something to play with this weekend.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app