{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a team effort by all Team codefireX members listed below, as well as many other developers and users in the android community.
The codefireX team:
synergy(e) - lead dev
Mustaavalkosta - lead dev
michyprima - dev
Pnoire - bug tester and crowdin manager
Rdlgrmpf - contributor
BananaGranola - contributor
Entire crowdin translation community
PatrickC - contributor
simonsimons34 - dev
Unlike with some other JellyBean roms on this forum, I believe that all users should know exactly what is being built in/for the ROM. That is why all the repos I use and maintain are available for all to see and contribute to. The codefireX source links are above the download link. Please do not ask me to include any prebuilt or proprietary applications in this ROM; I will refuse, or ignore you entirely. Using proprietary or closed source applications/ROMs is and always will be a security concern I would rather not expose users to.
Click HERE for a full cfX settings feature flowchart by BananaGranola (thank you!)
NOT simply a re-named CM build
Based on AOSP master with regular AOSP master merges
Open Source as all AOSP ROMs deserve to be
Easily switch between a custom and "vanilla" experience in the settings app "on/off switch"
LOTS of customization options including quick settings
Built with a custom GCC 4.7.3 toolchain (opposed to stock 4.6.3), strict aliasing, -O3 completely (including thumb_cflags), and other Linaro optimizations such as OOM/LMK changes. JUST TRY TO FIND A FASTER SOURCE BUILT JELLYBEAN ROM!
Lots more but I'm boring myself already
The codefireX source
The kernel source
Official IRC Chan is #codefirex
My twitter
NIGHTLY
DarkCow aka elliot.newnham for the great OP design
IOMonster
KozmikKick
Faux123
MDeejay
ShowP1984
Cayniarb
ToastCFH
Kali-
Intervigil
eXistZ
CodeAuroraForum
Bhanvidia
BananaGranola
DeamonFish
MrSchapps
Kraizk
ALL Team Codefire members
Google
KushDeck
Aus_azn
BananaCakes
Contactwajeeh
Rafyvitto
dumpsta
cruzin_cruzin
zacgoesrawr
Zanzibar
crackajack
Zelendel
daspazz
jenkem110
Virtuous Team
Andromadus Team
CyanogenMod Team (all maintainers included)
anyone I forgot
NOT WORKING
Camera (Due to ion)
reserved for changelog
Nice, will try this tomorrow ! (technically today)
Whoops, that build is bad if you downloaded it. Ill edit this post with the all clear when the new one is up
EDIT: Build is the newest one now. Should be good for a flash. Remember to flash the kernel too everyone
its only stable and all working ^^
what kernel should I flash with this rom?
The one in the zip is the only kernel choice you have. If you use another, I can not help if you have problems
Hey, Thanks a lot this looks great, but I cant seem to run it, I flash the boot in the zip, and I flashed the zip itself, cleared everything, ad then when it boots it is stuck at a black screen.
Twner said:
Hey, Thanks a lot this looks great, but I cant seem to run it, I flash the boot in the zip, and I flashed the zip itself, cleared everything, ad then when it boots it is stuck at a black screen.
Click to expand...
Click to collapse
Same here.. Guys avoid to flash this one. Something wrong is in kernel i guess. Wait for an update from Simons.
BTW Simon thank u for supporting primou as well..
Black screen or HTC screen guys? You know I don't own the device, so please, logs.
simonsimons34 said:
Black screen or HTC screen guys? You know I don't own the device, so please, logs.
Click to expand...
Click to collapse
edit: Gets stuck at HTC white screen with provided kernel.
Be aware...
The kernel does not work...
Its gets stuck at HTC (white screen)
most importantly... the phone gets un-usually "warm"...
yes.. it get stucked at HTC welcome screen
I'll log if I get time today
Sent from my One V using xda premium
Calm down. I only need one person telling me
Sent from my Nexus 7 using Tapatalk 2
no point of doing a logcat - it doesn't reach that far. the log is empty with 'waiting for device' output. something is borked alright.
Even i tried to get Logcat but nothing was there and in shell it was saying "Waiting for device"
managed to get a logcat using maxwen's 4.2 kernel - even got past htc screen and got blank display with led going.
your full logcat can be found here: http://pastebin.com/muMxyrfF
the problem that i spotted so far seems to be the memory not loading - ion, then tries to fall to heapmem but that doesn't exist either so display fails.
Code:
E/memalloc( 1488): open_device: Failed to open ion device - No such file or directory
W/memalloc( 1488): Falling back to system heap
E/memalloc( 1488): open_device: Failed to open ion device - No such file or directory
E/gralloc ( 1488): gralloc failed err=No such file or directory
W/GraphicBufferAllocator( 1488): WOW! gralloc alloc failed, waiting for pending frees!
E/memalloc( 1488): open_device: Failed to open ion device - No such file or directory
W/memalloc( 1488): Falling back to system heap
E/memalloc( 1488): open_device: Failed to open ion device - No such file or directory
E/gralloc ( 1488): gralloc failed err=No such file or directory
W/GraphicBufferAllocator( 1488): alloc(480, 800, 2, 00000b03, ...) failed -2 (No such file or directory)
E/SurfaceFlinger( 1488): GraphicBufferAlloc::createGraphicBuffer(w=480, h=800) failed (No such file or directory), handle=0x0
E/BufferQueue( 1488): [BootAnimation] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
W/Adreno200-EGLSUB( 1642): <DequeueBuffer:420>: dequeue native buffer fail: No such file or directory
W/Adreno200-EGL( 1642): <qeglDrvAPI_eglMakeCurrent:2850>: EGL_BAD_ALLOC
E/libEGL ( 1642): eglMakeCurrent:593 error 3003 (EGL_BAD_ALLOC)
Its an ion rom. Therefor only my ion kernel will work. I'll have to look into what may be causing primou ION to not boot... I was told before that ion booted on the primou. Apparently not
Sent from my Nexus 7 using Tapatalk 2
simonsimons34 said:
Its an ion rom. Therefor only my ion kernel will work. I'll have to look into what may be causing primou ION to not boot... I was told before that ion booted on the primou. Apparently not
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
apparently your 'ion kernel' doesn't even got past htc logo. so at least be thankful that i got a logcat.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TripNDroid kernels for the HTC Endeavoru
Introduction:
The kernel released in this topic is a true 3.1.10 kernel based of the latest nVidia Tegra reference source. Please keep this in mind when using my kernel. This kernel isnt in any way related to HTC, neither to sources released on htcdev. This kernel -does- include stuff from HTC tough, for example camera, mhl and parts from the usb drivers. This was the first kernel builded from scratch and i hope you enjoy this as much as i do. A long the way more HTC stuff will be removed and my own stuff will be introduced to replace it. For the most important thing was (and is) that the "core" is completely my own work. With core i mean the power supply board file. From now on the Endeavoru will run on static regulators and not switched gpio regulators, for those who dont know much stuff about developing, this means that the power supply system is 1:1 compatible with the Linux mainline kernels. The advantage of this speaks for it self offcourse.....
Features:
- True 3.1.10 kernel
- Tegra reference pinmux support (w.i.p.)
- Linux mainline compat. power supply
- True Jelly Bean kernel
- Custom hardware drivers
- Fully unlocked speedo, sku, skuid as per Tegra ref.
- GPU OC 520mhz
- Synchronisation Framework
- Much more!
The list above will be updated along the road.
Tegra ref. pinmux
This gives us the possibillity to disable hardware pins or put them in low power mode when they are not used by the One X mainboard. As you can guess, without knowledge of hardware its extremely hard to configure them correctly. The major difference is that HTC just connects pins by let the mainboard choose where to connect them. Search for RSVD in last_kmsg from 2.6.39.4 and you know why we need the Tegra ref. method here lol.
For now the kernel will most likely only work on Jelly Bean or ICS AOSP roms. There will be support for HTC Sense based roms. It could be working allready on HTC Sense but i didnt test them so i only guarentee a working kernel on AOSP roms. If you want to try it on Sense just repack them and give it a go.
Synchronisation Framework
Android Synchronisation framework enables the framework for synchronization between multiple drivers. Sync implementations can take advantage of hardware synchronization built into devices like GPUs.
Installation:
- Download zip file and place it on youre sdcard
- Extract boot.img from the zip file
- Flash the boot.img manually via "fastboot flash boot boot.img"
- Go into recovery and flash the downloaded zip there
- Reboot
- Enjoy the TripNDroid Mobile Engineering kernel!
Downloads:
Jelly Bean AOSP:
http://tripndroid.bindroidroms.com/TripNDroid_Unleashed_3.1.10-022A.zip
http://www.tripndroid.com/downloads/kernel/3.X/Kernel-3.1.10-022A.zip
ICS AOSP:
see Jelly Bean AOSP
HTC Sense:
unavailable
Old kernel:
If you have issues you can downgrade youre kernel here:
EXP AOSP 031:
http://tripndroid.bindroidroms.com/TripNDroid-endeavoru-jb-031-exp.zip
STABLE AOSP 021:
http://tripndroid.bindroidroms.com/TripNDroid-endeavoru-jb-021.zip
Source:
https://github.com/TripNRaVeR
Credits:
Special thanks to show-p1984 for teaching git and providing information
BinDroid for providing webspace
is this the same kernel used with your jb 005 rom?
Is this one included in your ROM? And would you consider it stable?
DarkNe0441 said:
Is this one included in your ROM? And would you consider it stable?
Click to expand...
Click to collapse
Yes this version is stable, and yes this is included with my 005 release. Only this kernel will get more updates then my rom seeing i almost work daily at my kernel. My rom will contain always the latest version with each update ofc. Now you just have the option the update earlier :silly:
Thanks for your awesome work mate ...
Cool. Cool cool cool.
Is it possible to uv/uc??
Trip, I'm still having slow music playback when screen-off. Attached last kmsg.
http://db.tt/K0uRd3Ah
I also tried cranking the minimum clock to 340 but problem still there.
EDIT:Scratch that, seems better now after setting the 340 minimum.
Tapatalked from my HOX
Another awesome development by a great developer. Will definitely keep a watchful eye on this one. Using your rom, and it will be nice to have a complete package with your kernel as well.
Now that you are working on a standalone kernel. Will you be able to uncap the gpu like faux and kohlk did? Just very curious.
Code:
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiStateMachine( 419): Failed to setup control channel, restart supplicant
D/CommandListener( 184): Setting iface cfg
D/CommandListener( 184): Trying to bring down wlan0
E/wpa_supplicant( 4773): Could not set interface wlan0 flags: Invalid argument
E/wpa_supplicant( 4773): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 4773): wlan0: Failed to initialize driver interface
D/Beautiful Widgets(4110100)( 1635): WidgetRefreshService
D/dalvikvm( 1635): GC_CONCURRENT freed 1543K, 73% free 3407K/12288K, paused 11ms+1ms, total 29ms
D/dalvikvm( 1635): WAIT_FOR_CONCURRENT_GC blocked 4ms
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiHW ( 419): Supplicant not running, cannot connect
i can't activate my wifi, i'm on the cm10 preview 8 rom from tbalden, and wanted to try your kernel, i flashed the boot.img, erased cache and flasched the modules!
What do you think, can I build/compile the kernel anytime form source (i.e. when I see a fix/commit that I must have asap ^^), or is that too risky and should I wait for your "official" kernel built?
And to make it easier to coordinate that "build-it-yourself", could you mention the last included commit (hash) in the changelog of your provided built? Thanks
Rycon33 said:
Trip, I'm still having slow music playback when screen-off. Attached last kmsg.
http://db.tt/K0uRd3Ah
I also tried cranking the minimum clock to 340 but problem still there.
EDIT:Scratch that, seems better now after setting the 340 minimum.
Tapatalked from my HOX
Click to expand...
Click to collapse
I also having this issue....but I manage to solve it by re-install the rom.... :victory:
forgot to mention that I'm using poweramp for my music.
Just tried this kernel, no luck. Wi-Fi is very slow. I tried with Trip's 005
Trip
phone doesn't seem to charge using the 002 kernel using with 005 ROM.
vickysud said:
Trip
phone doesn't seem to charge using the 002 kernel using with 005 ROM.
Click to expand...
Click to collapse
Guess why he posted to use the new boot.img 005 ?? Flash 005 and you are good to go
n3ocort3x said:
Guess why he posted to use the new boot.img 005 ?? Flash 005 and you are good to go
Click to expand...
Click to collapse
check this out
Trip himself suggested to use updated kernel sadly this kernel has battery charge problems where as kernel with 005 ROM doesn't
http://forum.xda-developers.com/showpost.php?p=29435454&postcount=1121
Using kernel 002 phone is charging for me, although it's getting warmer than usual while being charged.
For me no charging issues either, will give the charger port max power in next release
TripNRaVeR said:
For me no charging issues either, will give the charger port max power in next release
Click to expand...
Click to collapse
Lol at max power. Just hope it doesn't explode.
Sent from my HTC One X using xda premium
Trip
Phone is charging but very slowly takes almost 20min or more to increase a %.
Do not flash to the Galaxy W, the kernel is incompatible, along with other smaller things
After about 6 month of waiting, most of which was fighting my computer, AOKP pure is finally here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Major update:
I've switched over to the 3.4 kernel . I will be testing the wifi tonight to make sure it works fully. This is easily the snappiest I have ever seen this device
Built on AOKP 4.1.2 code, this is slightly out of date, but stable. What I've found so far that is broken is as follows:
- Camera is still broken (kernel limitation, for the moment)
- WiFi tethering (broken by kernel)
- USB Tethering
Thankfully, it's a short list. Here's what is working:
- WiFi
- Cell data
- 2G mode (seems spotty though)
- vsync (project butter)
- Bluetooth
- USB mass storage
- volume scrolling shortcut
- color choosers (a little finicky sometimes)
- GPS
- MMS
UPDATE: 5/13/13
- Airplane mode also works
- Data monitor (after correcting the kernel)
UPDATE: 7/18/13
- Orientation works!
Thanks to the following people:
KemoNine96: For providing a base for the device and vendor files
arco68: For providing the kernel source, bringing the Rugby Smart to the 3.4 kernel
Team Kang: For the ROM source
Team codefire for the build box access
Sources
Team Rugby (will be pushing my frameworks/base up later): https://github.com/TeamRugby
AOKP: https://github.com/AOKP
To Install, you must meet these criteria:
- Have a Samsung Rugby Smart
- Be using KemoNine96's 6.0.1.1 or newer CWM recovery or my TWRP builds
- Have GAPPS 4.1.2 in a flashable zip
- MOST IMPORTANTLY, accept the fact that I, as a developer, take no responsibility for damage to your device. Consider yourself warned.
Current Builds
Beta 2
- Fresh sync with upstream
- Orientation now functions
Older Builds
Beta 1
Alpha 2
AOKP Apache Alpha 1
AOKP Apache Initial
See OP
Gapps information
For those that don't know about GAPPS
Installation is as easy as:
1. Download the zips, and transfer it to your device
2. Boot into recovery mode and select "install zip from sdcard"
3. Select "Choose zip from sdcard", find the ROM zip, then confirm the installation
4. Follow the same procedure for GAPPS
5.Enjoy the new ROM!
1st Thanks
keep forward man
Slow down a minute, the link's not even up yet
our brother got a newly created AOKP
i'm thinking that ancora family started to develop faster B)
hadidjapri said:
our brother got a newly created AOKP
i'm thinking that ancora family started to develop faster B)
Click to expand...
Click to collapse
nah loh keduluan...
---------- Post added at 12:38 AM ---------- Previous post was at 12:38 AM ----------
Motorhead1991 said:
Slow down a minute, the link's not even up yet
Click to expand...
Click to collapse
good job bro :good:
Good Job It's possible to convert it into Galaxy W?
It's alot like Remics, so there's not a bunch of difference. it also has the "same" kernel in the sense that it is built on arco68's 3.0 sources.
Motorhead1991 said:
It's alot like Remics, so there's not a bunch of difference. it also has the "same" kernel in the sense that it is built on arco68's 3.0 sources.
Click to expand...
Click to collapse
i wonder how similar our phone is. is it just like sgw,sgs+, and exhibit?
Sent from my GT-I8150
From what Kemonine and I have gathered, it shares the board architecture with the W, with the Galaxy S display and a similar touchscreen to the S. It has hardkeys like the W, but has 4 instead of 3.
Motorhead1991 said:
From what Kemonine and I have gathered, it shares the board architecture with the W, with the Galaxy S display and a similar touchscreen to the S. It has hardkeys like the W, but has 4 instead of 3.
Click to expand...
Click to collapse
The big differences I've found:
kernel differs in sound area
different lcd panel
sensors libs differ greatly (not @ all compatible)
wifi config file is us, not eu based
different battery capacity
misc other bits and pieces scattered throughout
the original apache sources do have "ancora" and "GT-I8150" strings, looks like samsung started with the ancora sources and moved things over
Thanks for the clarification KemoNine. .
Hi, is it possible to make this rom compatible with our SGH-i847? http://forum.xda-developers.com/showthread.php?t=1753233
It would be great to have Rugby which looks like GT-i9300. Thanks.
Wysyłane z mojego SAMSUNG-SGH-I847 za pomocą Tapatalk 2
That just looks like a reskinned CM9. If you can find Remics' sources, I can build it properly.
Where should I find them?
I haven't found them yet.. I would like to though.
Aplha 1 will be up shortly .
EDIT:
Alpha 1 is up, with a changelog added.
I apologize for not posting any updates in a while, I haven't made any changes that warrant an update. I have started playing around with the kernel again, so maybe I can bring the battery life up a bit.
Here's a much needed update...
GUMMY
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gummy ROM is made for speed, stability and to stay as closely in line with AOSP as possible while still supporting a large amount of devices and giving you all of the features you love. It isn’t slowed down by features you’ll never use nor is it so slim as to be just another AOSP build.*
Features:
* New base built from AOSP
* Status Bar Mods
* Hardware Key Mod
* Many Wallpapers
* Performance Control
* Application Permission Controls
* Carrier Label Options
* Lock clock widget
* QuickSettings
* Theme Manager
Device Specific:
Whats not working...
* In-Call mute
* HDR camera
* misc QuickSettings buttons may still have issues (let us know what you find)
* what else (you tell us)
ChangLOG:
Please review out Gerrit instance to keep up with changes daily...
Instructions for installations:
1. Download ROM
2. Download Gapps
3. Push to sdcard
4. Reboot Recovery
5. Wipe Data and Cache
6. Install ROM
7. Install Gapps
8. Reboot System
Contributions:
- Thank you to Cyanogenmod for device and hardware repositories. Without this, porting * * Gummy to QCOM devices would have been nearly impossible.
- Thank you to Google for the best source code.
- Androidfilehost.com for hosting our file servers!
Team Members: In alphabetical order
Primary Developers:
Cphelps76, Kejar31
Developers and Device Maintainers:
Bkjolly, BytecodeMe, DHacker29, Hashcode, NoCoast, Papi92, TDM, Xoomdev
Artwork direction and development
ChadFrankos, Cphelps76, Kejar31
Github- https://github.com/TEAM-Gummy
Gerrit- http://review.gummyrom.com/#/q/statuspen,n,z
Twitter- @gummyRom
GAPPS - we now recommend PA-Gapps
ROM
First of all thank you, will going to test it
One question , when open the downloadlink 9505 - http://old.androidfi...xx/KitKat-Beta/ it shows jfltevzw links. Is this i typo ? Are the Builds correct ?
Best Regards
Tylog said:
First of all thank you, will going to test it
One question , when open the downloadlink 9505 - http://old.androidfi...xx/KitKat-Beta/ it shows jfltevzw links. Is this i typo ? Are the Builds correct ?
Best Regards
Click to expand...
Click to collapse
Oh crap lol.. fixed.. try again!!
kejar31 said:
Oh crap lol.. fixed.. try again!!
Click to expand...
Click to collapse
now its fine, download now
OK it's time for something new
let's try this one !
Thanks! Trying now
Me Gusta!
Will test now thanks
File says unofficial while thread title says official? Downloading anyway as the date is the same
Me Gusta!
Me Gusta said:
File says unofficial while thread title says official? Downloading anyway as the date is the same
Me Gusta!
Click to expand...
Click to collapse
yeah yeah ignore that lol.. the it says official in the thread to let you know this is the official Gummy team.. official in the rom just indicates that we are still on an early released and it has yet to go full blown 2.0 release.
kejar31 said:
yeah yeah ignore that lol.. the it says official in the thread to let you know this is the official Gummy team.. official in the rom just indicates that we are still on an early released and it has yet to go full blown 2.0 release.
Click to expand...
Click to collapse
Okay! And do I maybe know this rom from my Nexus S?
Me Gusta!
Me Gusta said:
Okay! And do I maybe know this rom from my Nexus S?
Me Gusta!
Click to expand...
Click to collapse
Well the primary devs both have the S4.. this is why we got this S4 builds out and tested first. We will be adding new devices as time and testing permits
Does HDMI out work???
Sent from my GT-I9505 using Tapatalk
WOW, Team Gummy here...THX
kejar31 said:
Well the primary devs both have the S4.. this is why we got this S4 builds out and tested first. We will be adding new devices as time and testing permits
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1486264 was talking about this, but never mind let's get back on topic! Flashing this as we speak
Me Gusta!
Bug? Thank you for all your work
My bugs:
Camera HDR not work
Front camera green lines
Sharpen effects from gallery fc
No posible install from ex SD card....must be moved app to phone( internal)....
Sorry for question but im on official 4.3.... How can i install this rom or at first install a recovery on my device ?*shame*
downloaded twice and keep getting error code 7 install aborted
JohnnyBlack10 said:
My bugs:
Camera HDR not work
Front camera green lines
Sharpen effects from gallery fc
No pisibke install from ex SD card....must be moved app to phone( internal)....
Click to expand...
Click to collapse
Thanks for the heads up.. just found out today about the HDR issues... now I see the ffc green line issue as well. Just got the sharpen issue as well lol how the hell did you find that
not sure what you mean by the last one though but I will look into the rest.
DuTY09 said:
downloaded twice and keep getting error code 7 install aborted
Click to expand...
Click to collapse
@kejar31 seems like you did something wrong with the updated script. TWRP says that this file is for jftle devices, and it recognises our devices as a jftlexx device, so installation keeps aborting.. Not such a big problem but it needs to be fixed.
Me Gusta!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Important Notes:
Fully compiled from AOSP source ( source.android.com) with our mods.
Read the changelog and installation instructions on the website here carefully.
Feature requests will be ignored in general but will review ( if a relevant commit is provided) and decide
No ports based on our ROM zip (official or unofficial build) file, manifest.xml will be updated regularly and feel free to compile from source
Changelog
To find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers at #freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Instructions
For installation instructions please check here
Please keep in mind if a special instruction is needed it will be noted in Changelog
Downloads
Before you download i want to let everybody know that this release is untested as i dont have the phone myself
Betav1.9 http://goo.im/devs/demetris/Nozomi/Slimkat//Slim-nozomi-4.4.2.beta.1.9-UNOFFICIAL-20131224-0035.zip
Betav2 http://goo.im/devs/demetris/Nozomi/Slimkat//Slim-nozomi-4.4.2.beta.2-UNOFFICIAL-20131231-0735.zip
Betav2.1 http://goo.im/devs/demetris/Nozomi/Slimkat//Slim-nozomi-4.4.2.beta.2.1-UNOFFICIAL-20140110-2349.zip
V2.6RC2 http://goo.im/devs/demetris/Nozomi/....2.build.2.6.RC2-UNOFFICIAL-20140205-0142.zip
SlimGapps and other addons for 4.4.x SlimKat here.
FAQ[/SIZE][/B]
Check out our FAQ before posting! Keeps more common questions answered in one place!
Bug list
For a list of confirmed bugs look here
Xperia S specific bugs:
Whatever bugs CM-11.0 | OpenSEMC has to offer
Thanks!
You can find the full list of credits here
Source
Please visit here for the source code.
CREDITS:
FXP for the CM10 initial sources!
Slim Developers for their sources!
CyanogenMod for CyanogenMod!
RaymanFX : as this build is based on his sources
U doing an awesome work man keep it up!
Click to expand...
Click to collapse
And again if you find my work useful there is a thank you button, use it! :highfive:
As usual this is mine too
Nice *-*
Cool
Will try this for sure
sent from my lt26i running android 4.4 by RaymanFX
its great to see new roms,thanks to you and all developers :good:
Yay! A new ROM! But what's the difference with RaymanFX alpha? Is this updated frequently when Rayman update his rom? Thanks.
Hey feel free to build this for hikari i keep the sources upto date in the opensemc github so if you use that as the base and change what you did to the vendor files and whatnot you should have no trouble building it with hikari as well. Im sure the people in the Acro S forum would appreciate a ROM other then mine.
No problem from my side but lets see 1st if this boy boots
Demetris said:
No problem from my side but lets see 1st if this boy boots
Click to expand...
Click to collapse
ai, too bad :crying:
installed rom + Slim_minimal_gapps.4.4.1.beta.1.5
boot logo takes a long long time (but no problem), a nice new boot animation and...
multiple fc's, where "unfortunately, the process com.android.phone has stopped" is on top (but i saw several fc's before that).
dreezz said:
ai, too bad :crying:
installed rom + Slim_minimal_gapps.4.4.1.beta.1.5
boot logo takes a long long time (but no problem), a nice new boot animation and...
multiple fc's, where "unfortunately, the process com.android.phone has stopped" is on top (but i saw several fc's before that).
Click to expand...
Click to collapse
Usually means that you used the wrong "frameworks/opt/telephony" you cant use the opensemc one you have to use the slimroms one.
Nope
SlimKat/frameworks/opt/telephony$ git log
commit 9531340ea8e59f0cca5843c0b7e156ece1f5fdb7
Merge: 2353ac1 567ea11
Author: Lars Greiss <[email protected]>
Date: Wed Dec 11 21:37:30 2013 +0100
Merge tag 'android-4.4.2_r1' into HEAD
Android 4.4.2 Release 1
commit 2353ac19d5d3c13e47ab92eca1e067e176975767
Merge: 22ae3a8 449cbf8
Author: Lars Greiss <[email protected]>
Date: Fri Dec 6 03:41:50 2013 +0100
Merge remote-tracking branch 'aosp/kitkat-mr1-release' into HEAD
Conflicts:
src/java/com/android/internal/telephony/RIL.java
Change-Id: Icd0b4b12c7efa5906fb62107e3a9249428954dad
Screenshot pls
Xperia S1
Demetris said:
Nope
SlimKat/frameworks/opt/telephony$ git log
commit 9531340ea8e59f0cca5843c0b7e156ece1f5fdb7
Merge: 2353ac1 567ea11
Author: Lars Greiss <[email protected]>
Date: Wed Dec 11 21:37:30 2013 +0100
Merge tag 'android-4.4.2_r1' into HEAD
Android 4.4.2 Release 1
commit 2353ac19d5d3c13e47ab92eca1e067e176975767
Merge: 22ae3a8 449cbf8
Author: Lars Greiss <[email protected]>
Date: Fri Dec 6 03:41:50 2013 +0100
Merge remote-tracking branch 'aosp/kitkat-mr1-release' into HEAD
Conflicts:
src/java/com/android/internal/telephony/RIL.java
Change-Id: Icd0b4b12c7efa5906fb62107e3a9249428954dad
Click to expand...
Click to collapse
Don't do any merges in the Fuji common folder there is the file needed already it will add it to your telephony folder on build
Demetris,
nice to see a modern SlimRom. but why it is based on bugy opensemc? If you use Letama 4.3 as base, you will become a bugfree SlimRom.
You realize this will be more and more perfected as time passes, right?
more and more perfected?
I think not. but opensemc had charge/video/camera/ram bugs since CM10.
Geia sou re Mitso tsiakko, kalosorises sto pio prixto forum tou planiti!
Going to give this baby a spin tomorrow and see how it goes
Ευχαριστούμε Μητσάρα
sent from my lovely white ***** XS using my nipples
Nice too see SlimRom again for our beloved Xperia S :good:
heross said:
Demetris,
nice to see a modern SlimRom. but why it is based on bugy opensemc? If you use Letama 4.3 as base, you will become a bugfree SlimRom.
Click to expand...
Click to collapse
why don't you contributing or create something instead complaining of something is buggy?
No, letama has stop the development of our phone while opensemc will definitely gets better over time.
Xperia ZL/ODIN/C6503 CYANOGENMOD 11 LINARO/SABERMOD WEEKLY BUILDS
Weekly Build 20140422 is ONLINE
Build/Sync Date: April 22 0xh:xx GMT+1 Lisbon
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.10.0 201404 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.3 201404 toolchain
FEATURES
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
sqlite fsync hack by dorimanx
white kk UI
CHANGELOGS
(check build/sync date and compare)
http://www.cmxlog.com/11/odin/
http://changelog.bbqdroid.org/#/odin/next
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 16 "Petra" x64 3.11.10)
HOMEPAGE
http://infectedbuilds.net
DONATIONS NEEDED
if you can, please make a small donation... not for my work, 'cause this is a hobby for me, but to keep website and dedicated server up and running, so i can deliver fast and unlimited downloads, and host the builds.
thank you all,
regards.
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
latest linaro arm-eabi-4.10.0 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.3 toolchains to compile ROM code
Special Thanks
CyanogenMod Rom Dev Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 11 for the Xperia ZL/odin.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.8.3 14.03 (kernel code) & boosted-tc arm-linux-androideabi 4.8.3 14.03 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
Looks good, I'll try it out later and report findings.
Will try exactly after two weeks.
Sent from my C6502 using xda app-developers app
Using this ROM now. however i am facing a problem. where touch response stops. Only reboot using key helps to make it work again
coolrevi said:
Using this ROM now. however i am facing a problem. where touch response stops. Only reboot using key helps to make it work again
Click to expand...
Click to collapse
i also faced this but only on lockscreen
quick inquire:
how many users of the samsung i9505/jflte are in this thread?!
just press thanks.
Been using this for about a week or so, pretty good so far.
Testing !!!
When installing the (any)CM11 based rom, I did have a LTE connection, could send/receive SMS but no internet on LTE Mobistar (Belgium).
After some googling, I found apns-conf.xml in the /system/etc/ folder. I checked the values for internet and MMS.
These are the correct values for the /system/etc/apns-conf.xml.
There is no username or password and for internet there is no proxy or port. And there is a PAP authenticationtype.
<apn carrier="Mobistar MMS" mcc="206" mnc="10" apn="mms.be" mmsc="http://mmsc.mobistar.be" mmsproxy="212.65.63.143" mmsport="8080" authenticationtype="PAP" type="mms"/>
<apn carrier="Mobistar Internet" mcc="206" mnc="10" apn="mworld.be" authenticationtype="PAP" type="default,supl"/>
Please adapt it in your builds, so that I don't have every-time when installing the nightly builds, I have to fix it manually
Where is recovery?
suleymanovemil8 said:
Where is recovery?
Click to expand...
Click to collapse
sources issues.. try official. happens the same thing.
regards.
infected_ said:
sources issues.. try official. happens the same thing.
regards.
Click to expand...
Click to collapse
Same on official
Hi boss is app2sd working on this rom?
Sent from my Xperia ZL using Tapatalk
imkentoy said:
Hi boss is app2sd working on this rom?
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
never tried it. you have to find out by yourself ..
infected_ said:
sources issues.. try official. happens the same thing.
regards.
Click to expand...
Click to collapse
Hey,
is your CWM recovery gone, too? Any idea in how to get it back?
lordsony said:
Hey,
is your CWM recovery gone, too? Any idea in how to get it back?
Click to expand...
Click to collapse
flash a boot.img from a build before 20140508 ..
infected_ said:
flash a boot.img from a build before 20140508 ..
Click to expand...
Click to collapse
cool, thank you! I suppose I should flash it via fastboot?
infected_ said:
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
why i can't write in fastboot mode? is there important if in settings was checked the debugging mode? my ZL is soft brick, I can flash just with flashtool, but after each flashing i have no erros but still remain the first version of ftf before bricked. do you know why it cannot replace it? pc companion do the same, no errors but still not fix my phone.