Related
[ 02/09/2012: Screen Flicker / Brightness is an issue. I'll be looking at it. ]
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time and built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Moving forward into CM9/ICS, some changes need to happen to the kernel over time. The migration kernel is found in a branch: "L27.13.1-ICS". The END result of this will be a kernel / source that fully support hw codecs for ICS.
[02/08/2012] FLASH ZIP FOR THOSE RUNNING NIND'S BUILDS: http://bit.ly/xYOf0V
The following ROM is built from the sources at GitHub under the KFire-Android org. Many of those files and configurations are the result of countless hours of development by JackpotClavin. I don't want there to be any confusion as to who put in a ton of time getting this to work.
[02/09/2012] FULL ROM INSTALL: http://bit.ly/ygVvQB
Changelog:
- Screen flicker IS an issue right now. Digging into it
- Touchscreen "Slop" set to 16. This should help touches register on the touchscreen.
- Working Data usage stats (xt_qtaguid / xt_quota2 kernel modules)
- TUN, CIFS support
- USB mounting fixes
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
nind said:
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
Click to expand...
Click to collapse
If you want to follow a very good step by step guide for setting this up the same way TI (the CPU maker) intended, then follow this:
http://www.omappedia.com/wiki/PandaBoard_L27.12.1-P2_Release_Notes#Setting_up_build_environment
Obviously, that's for PandaBoard, but the Toolchain source and setup are very good.
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Hashcode said:
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time nd built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter2_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Tonight, I'll go back to both of my in-progress kernels and do some testing to see if they'll boot.
EDIT:
Current issues being looked at with this kernel:
- Power off doesn't really power all the way down. It goes to a black screen, but requires long press to turn off.
- Deep sleep isn't happening. The backlight is on a tad while the screen should be off.
But this config is still MUCH better than trying the original.
Click to expand...
Click to collapse
So does this boot cm7 or anything? My kernel builds boot stock kindle but not cm7
Its something to do with netd/dnsproxyd. Just finding a fix that works is a PITA common issue, but then people dont say how they fixed it..
Right now ive only tested this with CM9
Sent from my DROID RAZR using XDA App
touch points
Any chance you're looking into enabling more than 2 touch points in this kernel?
foxdog66 said:
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Click to expand...
Click to collapse
I'm running nind/sitic's cm9-02-04 build with this kernel baked in. I, too, have Stay Awake disabled in Developer Options, and my Kindle is going into deep sleep. I am experiencing the power down issue, though.
It's something I'm absolutely willing to live with for the time being. This is good stuff. Thanks Hashcode!
jabdo79 said:
Any chance you're looking into enabling more than 2 touch points in this kernel?
Click to expand...
Click to collapse
Thats really the future of this kernel. I needed a solid base to start from.
Sent from my DROID RAZR using XDA App
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Right now the difference between this kernel and stock is:
- About 8 ip6 netfilter modules were added
And that's about it.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
wdfowty said:
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
Click to expand...
Click to collapse
ill look into insectraven's cm kernel thanks!
Edit: That worked! Thanks!
he starts the dnsproxyd differently than what I've seen. But it works!
So I noticed that /mnt/ is mounted read-only which causes issues with apps installing to the sdcard and probably the issue people are having with mounting the sdcard to the computer. Some apps insist on installing to the sdcard (I hate that)
Edit: or do I have this all wrong? Lol I'm no dev remounting it r/w gets the job done.
Is there any websites or anything that you guys would recommend to learn about the Linux kernel and development of it?
Tonight, I went back through and cleaned up my config some more. Removed extra power controls, usb mtp settings and omap mmc host controller (for sd card slot boards).
From my tests, everything deep sleeps correctly and the power off issue is fixed.
https://github.com/KFire-Android/kernel_omap
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
foxdog66 said:
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
Click to expand...
Click to collapse
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Hashcode said:
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Yeah that's cool.
foxdog66 said:
Yeah that's cool.
Click to expand...
Click to collapse
Here's an updated boot.img for nind's 2/5 build:
[ UPDATED OP W/ FLASH.ZIP FILE ]
STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
Flash with the following adb commands:
Code:
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img
If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
Mirror 1: Download (Goo.im)
BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.
STEP 2: DOWNLOAD A BUILD OF CM11.0:
DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM
NIGHTLIES:
http://download.cyanogenmod.org/?device=otter
GAPPS (Use Version "CM 11" row):
http://wiki.cyanogenmod.org/w/Gapps
Older builds are found here:
http://goo.im/devs/Hashcode/otter/cm10/
http://goo.im/devs/Hashcode/otter/cm10.1/
http://goo.im/devs/Hashcode/otter/cm10.2/
GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip
CHANGES:
[05/15] More audio updates to fix low-power states (screen off / background music)
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w/ SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
KERNEL FEATURES:
[08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
Many bugfixes pulled down from TI's omapzoom sources.
RESERVED FOR NOTES
XDA:DevDB Information
Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-01
Last Updated 2014-05-21
UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1
DEVELOPER BUILDING:
Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
Patch 1: http://review.cyanogenmod.org/#/c/53917/
Patch 2: http://review.cyanogenmod.org/#/c/54562/
And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
Won't get a decent build till that's all done.
KNOWN BUGS:
1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
6. Headset recording via the MIC input jack doesn't work
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.2)
repo init -u https://github.com/CyanogenMod/android -b cm-10.2
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter
FINALLY!
I'll see if I can help with power button LEDs.
*out-of-topic note: 3rd post!
1. The backlight doesn't sync up well with the screen. Meaning that sometimes when you bootup you won't see anything but a black screen. Once the boot is done, you can hit the power button a few times and eventually the screen and backlight will sync up and you'll get a picture.
Click to expand...
Click to collapse
I can't even get a picture.
animefun135 said:
I can't even get a picture.
Click to expand...
Click to collapse
Power button four or five times, and it'll pop up.
Edit: not having the sync issue in HC, hash, do you have the log posted on your site regarding the back light issue? I know its kernel related but 3.2 is a lil more cumbersome, so it could just be OS lag. Are we using 4.0.3 or 4.0.4?
Sent from my MB860 using XDA
Power button four or five times, and it'll pop up.
Click to expand...
Click to collapse
I tried 30+ times.
Nice job Hashcode.
Sent from my PG86100 using Tapatalk
I don't have time at the moment to pull down the sources and poke around for myself, but it sounds like #4 is a script issue of some sort.
Either one of the scripts that needs to fire for shutdown is hanging up, or the output isn't returning properly so that the master script can continue and finish pulling it all down.
If I get a chance tonight, I'll grab the sources and poke around a bit.
I deal with hanging/incorrectly-terminating script **** at work all the time, so now I might even be able to contribute, yay!
Reserving this for a complete description of the backlight driver/issue and related sources for research.
Sent from my DROID4 using XDA
Hey Hash I wanted to let you know that the charger does work for me. I don't have to boot back into twrp. Don't know if its just me or what but it works.
Edit: Didn't see that you had put its not working well instead off not at all, I'll do some more testing to see if it will give me problems. So far plugged it in about 20 times and its registering the charge.
Sent from my Amazon Kindle Fire using XDA
Let me be the first to say "Does Netflix work with this?"
Just kidding, things are coming along it appears, wish I knew more about hacking kernels, last time I did anything with a kernel I ran "make xconfig"
i just get a lit up black screen 0.0??
symbiiote said:
i just get a lit up black screen 0.0??
Click to expand...
Click to collapse
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
isaiahhhhh said:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
Wait, are you talking about things like large grey rows of pixels appearing on the screen? Sometimes I see gradients of monochromatic tones in addition to this. They only appear as the backlight is shutting off.
isaiahhhhh said:
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
your right, sorry, as for the rom, i noticed when i flashed hashcode's rom then reloaded rom over it youtube worked in HD, and that got me thinking, you think we can get a Flashable ZIP of the kernel?
is this the kernel that everyone was waiting for? 3.0?
@shahabk818
YES!
But it's still in development, so not for daily use!
TuikS2 said:
@shahabk818
YES!
But it's still in development, so not for daily use!
Click to expand...
Click to collapse
so this will fix the hardware acceleration problem, right?
shahabk818 said:
so this will fix the hardware acceleration problem, right?
Click to expand...
Click to collapse
So you can't read the title, right? [WIP][KERNEL][DEV-ONLY] 3.0 Kernel Development for Kindle Fire [04-10]
DEV ONLY!
OK, so compiled an aosp last night from the CM9 tree... I'm still not having a back light issue? Can't adjust brightness, but no sync issues. Could it be the ROM?
Sent from my MB860 using XDA
Known bug list and known work arounds are in Post 2, at the bottom, below the instructions. Please if you read nothing else, read post 2, and report anything NOT already listed there, thank you.
WeeFeeri was kind enough to take the time to make a video showcasing these CM9 nightlies (featuring Build 46) so check it out HERE! Please be sure to give him your thanks for the taking the time to do this on his own!
As per notsointeresting's suggestion, and a few complaints of dev-host's reliability lately, I setup androidfilehost to hold my stuff, I'll be slowly migrating everything over for use as a mirror.
I'm writing a general guide for the A100, please give it a read if you have any questions. Its a WIP, but is full of goodness, I promise! Guide to all things A100
Since there doesn't seem to be any nightly releases for A100 CM9, I decided to build them myself for myself, then figured, hey, if I build them, why not let others have at them? And with that I present to you....
CM9 Nightlies by pio_masaki
What is a nightly vs whatever release?
Nightlies are untested and considered unstable, however they contain all of the latest source code available. This means things may be fixed, things remain broken, or new things are broken. It also may mean its your new favorite daily driver rom.
What do you do to this rom?
Nothing at all. I only compile after syncing to the repo daily. This is not modified by me in any way, shape or form, completely stock vanilla CyanogenMod roms.
How often will you release these?
Whenever possible I plan to release these nightly, or once a day. I'm sorry if I miss a day or two, I will build and upload when I have the time. I do NOT have time to test each one, so that will have to be a risk you take. This first build boots and runs, I do not know of any bugs or what works or not.
What about bugs?
I don't know, please tell me in the thread and I will add what is broken or fixed to the post. Posted at the bottom of post 2 for now with work a rounds if known, dated with build number reported.
What does the filename mean?
the file names will be in this format: cm-9-6-11-B1-a100-PM.zip
here's the breakdown:
cm-9 is of course, its a CM9 release.
6-11 is the date of the build.
B1 is the build number, tomorrow will be B2, so on. If there is a B1-2 that's a second build for the same day. Not likely, but just in case.
a100 device model this is meant for, please don't use this on another device.
PM is pio_masaki.
Source
Source is directly synced from CM, nothing is added by me. Kernel is directly from ezterry, in his original zip file release, nothing added by me.
Thanks
Thanks to the CM team for doing awesome work to get this kind of stuff to most devices possible!
EzTerry for making an OC kernel for our devices!
da-pharoah for letting me bounce ideas off him and letting me work things out through him and cheering me on for this.
x0hell0x for inspiring me to decide to attempt compiling from source.
Downloads
Theme:
EpicBlueCM9 Theme courtesy of stetsonaw! Be sure to give him your thanks!
Add ons:
ezterry's OC kernel Thread, Please read it all!
Required for Play Store and other Google stuff/framework:
gapps
Optional scripts for wiping:
Blackhole Wipe/Nullifier Thread
Experimental CWM Touch Recovery:
This is an experimental build! Use caution with this!
Removed as it seems pretty broken.
If it works out OK for anyone willing to try it out, I'll do a formal release for it later.
Builds:
Build 6 6-16-12
Build 7 6-17-12
Build 8 6-18-12
Build 9 6-19-12
Build 10 6-20-12
Build 11 6-21-12
Build 12 6-22-12
Build 13 6-23-12 *experimental* (new build machine) Has issues lol skip it.
Build 14 6-24-12
Build 15 6-25-12
Build 15 Experimental
Build 16-2 6-26-12 *see note below Update section*
Build 17 6-27-12
Build 18 6-28-12
Build 19 6-29-12
Build 20 6-30-12 We made it! 20 straight!
Build 21 7-1-12
Build 22 7-2-12
Build 23 7-3-12
Build 24 7-4-12
Build 25 7-5-12
Build 26-4 7-6-12 Had multiple build fails, sorry it's so late.
Build 27 7-7-12
Build 28 7-8-12
Build 29 7-9-12
Build 30 7-10-12 | Mirror
Build 31 7-11-12 | Mirror
Build 32 7-12-12 | Mirror
Build 33 7-13-12 | Mirror
Build 34 7-14-12 | Mirror
Build 35 7-15-12 | Mirror
Build 36 7-16-12 | Mirror
Build 37 7-17-12 | Mirror
Build 38 7-18-12 | Mirror
Build 39 7-19-12 | Mirror
Build 40 7-20-12 | Mirror
Build 41 7-21-12 | Mirror
Build 42 7-22-12 | Mirror
Build 43 7-23-12 | Mirror
Build 44 7-24-12 | Mirror
Build 45 7-25-12 | Mirror
Build 46 7-29-12 | Mirror
Build 47 7-30-12 | Mirror
Build 48 7-31-12 | Mirror
Build 49 8-1-12 | Mirror
Build 50 8-2-12 | Mirror
Build 51 8-3-12 | Mirror
Build 52 8-4-12 | Mirror
Build 53 8-5-12 | Mirror
Build 54 8-6-12 | Mirror Note - the file names are wrong, I was to lazy to reupload them, this is the correct info, ignore the file name.
Build 54 8-7-12 | Mirror
Build 55 8-8-12 | Mirror
Build 56 8-9-12 | Mirror
Build 57 8-10-12 | Mirror
Build 58 8-11-12 | Mirror
Build 59 8-12-12 | Mirror
B60 8-13-12 | Mirror
Build 61+ are now on Goo.im and can be accessed through the goo.im app. Even will tell you when the new nightly is available for you! For now I'll just be updating the thread Build number and date, I won't be linking anymore.
Build Notes
Build 16 is a sort of mile marker, rotation lock fix got merged today! I had already synced and built Build 16, however (and I announced it over twitter for those that care) scrapped it in favor of adding the newly merged Rotation Lock fix! Luckily I was sitting around in #Iconia-dev when it was announced. So, please test rotation lock and report back if its working or not for you guys!
Instructions
Fresh install from another rom:
Download to your external SD card
Reboot into recovery
Backup current installation
Wipe data, system, cache, dalvik cache (optional use my Blackhole scripts)
Install from zip, pick the CM9 zip
Flash gapps
Once done, wipe cache and dalvik cache again
Reboot system
Wait 10 minutes, then reboot system
Log into google and setup your device
Enjoy
Updates from my previous builds:
Backup current installation
Flash the new build zip
Clear cache
Clear dalvik
Reboot
Let settle 10 minutes
Reboot
Enjoy.
Only for updating over a previous PM CM9, not meant for flashing over any other rom, even another CM9.
Advanced update method:
Backup your current PM CM9 install you wish to update
(CWM) Go to mounts, mount /system, then go down to format /system
(CWM) wipe data
(TWRP) Go to wipe, wipe system and data
Install newer PM CM9 version
Install gapps
Go to restore, advanced restore
Restore ONLY Data
Clear cache and dalvik, fix permissions
Reboot system
Let settle 10 minutes
Enjoy
This method will clear the system partition and replace with the new system, but restores your user data, settings, apps, etc. Its IMO a cleaner upgrade method then "Dirty Flashing" straight over the previous rom. Intended ONLY for updates from a previous PC CM9, no other roms.
Current known Bugs
6-11-12, B1: You have to disable the screen off animation or your device will reset everytime you press the power button. Settings>Display> Uncheck Screen-off animation prevents it.
6-12-12, B1: Labros1995 reports rotation lock still broken.
6-16-12, NA: HDMI audio still not working, reported by pomka78
6-19-12, B7: labros1995 reports Torch Toggle does not work, volume is upside down in portrait mode (still uses landscape default layout).
6-29-12, NA: Its not really a bug, but it has come up, themes DO work, however complex themes will give a compiled error. For now, only simple color changing themes work, such as the Holo series of themes. I don't think its the ROMs fault, I think it has to do with the themes not being for Tablets. But, I added it here anyways, as a heads up.
7-1-12, B20: nickownzya reported Chrome crashes going into settings, confirmed by mapaz04. Turns out its the newest version, 18.0.1025.166 (Official Build 130050), confirmed by mapaz04. Chrome version 18.0.1025.133 does not appear to have this issue. The only fix for now, if possible, is to uninstall the update. Not possible on a freshly downloaded restore, but maybe through TiBu or whatever backup app you use. Chrome appears to otherwise function fine, just can't enter settings.
Updates:
6-13: Modified the OPs a little bit, added advanced update instructions in post 2. Added bug list location to post 1.
6-25: Added CWM Touch experimental to downloads, added some whatever info. I dare you to find it!
7-2: I've put my A100 up for sale today, but I will continue building these nightlies until the official nightlies begin rolling out, as promised.
7-2: Added a new link to the downloads section of post 1, EpicBlueCM9 theme by stetsonaw, which he confirms working for our devices!
7-4: Removed builds 1-5 as I'm sure they are no longer needed, and they were using dropbox anyways. All builds now on Dev-Host.
7-4: As the new title states, I've been working on my custom edition CM9, some build.prop tweaks, some init.d tweaks, some free apps that I generally use. It was originally going to be a pre built restore for myself, but I figured, as always, why not share it? Should be available in it's alpha form tonight or tomorrow. Still a LONG way to go on it!
7-6: The custom edition is going a little slower then I expected, hitting a couple of road blocks with the modular expansion I had in mind for running scripts, but it's getting there. cdkg has offered to test run today's alpha, so hopefully that goes well. I can't test stability since I'm constantly flashing new crap to the build, or entire new builds, that I never spend more then an hour on any flash lol. It's coming, eventually. If cdkg doesn't run into any issues I'll put up the alpha 1 build.
7-8: For those that haven't noticed, and the few still that read this section, (does anyone read here?) the custom edition is availble in the Dev section as of this morning, Aoikaze Alpha 3, please give it a whirl and report any issues you may run into, if any (because I'm perfect and all).
7-9-12: As per notsointeresting's suggestion, and a few complaints of dev-host's reliability lately, I setup androidfilehost to hold my stuff, I'll be slowly migrating everything over, then using dev-host as a mirror.
7-25-12: I'm taking a short vacation, I leave the morning of 7-26 and I'll return 7-29, I know it's a short trip, but I think I need a break for a few days. I will likely not have any kind of data up there, so I can't remote the machine to build from there, so there will be NO builds until 7-29. I also probably will fall way behind on the forums as I probably can't check in on them either, so help each other out as best you can! I wanna see peace, love and CM15 when I get back!
8-11-12: General project update. Considering my A100 bricked, I get complaints constantly about slow downloads, missing days, missing features, random broken crap that I said would happen, and other general BS that I keep getting about these builds, I'm considering stopping. I did this as a favor for everyone, it's not my job, it's not required that I do this every single day, and I DON'T GET PAID FOR THIS. So either deal with the slow hosting (it's free, want faster? It costs money) and the random broken things and odd bugs, or please stop messaging me complaining about it or I just won't build these at all, and when CM10 comes up for nightlies, I won't build them either. I'll just do my own thing, build them for myself, and laugh at people with 4 month old CM10 releases (hint, I built a CM10 an hour ago, yes I can build A100 CM10s). All this complaining REALLY makes me wonder why I'm even doing this, spending my time and money on this stuff, when it doesn't seem like it really even matters. It kinda ruins the reason I started doing this and kills my drive to even do anything for android any more, let alone the a100 or the a200. /rant
8-13/14-12 : A final general project update - I'm stopping these for awhile. You may have noticed this message already below the latest download. I'm not going to name names, just know I'm tired of the complaints and demands, if you want to demand I do something, then make it worth my while, until then deal with what I can give you when I can give it. If you aren't happy with my builds, build it yourself.
Thanks for making this available!
CM9 Nightly builds for our A100, it's a beautiful thing.
PM me if the is anything I can do to help
Sent from my A100
All I ask is that if you notice any bugs to post them up so I can add them to the post, as well any anything that used to be broken but now works, hopefully the CM team can take notice and work fixes for our device branch.
Great job man. I will definitely flash this tomorrow and report back with my experience. I love that we have options now!
tested the rom!it works fine! rotation lock not working only..
labros1995 said:
tested the rom!it works fine! rotation lock not working only..
Click to expand...
Click to collapse
Nice thanks for the report I'll add it in. I think that fix is awaiting approval for merging so hopefully that will get fixed soon.
Tapatalked from my Galaxy S II.
Does this have adhoc wifi support or can it be added? I tether my tablet to my nokia phone a lot.
Sent from my A100 using xda premium
plaseo said:
Does this have adhoc wifi support or can it be added? I tether my tablet to my nokia phone a lot.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Pretty sure all AOSP roms support ad hoc wifi. Tethers to my galaxy s 2 with AOKP fine. AOSP doesn't have the same limitations as Acer roms as they share all android code with pretty much every other device in existence.
Edit: also I'm not a dev, I can't add things to these releases, I'm just syncing the code and making the rom, then putting it online for whoever wants it. That alone takes like 4 hours.
Tapatalked from my Galaxy S II.
Fantastic!! Tomorrow I'll try, anyone reports bugs?
Inviato dal mio A100 usando Tapatalk
Any reported or known bugs are listed in the second post, below the instructions for anyone to see, in case anyone missed my adding it there.
Side note, Build 2 will be available shortly. It seems to only take a couple of hours now instead of 4 like yesterday.
So we can't just upgrade whenever a newer rom is posted? We have to wipe n reflash every time, or can we just wipe dalvik n cache, then flash to update?
Sent from my A100 using Tapatalk 2
MDMonster said:
So we can't just upgrade whenever a newer rom is posted? We have to wipe n reflash every time, or can we just wipe dalvik n cache, then flash to update?
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Well you can dirty flash the same rom over each other. And yes clear cache and dalvik after flashing. The instructions are for fresh installs from another rom. Keep in mind this may prevent fixed bugs from being fixed on your install but if anything broken shows up fixed I'll post it.
Tapatalked from my Galaxy S II.
pio_masaki said:
Well you can dirty flash the same rom over each other. And yes clear cache and dalvik after flashing. The instructions are for fresh installs from another rom. Keep in mind this may prevent fixed bugs from being fixed on your install but if anything broken shows up fixed I'll post it.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
K, thx :-D
Sent from my A100 using Tapatalk 2
MDMonster said:
K, thx :-D
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'll add those to the first post with the install instructions too.
Tapatalked from my Galaxy S II.
pio_masaki said:
No problem. I'll add those to the first post with the install instructions too.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Awesome :-D . I knew about it with my captivate, but like no one ever mentions that with any Iconia ROMS, so I thought it was different with them. Thx for clearing that up for me
Sent from my A100 using Tapatalk 2
This looks awesome, will be spending some time with this tomorrow, will post whatever tweaks etc work and dare useful
Loving the latest cm9 on my touch pad to have it here too is real nice
Sent from my A100 using xda premium
Awesome! Thanks pio! Testing this now. I noticed there is no Power Control widget. Is there a way to get the AcerRing on this one?
Sent from my A100 using xda premium
[email protected] said:
Awesome! Thanks pio! Testing this now. I noticed there is no Power Control widget. Is there a way to get the AcerRing on this one?
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Not sure what you mean by power control widget, but you can add toggles to the clock pop up and scroll down. I have my wifi bt gps and brightness there.
Acer ring will only be available if one of the devs decides to port it to CM9 as there's changes to be made in the framework to get it working. Just pushing the apk won't work.
Tapatalked from my Galaxy S II.
pio_masaki said:
Not sure what you mean by power control widget, but you can add toggles to the clock pop up and scroll down. I have my wifi bt gps and brightness there.
Acer ring will only be available if one of the devs decides to port it to CM9 as there's changes to be made in the framework to get it working. Just pushing the apk won't work.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Yeah, the toggle widget but I can use Widgetsoid or the toggles in the notification pop up.
Lol that's what I did, flashed the AcerRing zip to push the apk. Of course that didn't work.
So far so good.
Sent from my A100 using xda premium
This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw
:/
ported from where? more details..
1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources
not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.
awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know
Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g
What works and what not?
jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.
Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990
-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.
Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip
----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.
Good job.
Sent from my Nexus 7 using Tapatalk 4
hello
anyone tried this out ?
feedbacks ?
thanks in advance
pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium
Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!
So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app
I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!
It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.
Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Are you going to try to make CM 10.2?
LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.
LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.