Related
After the rather...disappointing way I departed and the resulting issues, I'm setting some things straight here and now.
1. No ETAs. Period. I don't want to see when will I fix or add anything.
2. No complaining. There's a line between reporting an issue and complaining. This line is crossed when it's reported more then once.
3. Requesting additions is fine, within reason. Keep it within reason, I'm not a real dev.
4. Using this ROM...this is where a lot of issues have come up, generally speaking, you can use this ROM as a base if you choose, however ASK ME FIRST. That's it! Everything could have been avoided if people had simply asked me before using my ROM and slapping their names on it then putting it out there. Please include some credit to waydownsouth, gh123man, randomblame and myself. For 4.3 Jellytime, randomblame in particular.
5. Hosting/mirroring. Please don't host or mirror this elsewhere, I will supply hosts for this ROM, I don't need more, and I prefer to keep track of how many users of a given build I have. Hosting elsewhere interferes with this. The only exception I can see is for our Russian/Ukrainian user community, my hosts may be slow there, or in other parts of the world. If you wish to host for another country, please let me know.
6. READ. For the love of all that is holy and great, READ the OPs, read at least the page before where your post will be. I will not answer questions already answered. If I respond, it may not be the nicest way I could do so. Please, save me, yourself, and everyone else the time and /facepalming and at least attempt to find the answer on your own. This is not limited to only this ROM, but anything you may wish to post about in this thread. Questions about CWM or TWRP don't belong here, but if they are valid questions that have something to do with this ROM, go ahead, after reading up on it.
7. Remaining on topic....well this one is loose. I prefer it to stay related only to this ROM, however I know things stray, and generally I'm OK with this, just try to keep it at least related to android. Or at least something related to something to do with on this planet.
Features:
Halo
PIE
Listview Animations (settings>display)
System Settings (CM)
Screenies:
Builds
Jellybean 4.1
Build 1 | Mirror
Kuroikaze-Sosei RC1
Kuroikaze-Sosei II B3 Final
Jellybean 4.3
Jellytime 4.3 - AFH | Jellytime 4.3 - DH
Gapps 4.1
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Gapps 4.3
gapps-jb-20130813-signed.zip
Change log 4.1
Build 1: Updated to 4.1.2 sources. Generally stock CM10. Everything works. I think.
RC1: Based on Black Bean AOSP sources now.
Sosei II B3 Final:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
Final release.
Change log 4.3
Ported from Randomblame's Jellytime Build 7
Build 1: Unreleased, initial trials to get it running. Bootloops.
Build 2: Unreleased, boots, but runs badly, storage is broken, audio stutters
Build 3: Almost everything works now, fixed storage via init/ramdisk entries
FULL WIPE NO MATTER WHAT
Broken in 4.1
RC1 -
Auto Brightness
Hardware Rotation Lock Switch (use software settings, it's more flexible anyways)
GPS
Fixed -
HDMI audio should now work (again)
Switchable UI (tab or phab UIs now)
Bugs-
In tab ui the clock is messing it's rear texture on the homescreen, ie its not black there, its wallpaper instead. Doesn't interfere with anything, just a glitch.
Huge thanks to justjackyl for testing this out for me and reporting back on issues.
FULL WIPE NO MATTER WHAT
Broken in 4.3
Mic
?
Untested:
GPS
HDMI
Bluetooth
Dock
Bugs:
WiFi will not reconnect if it turns off, a reboot is needed. Turning off the always scanning option seems to help this.
Forcing GPU acceleration can help even out the framerate in some cases.
4.1 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. Get one for JB, you can try a 4.2 package, but is as yet unsupported.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Feel free to flash any kernel you want, but don't post about problems here until you use the kernel it came with first.
4.3 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. 4.3 ONLY! Don't report anything if you use anything but the gapps I linked from my site.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE Don't report ANYTHING if you did not flash 100% clean!
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation. It may blank out for awhile on the first boot, just leave it be.
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
I strongly recommend you download and install apps FRESH from the Play Store, and do NOT restore apps if possible. If you want, then go ahead...
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Do not report any issues if you:
Dirty flashed.
Restored anything with any app.
Don't use the supplied kernel.
Modified the ROM in any way prior to the issue coming up.
Did not read the entire post and noted what bugs are already known to exist.
Did not use the 4.3 GApps on my site which I linked right below the ROM download.
Can not report a bug issue without quoting Hawkeye because you skipped all of this.
Thanks:
waydownsouth
randomblame
gh123man
godmachine / linux society
justjackyl
das_webos_transformer / xbooow
Cyanogenmod
AOKP
Team Baked
The Team behind the AC!D audio engine
Plus more, I'm sure.
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
cdkg said:
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
Click to expand...
Click to collapse
Roflmao so says my biggest donater!
Sent from my SGH-T989 using Tapatalk 2
You are the freaking man!
Sent from my A100 using xda app-developers app
Go for it.
You sir, are why I miss my Iconia A100 . Hopefully can get a new one soon, miss the A100 community
Sent from my SCH-I500 using Tapatalk 2
A big thank you !!!!!!!!!!!!!!!!!!!!!
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
rockthegod said:
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
Click to expand...
Click to collapse
Thanks, and welcome to our little corner of XDA! Hope your new tablet is as good as mine has been to me
But really guys, randomblame did the hard work on this. I just got it running on the A100.
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
wild1z said:
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
Click to expand...
Click to collapse
Thanks for the understanding.
Also....new version with WiFi and some sound is up. Root seems to work to a point but I'll say its broken for now.
tapatalked from my A100 - Jellytime V7.7
unbelievable, I am bewildered by this topic! fantastic!
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
xitrumch said:
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
Click to expand...
Click to collapse
Thank you for the kind words, and no I'm not offended, there are certainly much better developers for sure, as I don't really consider myself a developer anyways. Most of this work has been done by randomblame and waydownsouth I just move it over for us on the A100, which isn't always easy I'll admit.
Version 7.8 is now available
Change log:
Root is now working as it should.
Open Super SU
Let it "install" binary (its already there)
Enjoy
External SD is now RW:
Fixed a permission issue in platform.xml to allow full read/write to external_sd.
Brightness control now works:
Auto brightness doesn't seem to work, manual brightness works. This was actually fixed in a previous release, and broke again, and is now working again.
Sound:
Sound works in some apps, but system sound is still broken, ie notifications, music, but some apps/games work, like angry birds now has audio.
Bluetooth:
Bluetooth has been proven fixed by a pairing, testing done by ntan97.
Still Broken:
Gallery/camera
Internal SD doesn't mount
Power LED is erratic, sometimes always on, sometimes always off
Home to wake: works when power led is ON, doesn't work while it is OFF
Video playback is still broken. Tested on stock player, dice player, mp4 and avi.
I'll be redoing the posts to be a little less confusing by moving things to change logs like this.
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
notsointeresting said:
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
notsointeresting said:
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
Click to expand...
Click to collapse
Yeah not a bug, that's the new 7" UI jellybean uses. Not sure why they killed the combined bar and chose a phone UI though. That's how the N7 will look too.
Oh edit there is a jb gapps but they're kinda broken, so flash them, ten icss gapps over it and itll work, that's how I do it. I'll add them into the OP sometime today, niece and nephew are staying with us for a few days so I'll be busy being the coolest uncle ever with all my modded consoles, devices and toys lol
tapatalked from my A100 - Jellytime V7.9
pio_masaki said:
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
Click to expand...
Click to collapse
Bit off topic... but woah, thanks man. Just donated 5€
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.
Reserved
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.
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
What is this:
This is Stuxnet a custom kernel for Android, this kernel focuses on simplicity and stabiilty. All features on this kernel are based on long hours of testing and all are thoroughly tested to give end users the best experience for their device.
Stuxnet is mostly stock with optimizations and features that are often used by users that are not affecting performance on their device. Future development of this kernel will focus on Performance and Stability.
So enough with the intro and start testing this on your device.
Features:
Based on Xiaomi kernel source
Fully Optimized Kernel
Sound Control
FSYNC Control
Voltage Control
MSM Hotplug
Thermal Enhancements
USB Fast Charge
Check Github and/or Gitlab for full changelog
How To's:
Install in recovery
No need to wipe (unless you want to wipe your a$$)
Reboot
Kiss yo' mama
***** Slap an iPhone user.. Smile!
Enjoy
Credits:
Google
CyanogenMod
Linux
SimpleAOSP
and all custom kernel devs
Download:
CM
MIUI
Kernel has two builds Stable and Nightlies
WARNING!
This kernel is only compatible on CM based ROMs.
~End
Donations:
@morpheus620 - $15
@gary138.138 - $15
@Riichard63 - $20
Thanks man!
Will test it soon! Sorry for the Noob question but can you tell me if it can be used for building cm11. I am a noob in android development.
I'm using this at the moment on XenonHD. So far everything is working. And that smoothness....its off the charts! xD Btw Dev @Gnome, can you add Lionheart and Sio on the next release?
And LCD KCAL please.
Gnome said:
One More!
Click to expand...
Click to collapse
Thanks
Sent from my MI 3W using XDA Free mobile app
I just flashed this kernel on the XeonHD 4.25 build.
Hoping that they are good partners.
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Gnome said:
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Click to expand...
Click to collapse
Ooohh yeaahh! E. A. G. E. R. L. Y waiting. XD
Working on Bitti09's CM12.1 confirmed
No new governors yet! Waiting!
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Thanks a lot, @Gnome!
Jhayzt said:
And LCD KCAL please.
Click to expand...
Click to collapse
+1
I used KCAL controls on StellAR and the difference was AMAZING! (alas StellAR doesn't gel with XenonHD for me)
SharksT said:
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Click to expand...
Click to collapse
*Resurrection
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
The Dork Knight Rises said:
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
Click to expand...
Click to collapse
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
sudy_freak said:
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
Click to expand...
Click to collapse
Yeah, call bug v1 is something most ppl who recently joined the Mi3 forums won't have faced.
It is one of the major bugs (aside from deep sleep reboot) that was there in the original Lollipop ROMs for cancro. It was fixed a long time ago (by audahadi and Bitti I believe, as Ivan's ROMs had the bug for a long time afterwards too).
The bug was that the touchscreen would remain active when you're in a call and the proximity sensor turns the screen off. It would cause the notification/quicksettings panel to be pulled down or brightness to be changed due to contact with ear or cheeks. Other more complex things could also happen like when I once turned on Airplane mode while talking and got disconnected :laugh:
And call bug v2 is a new bug that seems to affect ROMs (except I believe Ivan's AOSP and SOKP which switched to Ivans kernel I think) since 5.1...
While calling (or sometimes VERY RARELY while doing something else) the phone kind of hangs, the screen goes dark and it goes into a screen of death mode. Nothing can be done, your only option is to press and hold Power button for a very long time (approx 12-15 secs; much longer than a normal hard reset ~8secs) to hard reboot your phone.
Hope you got it. :good:
PS. Yes, try this kernel. You won't be disappointed.
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Thanks Dev @Gnome! I'm trying it at the moment.
Wow, using alpha 3 working great even on temasek 10.6 by moonlight, just waiting another hotplug, IO Scheduler, CPU & GPU Governors, btw can you make a little downclock and overclock cpu freq tables? Thx for great kernel....
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Fast charge!
Very useful!
I'll try this asap.:laugh:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
ZenR2 said:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
Click to expand...
Click to collapse
dont mind the Lettered version, just flash the numbers.
Gnome said:
dont mind the Lettered version, just flash the numbers.
Click to expand...
Click to collapse
buddy flashed the alpha 3 build , but now wifi is not working on latest Xenon Hd rom
Hello all.
Those of you who know me know I would never report an issue without logs, but I'm in a financial position that doesn't give me the ample time to research.
4 custom ROMs (remain unnamed to avoid problems) all would eventually lock the big or small cores (never at the same time) at their max frequencies. It's easy to miss but I noticed it occurring within many different contexts.
I even did clean flashes of each with no additional apps and using the nano/Pico gapps packages.
Others have pointed to Google play services eating up a significant chunk of battery. I want to believe it's a gapps issue, but even with built-in gapps packages, I still eventually will lock at 1900 or 2400 on one of the core sets.
Hmp, EAS, doesn't matter - I end up with the small cores locking at 1900. If you wait it out sometimes the frequency settles, but OOS is the only place where this 'bug' to occur.
Thanks xda buddies.
Plz move to questions and answers if necessary. I just wanted to get a feel for discussing bugs without explicitly naming the ROMs in question.
If someone has a legit solution or knows of a magisk module that might be f**king me over... please give me your wisdom.
I dont have anything like you stated and yet i have tried many roms in a single month. Im not saying you are lying but there are hundreds maybe thousands of people using custom roms and people dont state such an issue.
I had the same problem on my s9+ and it was due to kernal manager application which is Mtweaks app. Then i have changed to ex kernel manager and didnt see it locking at max frequencu.
Oos might have problems, as i dont use it so often. But like you have said you tried 4 diffrent custom roms and saw the same behaviour.
Sent from my OnePlus 5T using XDA Labs
---------- Post added at 03:01 AM ---------- Previous post was at 02:55 AM ----------
I play games a lot and i like testing custom roms with diffrent kernels to see what kind of performance i can get. I have played almost 1 hour of pubg with weeb kernel on DerpFest, as you can see 45 mins on big and 15 on little which is normal. Other than that everything is working fine on my end. Maybe it depends on the kernel you are using? Best thing i can say is check your apps, maybe you have a malware in your device? Check wakelocks and alarms, kill social apps(especially sh*tty facebook apps)[as you have said clean flashed with no apps]. Maybe you have done it already? My best bet would be using unbrick tool and flash ota updates one by one.
Crdroid derpfest treskmod lineageos coltos aex krieg pixel experience theone5tos and many more... Didnt face any issues like you did. Not to mention that i have f*cked up my phone manytimes by messing with sgis and the ones that modifies vendor, hard bricked many times, still didnt have any issues like that.
https://ibb.co/YQYgcnL
Only thing that comes to my mind is either your device has hardware issue or you are doing something wrong. 4 diffrent roms plus oos and experiencing same issue is not a coincidence.
Or you can just grab a log from any logcat app and someone can take a look at it?
Sent from my OnePlus 5T using XDA Labs
Here is a ss after 15 mins. In this time line, almost 2 mins on big and 5 mins on little have added. And it is normal because i was doing stuff for these 15 minutes.
Sent from my OnePlus 5T using XDA Labs
Usually when U flash a rom or update the CPU will be locked at 100% for like 5 min ish. This is normal. So let it settle and it should be good. I'm using ex kernel manager on derp but all other ROMs have been fine. I'd recommend aex or derp. Cnp I would stay away because no open source kernel etc.
Been getting 6 hr sot on derp with a almost 2 year old phone. Stock settings
gsser said:
Here is a ss after 15 mins. In this time line, almost 2 mins on big and 5 mins on little have added. And it is normal because i was doing stuff for these 15 minutes.
Click to expand...
Click to collapse
For me it happens despite activity, I can camp out on OOS until I feel like leaving again. I formatted my phone a few times, so I can only try again. If it happens again I definitely will have logs.