I do not own the i9300 anymore, older builds are still available but I won't be able to publish any new one
THIS IS STILL AT AN EXPERIMENTAL STAGE
Hey guys, I started porting Ubuntu Touch to the international S3 (i9300).
This is just a first build, so there are quite a few bugs (listed below).
Code:
DISCLAIMER: Flash this at your own risk.
I won't be held responsible for any damage done to anything whatsoever, you guys should know the drill by now
Source-Code
You can find the GPL-compliant code on my github for both the device-tree and the kernel :
i9300 Device-Tree: https://github.com/Androguide/android_device_samsung_i9300
Exynos4412 Kernel: https://github.com/Androguide/android_kernel_samsung_smdk4412
Exynos4412 Common device-tree: https://github.com/Androguide/android_device_samsung_smdk4412-common
Proprietary blobs: https://github.com/Androguide/android_vendor_samsung
CM common vendor blobs: https://github.com/Androguide/android_vendor_cm
local_manifest & modified CM manifest: https://github.com/Androguide/Ubuntu-Touch_manifests
Platform source code: http://phablet.ubuntu.com/gitweb
Build instructions
Build instructions, components licensing, and more in-depth infos on this port in the official wiki page for i9300: https://wiki.ubuntu.com/Touch/Devices/i9300
Known Issues
Fonts are messed-up - Fixed
No Wifi - Fixed
No GSM/Phone calls
Everything else seems to be working just fine (both cameras, brightness etc...) but please report if you find anything other than what is mentioned in the "State of Things on Official Builds" section of this post
Instructions
In recovery, wipe data, dalvik, cache (and optionally system, just to be sure)
Flash saucy-preinstalled-armel+i9300.zip first
Then flash saucy-preinstalled-phablet-armhf.zip
Reboot
Downloads
Build n°4: http://goo.im/devs/Androguide/Ubuntu-Touch/i9300/saucy-preinstalled-armel-i9300.zip OR http://d-h.st/IaD (md5: 7fed714149d95445869aef0ebc7a1fad)
Preinstalled ubuntu image (updated daily): http://cdimage.ubuntu.com/ubuntu-to.../current/saucy-preinstalled-phablet-armhf.zip
(md5: http://cdimage.ubuntu.com/ubuntu-to...t/saucy-preinstalled-phablet-armhf.zip.md5sum)
Changelogs
Build n°4:
Updated to Ubuntu 13.10 Saucy Salamander
Auto Rotation on supported apps
System settings
All installed apps show-up in the launcher
More
Build n°3:
Fixed Wi-Fi (commit)
Removed all useless dependencies & overlays (commit1 / commit2 / commit3)
Added cool Ubuntu ASCII art as the first logcat message on boot (replaces CM's one) (commit)
Removed some useless build.prop flags related to dalvik (commit)
Build n°2:
Fixed fonts by downgrading mali drivers to r3p0 (commit)
Downgraded ump drivers to r3p0 (commit)
Removed some unused packages & dependencies (commit1 + commit2 )
Documented changes on github (commit)
Build n°1:
Initial build
State of Things on Official builds
This table shows the current state of working/partly-working/non-working features on official builds for Nexus devices.
Ultimately, the goal for the S3 is to have the same set of working features as on Galaxy Nexus (maguro) :
{
"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"
}
Reviews
Article & installation guide by @adityalahiri13 : http://www.techgeekal.com/2013/06/10/ubuntu-touch-for-the-samsung-galaxy-s3/
Credits
Canonical for Ubuntu & Ubuntu Touch
CyanogenMod for the base tree & kernel sources
Linaro for their 4.7.2 gcc toolchain, used to compile those builds
Screenshots
good news , thank you
AWESOME! will take a nandroid and try asap!
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
maybe @temasek can help with wifi?
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
i have pmed the guy that fixed fonts in galaxy 1 and 2 for font fix for us
naathaanb96 said:
AWESOME! will take a nandroid and try asap!
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
maybe @temasek can help with wifi?
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
i have pmed the guy that fixed fonts in galaxy 1 and 2 for font fix for us
Click to expand...
Click to collapse
Ok, my bad, wifi might actually be working. From the Ubuntu Touch wiki it says that it currently only supports open networks (no wep or wpa keys) through the GUI, but you can import wifi settings from your Ubuntu desktop, which will cause it to install some packages including the Wireless Interface (iw), so it might be why I can't see the open networks neither as there is no wireless interface installed.
I'll import my desktop wifi settings and report back.
About the fonts, I think I know where the problem is, might be a dependency file I had to remove from the makefiles to fix a build error.
I'll probably do another build later today to try and work-around this, it's pretty fast to compile as it's only C/C++ and the output is like 40mb.
NETWORKING
The simplest solution given that you have a UI available is to use the networking indicator on the device. The network indicator currently supports basic Wi-Fi connections only ( eg. No security, WEP, WPA Personal ).
An alternate means of configuring networking is via the phablet-network-setup tool which is part of the phablet-tools package. This script can be used to copy an active Network Manager system settings file from an Ubuntu Desktop ( >= 12.04 LTS ) to the device. It also has some extra options which cause the tool to install network-related packages such as iw and openssh-server.
Click to expand...
Click to collapse
Other than that, brightness control and auto-brightness are working properly, and the fonts in the apps seem to be ok, looks like the fonts are messed-up only in the core UI/Launcher, appart from a few glitches here and there in some other apps.
The Dialer's call button doesn't seem to be responding, although I'm not sure if the dialer is functionnal already in the nexus builds.
I had a quick play around and it looks very promising. I couldn't get a call to make though and I couldn't find settings
Sent from my GT-I9300 using Tapatalk 4 Beta
naathaanb96 said:
I had a quick play around and it looks very promising. I couldn't get a call to make though and I couldn't find settings
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, it looks like the only settings are those you get in the statusbar, you can move left & right while swiping it down, and it gives you the settings for sound, screen, wifi, etc...
Thank you for this. I will test it when i get home from work. Can't wait. Rep+1 for you
Sent from my GT-I9300 using xda premium
---------- Post added at 04:10 PM ---------- Previous post was at 04:01 PM ----------
Btw can i make a call?
Sent from my GT-I9300 using xda premium
zulmajdi said:
Thank you for this. I will test it when i get home from work. Can't wait. Rep+1 for you
Sent from my GT-I9300 using xda premium
---------- Post added at 04:10 PM ---------- Previous post was at 04:01 PM ----------
Btw can i make a call?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nope, doesn't seem to initiate the dialing, but I don't really know if it's a bug or if that feature is still missing from the mainstream builds.
Working on the new build and trying to fix fonts as we speak.
Androguide.fr said:
Nope, doesn't seem to initiate the dialing, but I don't really know if it's a bug or if that feature is still missing from the mainstream builds.
Working on the new build and trying to fix fonts as we speak.
Click to expand...
Click to collapse
So all that related to sim won't work? Damn but still gonna test your build. Never had any chance to test the ubuntu touch. Thanks again
Sent from my GT-I9300 using xda premium
zulmajdi said:
So all that related to sim won't work? Damn but still gonna test your build. Never had any chance to test the ubuntu touch. Thanks again
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yeah, either way Ubuntu Touch is still a developer preview for the moment, many things are still not working/not ready, although the first public launch on a widely distributed device is expected by the end of the year.
I actually build this because I want to start writing apps for Ubuntu Touch and needed a device to test on.
The team of engineers behind Ubuntu Touch is publicly answering questions on xda if you want to know more about the OS and its current state : http://www.xda-developers.com/android/ubuntu-engineers-to-answer-your-questions-about-ubuntu-touch/
Androguide.fr said:
Yeah, either way Ubuntu Touch is still a developer preview for the moment, many things are still not working/not ready, although the first public launch on a widely distributed device is expected by the end of the year.
I actually build this because I want to start writing apps for Ubuntu Touch and needed a device to test on.
The team of engineers behind Ubuntu Touch is publicly answering questions on xda if you want to know more about the OS and its current state : http://www.xda-developers.com/android/ubuntu-engineers-to-answer-your-questions-about-ubuntu-touch/
Click to expand...
Click to collapse
Thank you for the information. Im home. Downloading now
Sent from my GT-I9300 using xda premium
Are you kidding me!!! This is very awesome, going to subscribe to this thread and wait for the wifi to work so i can switch over ;D
posted by the Q Master, woepidooo
Androguide.fr said:
...
Hey guys, I started porting Ubuntu Touch to the international S3 (i9300).
This is just a first build, so there are quite a few bugs (listed below).
...
Click to expand...
Click to collapse
Very nice - just a quick question that could become very relevant - can the Ubuntu system/ROM itself be made to boot with another kernel? Since if it could boot with one of the dual-boot kernel that will suddenly open some huge opportunities!
If that is not the case (since let's say Ubuntu needs some extra stuff in the kernel) - then here is the obvious question - can the Ubuntu special kernel be "mixed" with the dual-boot feature from Siyah / Googy-Max?
xclub_101 said:
Very nice - just a quick question that could become very relevant - can the Ubuntu system/ROM itself be made to boot with another kernel? Since if it could boot with one of the dual-boot kernel that will suddenly open some huge opportunities!
If that is not the case (since let's say Ubuntu needs some extra stuff in the kernel) - then here is the obvious question - can the Ubuntu special kernel be "mixed" with the dual-boot feature from Siyah / Googy-Max?
Click to expand...
Click to collapse
Yeah, it should dual boot with Siyah kernel or some other kernel that supports dual-boot for cm10.1
Don't quote me on that though, the fact that there is no Dalvik vm on Ubuntu Touch might be a problem, but the base is cm10.1 and the base kernel is from cm too. Plus the modifications required for Touch to run on the cm kernel are trivial, so I guess it should be easily doable on Siyah too.
I'll test this asap and report back. If it works I'll fork the Siyah kernel and make it the default kernel I guess.
I rememeber the older preview had the same problems and fixed them maybe you can contact those developers
You can fix Font corruption by reverting to r3p0 mali drivers.
Sent from my GT-I9300 using xda premium
Thealshear said:
I rememeber the older preview had the same problems and fixed them maybe you can contact those developers
Click to expand...
Click to collapse
It's all good I got the solutions for both font & wifi issues
The fonts require an older version of the mali drivers, and the wifi needs /system/etc/wifi/bcmdhd_sta.bin instead of bcmdhd_apsta.bin
It should be fixed in the next build, most likely tomorrow.
Nice, very nice pal! I was waiting for this for a long time, i'm subscribed now and if i can help i will, as tester
That would be great!
Androguide.fr said:
Yeah, it should dual boot with Siyah kernel or some other kernel that supports dual-boot for cm10.1
Don't quote me on that though, the fact that there is no Dalvik vm on Ubuntu Touch might be a problem, but the base is cm10.1 and the base kernel is from cm too. Plus the modifications required for Touch to run on the cm kernel are trivial, so I guess it should be easily doable on Siyah too.
I'll test this asap and report back. If it works I'll fork the Siyah kernel and make it the default kernel I guess.
Click to expand...
Click to collapse
That would be great - also take a look at Googy-Max (a fork of Siyah where some extra work was done to add some extra goodies like configurable zram, abb and touch2wake).
Also both Siyah and Googy-Max have two versions of Mali drivers inside, so that could also fix the problem above with the font.
Once a dual kernel is supported I would certainly try ubuntu in first-ROM partitions - I have my daily 4.1.2 ROM as 2nd but I would really like to see how native (as opposed to dalvik) code runs on i9300!
Nice downloading ... will give feedback asap
Sent from my GT-I9300 using xda app-developers app
Related
Hi to all
I'm here to present to you my new rom:
the Clean Blank ROM
This is a SIMPLE rom...
{
"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 NOT MEANT FOR ORD USERS xD
ORD
This is meant to be a STABLE rom, to flash and then forgot about it just like a REAL Stock rom!!!
Updates will be present only in case of versions bump and bugfixig
Don't expect nor nightly nor a weekly release, cause ITs NOT MEANT TO BE LIKE THIS!
LOL xD
Lets quickly start with the goal of the rom:
Having a REAL nexus user experience, on the Galaxy S2
This is not simply going to give you an Aosp rom, but a real OEM-Like Package, turning your SII into a brand new GNex just like it is when booted for the first time
So here is what the rom offers:
Update to android 4.1.2 (read changelog http://www.funkyandroid.com/aosp-JRO03R-JZO54K.html )
New 4.1.2 gApps + 4.2 gapps
OEM-like Nexus system Specifically built around Gs2, includes specific
OEM-like rom signaturing (encaching security)
Open source audio
System optimizations
Optipng
Zipaligned
Deodexed
Rooted
Added OTA updates
init.d support
Cm10 camera
full gapps (Gnow working)
USB OTG Mouse and Keyboard support
Encached Media Quality (MP4 -STEREO- video recording (working 1080p))
Fixed Holo background banding
Dock settings (now USB Audio with official base works)
Optimized scrolling
Optimized launcher memory usage
Optimized memory/graphic/speed
HSPAP:15 support (H+)
FM-Radio support (install it from the OTA App)
Resolved RILJ Wakelock
Optimized MediaScanner
Thats straight and simple
KNOWN BUGS (and relative workarounds!)
- TV Out Mirroring: not working (and will probably never work) -> You can still see videos from players/youtube/browser, just normal mirroring will not work
- No ProjectButter
REMEMBER:
THIS ROM IS OPENSOURCE!
www.github.com/89luca89
If YOU Want to compile your own nightly go to post 3!
Now I just want to explain to you WHY of some choices:
WHAT TO EXPECT:
Lghtweight, Fast, Smooth as silk rom BUT Still with a complete set of GApps (including FaceUnlock)
This is meant for REALLY PURE GE Experience, so NO TOGGLES, NO MODS, NO THEMES (from me, users are free to theme the rom for me ), but with the Suggestion I'll give you, you'll not Miss them...
If really then you want meteo in status, 213123 toggles, central clock and all that things go for CM9/10 and AOKP And simply leave this rom, its NOT meant to be This way xD
ADD-ON AND SUGGESTIONS:
Notification Toggles:
On Market, search for WIDGETSOID:
https://play.google.com/store/apps/details?id=com.jim2&hl=it
After a simple setup you'll have this
OR
you can use NOTIFICATION TOGGLES:
https://play.google.com/store/apps/...EsImRlLmo0dmVsaW4ubm90aWZpY2F0aW9uVG9nZ2xlIl0.
droidphile said:
Couple of tips for users:
1) For notification and battery percentage, use notification toggle from playstore. Download cyanogenmod icons/original ics icons from within app (stock toggles in the app are big and ugly) and after 5 minutes of configuration you will get this:
2) For bln there's no notification service that runs in background polling for missed calls and msgses by default - unlike CM9. Using BLN control app you can get the service running and hence bln. If you're using a kernel with built in bln support and misc files (like Siyah) do the following to get bln working for missed calls and stock sms.
Download missed call reminder. Check missed calls and unread sms in the app. Under cal reminder settings set LED color to white. Uncheck screen On. Do the same thing for sms reminder settings. Now activate bln through script or extweaks.
If you're using gosms, uncheck "unread sms" in the app and check "Blink LED" in gosms notification settings.
3) Press and hold volume down and power key simultaneously for a screenshot.
Click to expand...
Click to collapse
OR
you can use BATTERY WIDGET REBORN:
LINK MARKET
FM RADIO
To use it, install SpiritFM, check it on OTA APP or here:
http://forum.xda-developers.com/showthread.php?t=1059296
ALL CREDITS GOES TO mikereidis, HE IS THE WIZARD THAT MAKE IT TO WORK
Please consider donating or purchasing the paid apps to support the developer, he REALLY deserves it
OTA UPDATES:
Here is the OTA Updater app:
This is derived from original OTA App from gingermod but completely rewritten to match the New ICS Style guides from Google, and A complete Clean UP Of the code
Just click the
"CHECK NOW" And you've done!
you''ll have a similar screen:
You have all infos you need: Changelog, version, and the list of avaiable Updater and Add-Ons
There is also a section under this (just scroll) With the EXISTING Updates you've already downloaded:
When Finished download You'll be prompted to install NOW or LATER, click LATER to install MANUALLY
or APPLY NOW to install AUTOMATICALLY
DOWNLOADS
ROM
DOWNLOAD
MD5
Code:
879fc2e192667290001bc860b68581be Update-luca-4.1.2-AOSP_12092012-signed.zip
DISCLAIMER:
Doing This you've to be SURE of what you are DOING!!
ALWAYS DO A BACKUP FIRST!
If your phone does melt, you lose an arm, an asteroid hits you or simply SuperMario pops up from your phone...I'm NOT RESPONSABLE OF THIS!
REMEMBER TO PERFORM A DATA WIPE IF YOU FIND SOME PROBLEM!
A DATA WIPE MAY BE NEEDED ALSO IF YOU ARE ALREADY ON CBR!!
FAQs AND CHANGELOG IN NEXT POSTS!
CREDITS:
Cyanogenmod team
TEAM Hacksung
codeworkx
Entropy512
Xploid
espenfjo
Angelom & Guidox
Google
Koudd
SPECIAL THANKS
Guidox
kontinuity
thehaunted
sam87
Michael Weingärtner
Samitinjaya Mahapatra
They helped me betatesting the rom!
Thanks for giving me part of your time!
Sorry but I dont Remember all your XDA Nicks xD So if you prefer them, just pm me and i'll change it
------------------------------------------------
CHANGELOGs:
v0.2
Amplified Sound tweaked vol_hpgain values (Headphone Amp)
CRT Animation Fix
Open source audio ALL CREDITS TO CM TEAM ENTROPY CODERWORX
Updated to latest packages from Cyanogen
(libhardware, libhardware_legacy, hardware_samsung)
Latest cm kernel
Latest cm camera app (fixed FC on settings reset, better power button shot support zoom in/out with vol +/- )
Revert to MusicFX
Fixed Filemanager UI and permissions
Fixed Init.d support
v0.1JB
First Release
Update to android 4.1.2 (read changelog http://www.funkyandroid.com/aosp-JRO03R-JZO54K.html )
New 4.1.2 gApps
OEM-like Nexus system Specifically built around Gs2, includes specific
OEM-like rom signaturing (encaching security)
System optimizations
Optipng
Zipaligned
Deodexed
Rooted
Added OTA updates
init.d support
Cm10 camera
full gapps (Gnow working)
USB OTG Mouse and Keyboard support
Encached Media Quality (MP4 -STEREO- video recording (working 1080p))
Fixed Holo background banding
Dock settings (now USB Audio with official base works)
Optimized scrolling
Optimized launcher memory usage
Optimized memory/graphic/speed
HSPAP:15 support (H+)
FM-Radio support (install it from the OTA App)
Resolved RILJ Wakelock
Optimized MediaScanner
FAQs:
Q: Can I have AOKP/CM10 Features?
A: No, dont ask
Q: How can I set Soundboos (headphone amp)?
A: just go in terminal and type:
Code:
su
cbr soundboost X
X is a vaule from -20 to 20
Q: What are the known bugs?
A: the known bugs are
- TV Out Mirroring: not working (and will probably never work) (only video out works)
- No ProjectButter (and no CRT Animation)
- Audio 50% bug -> Use DSP Manager DynamicRangeCompression/PowerAmp Direct volume control
DO NOT ASK FOR THIS BUGS
Q: I really have many problems with this rom and "put_here_any_kernel" Kernel, can you help me?
A: NO. I DO NOT support officially ANY OTHER kernel different from CM One!
Q: I have FC or a bug, How to report it?
A: Be on FRESH INSTALL, with PROVIDED Kernel, if you have some FC, open terminal and type
su
logcat > /sdcard/log.txt
then send it to me, or put it on pastebin
If you have some SOD, panics or other, send me the dmesg of Kernel
Q: I cannot find my External SDCard!
A: Its in /storage/sdcard1, you can easly manage it with any filemanager
Q: Then can you mount it in /sdcard/external_sd??
A: NOPE, this is AOSP standard, and this will remain
and you have done!
Q: I have some strange issues with my ROM that nobody reported before. What should I do?
A: IFrist check if the MD5 Checksum is correct. Then flash ROM again and see if the issue is gone. If not wipe data. If not again make sure you DO NOT use any mod or other kernel not provided by ME
Q: My Quadrant score is not as high as Samsung ICS, What is this ****??
A: Quadrant/Antutu/Linpack means NOTHING, to test a rom, flash it, play with it a couple of days and see the performance, but NOT using benchmarks
Q: AudioOut_1 is draining the battery and causing Wakelocks, what to do?
A: Uncheck the touch sounds and lock sound in sound settings, then reboot
Q: I dont like the rom, it does not have many features and its ugly
A: Degustibus...Not my business, go away then
Q: I really like your rom, can I support in any way??
A: Yes, press THANKS, or donate using the banner in the signature or above my avatar... but PLEASE:
Consider donating also to Team Hacksung and CM9 team (Entropy512, XPloid, codeworkx) cause is THANKS TO THEM that we have Aosp
Q: I see, this rom is Open Source??
A: OF COURSE IT IS! See third Post to have instructions to build it!
COMPILING THE ROM ------> ADVANCED USER ONLY!!
Those instructions are tested and works on Ubuntu 10.04 an 12.04 (machines I Have)
For Extra settings please contact me and I'll try to help!
-Install the Android SDK
-Install needed pacckages:
Code:
git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
For 64bits enviroments also:
Code:
g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
-Create the enviroment where you'll going to develop
mkdir -p ~/bin
mkdir -p ~/android/system
-Install the Repository
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH
After this step, it may be necessary a reboot to have repo working from path
-Inizialize the Repository]/B]
cd ~/android/system/
repo init -u git://github.com/89luca89/android_manifest.git
repo sync -j16
This will take a while Go out for a walk xD
-Copy proprietary files
This is needed only the first time you compile, you must have a working CBR-JB rom, working ADB.
Make sure ADB Is working on your Machine
cd ~/android/system/device/samsung/i9100/
./proprietary-files.sh
This will put all proprietary files in the /vendor
- BUILD THE ROM
. build/envsetup.sh
lunch full_i9100-userdebug
make -jX (X= number of cores)
make -jX otapackage
This will build the complete rom WITHOUT gapps
If you want the complete build (like the one in th post) you have also to:
FOLLOW THIS GUIDE
http://www.kandroid.org/online-pdk/guide/release_keys.html
to create your signature keys (credits to Koudd that helped me sorting it out! )
put all Gapps (you can find the package, or simply manually take from CBR) in vendor/CBR/GoogleApps
then
vendor/samsung/CBR/tools/squisher
Will generate a signed flashable zip with also MD5sum
Reserved for Future
Great news, mate!
luca my friend, welcome back
Welcome back Maestro Gonna install this asap
Thanks! I Hope you like the rom cause I really enjoy it!
Just installed it... It is the fastest ICS I have used on GSII... Didn't find any bugs
Great news! I loved your GingerMod! I have couple of concerns flashing ICS mod. Do I need to first flash ICS bootloader before flashing Nexus SII.
Can I just flash the ROM via CWM? Also, what is MD5 (CSC?)
Do I have to do a full wipe if coming from another ICS Rom?
Ahhhhhh the ROM I have been waiting for!
How is this different to the other galaxy nexus rom?
Also I'm not sure if u can call ur rom that mate...
Sent from my GT-I9100 using xda premium
adamski123 said:
How is this different to the other galaxy nexus rom?
Also I'm not sure if u can call ur rom that mate...
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
The major difference between this and Faryaab's F1 ROM is that this is ODEXED and that one is DEODEXED. This is optimised for performance whereas that allows for theming etc. Visually, it won't make a difference but under the hood, this could be more fluid. Gonna have to give this a try.
Hmm OK I may try this rom. If I'm running f1s rom do I really need a full wipe? :L
Sent from my GT-I9100 using xda premium
to the OP .. ur missing a 'directions for install'
just a suggestion
xinhang said:
Great news! I loved your GingerMod! I have couple of concerns flashing ICS mod. Do I need to first flash ICS bootloader before flashing Nexus SII.
Can I just flash the ROM via CWM? Also, what is MD5 (CSC?)
Click to expand...
Click to collapse
Well yes, you can simply flash, just if you boot loop even with a data wipe, flash the cyanogen mod resurrection flashable via Odin, that sets all boot loaders compatible
MD5sum is a code to check if the zip is OK or corrupted so it will not be possible to have failure flash
goldencore said:
Do I have to do a full wipe if coming from another ICS Rom?
Click to expand...
Click to collapse
yes!
adamski123 said:
How is this different to the other galaxy nexus rom?
Also I'm not sure if u can call ur rom that mate...
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
well I know the other rom but sincerely I don't think the "intent" is the same...I develop an oem-lile rom, so its like the stock images of gnex, he does a pure aosp..., but even if are similar (aosp is aosp, optimization apart its the se for gnex nexus s and gs2...)
You cannot say this rom its not mine... you know just check the source code... its open source so just check, this is not a work you can do in a night... it might be only a coincidence, but still project are different
adamski123 said:
Hmm OK I may try this rom. If I'm running f1s rom do I really need a full wipe? :L
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes you need...
You can try to not wipe, but semember that in case of problems, the reason is the wipe not done
tdiddy1987 said:
to the OP .. ur missing a 'directions for install'
just a suggestion
Click to expand...
Click to collapse
Well, just flash the zip, is really necessary? XD
Inviato dal mio GT-I9100 con Tapatalk 2
Grear work
Sent from my GT-I9100 using XDA Premium HD app
installed, so far haven't faced any bug, great work again!
Installed running great so far. Is it possible to add reboot option in power menu.
Sent from my GT-I9100 using XDA
{
"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"
}
[ Unofficial CyanogenMod 10 Build on HTC DNA ]
git @ https://github.com/drewx2/android/ (Updated to download all necessary repos)
..CURRENT BUILD NOTES/HISTORY..
03.24.13: CM10 doesn't include support for csd-client enabled phones (which we need). I have built a work around for it to utilize our csd-client lib; hopefully it brings audio one step closer.
My audio changes can be found at a separate git repo @ https://github.com/drewx2/android_hardware_qcom
03.23.13: Current Audio Status
I have some time to look at things, so here just getting started and thought I would post the first strace for those interested. Looks promising and not too difficult.
Code:
writev(4, [{"\4", 1}, {"AudioHardwareALSA\0", 18}, {"ucm instance opened: 1082445752\0", 32}], 3) = 51
writev(4, [{"\6", 1}, {"AudioFlinger\0", 13}, {"int android::load_audio_interfac"..., 103}], 3) = 117
writev(4, [{"\4", 1}, {"AudioFlinger\0", 13}, {"loadHwModule() error -22 loading"..., 49}], 3) = 63
writev(4, [{"\5", 1}, {"AudioPolicyManagerBase\0", 23}, {"could not open HW module primary"..., 33}], 3) = 57
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"Not output found for attached de"..., 47}], 3) = 71
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"Failed to open primary output\0", 30}], 3) = 54
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"getDeviceForStrategy() speaker d"..., 74}], 3) = 98
clock_gettime(CLOCK_MONOTONIC, {205, 684889413}) = 0
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"getDeviceForStrategy() speaker d"..., 74}], 3) = 98
writev(4, [{"\6", 1}, {"AudioPolicyService\0", 19}, {"couldn't init_check the audio po"..., 54}], 3) = 74
ioctl(3, 0xc0186201, 0xbe961a28) = 0
Complete strace available here: http://bit.ly/Xx3M0v
-------------------------------------------------------------------------------------------------------------------------------------
There won't be any builds posted until one of the "not working" items has been fixed. I mostly likely will focus on audio this weekend.
If you have something meaningful to share, please visit http://webchat.freenode.net/?channels=CM10DNA
03.04.13 @ 03:29AM: Wifi *now* really working
03.04.13 @ 03:29AM: Wifi now working.
Enable 3 dot menu: Settings -> Hardware keys -> Show action overflow [check]
Working:
Radio/RIL (no sound, so can't hear yet), SMS / MMS, 3G / 4G Data, Display, Orientation, Sensors, Lights, NFC, Torch, GPS (not tested), Wifi
Not working:
Camera, Audio, Bluetooth
To Do list
I plan to do bionic/kernel optimizations once all features working.
Click to expand...
Click to collapse
..INSTALL INSTRUCTIONS..If you do not have S-OFF, you need to unzip the file and flash the boot.img inside via fastboot.
Install Instructions:
1) Download http://bit.ly/W0RAY8
2) Reboot to recovery of your choosing; wipe system/data/dalvik-cache/cache.
3) Install downloaded zip
4) Reboot.
5) Enjoy.
Google Apps @ http://goo.im/gapps/gapps-jb-20121011-signed.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
.SPECIAL THANKS FOR DONATING.
RuinedByMTV, drmp3z
kronikings, danahern, karn101, Majik Mushroomz, Matt P., Matt B., pio_masaki, Droidika, Wheelchairmitch, MrIcky, liquidhaste, jamiethemorris, rainabba
.SPECIAL THANKS.
Flyhalf205, x3demond3x[debugging]
dsb9938 [cmdline boot option]
x3demond3x [egl fix]
Jarocks [resized bootanimation/debugging], pio_masaki [debugging],
jcase [unlock], dees_troy [twrp], beaups, jcase, Dr_Drache, dsb9938 [S-OFF]
.... and of course the CyanogenMod team and those who laid the foundation for the DNA....
..WANT TO HELP? HERE ARE SOME DEBUGGING TIPS..1) Flash boot.img
2) On cmdline do "adb logcat"
Click to expand...
Click to collapse
If you're ever in the mood to donate, don't forget about the others that have helped advance the HTC DNA to new levels (e.g. dsb9938, jcase, Dr_Drache, beaups, CM team, or XDA for bringing us all together!). Although, I may be working on CM and it may seem like a completely different project, in many ways we all rely on each other to help make the DNA better.
Click to expand...
Click to collapse
I can't help you with specifics but the guys over on the nook color forums have great guides on building and may be amenable to questions if no one here gives you anything useful
sent from my unlocked and rooted droid DNA
jamesbra said:
I can't help you with specifics but the guys over on the nook color forums have great guides on building and may be amenable to questions if no one here gives you anything useful
Click to expand...
Click to collapse
Thanks. Brings me back to the days when I was writing some early scripts for the Nook Color... when you had to flash the "harder" way. Anyhow, it reminded me of just mounting each partition separately (/dev/block/mmcblk0pXX). Found kernel/system logs, just what I wanted.
What about radio??
Sent from my HTC6435LVW using xda premium
typeriz said:
What about radio??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That's a whole separate issue. We can have a Rom booting and usable without the ril working. Granted, this booting will most likely help with ril advancement.
Sent from outer space...
drewX2 said:
I've successfully built CM 10 on the DNA, however I'm stuck with debugging after booting in standby (assuming). For those that have built new roms on unsupported devices, how did you debug the boot process? Yes, I understand to use logcat/ddms/etc. I boot into standby with a black screen (no boot loop). Sdcard mounts once I get to black screen, however I built kernel from source as well so no hacks have been applied yet.
Also, when taking any kernel available right now, pulling it apart and remerging with no changes (just verifying process), I go into a boot loop on a working Rom (genome/ukb)
This is what I am doing to recreate boot.img:
Code:
(boot.img taking from DNA cubed kernel, I've renamed kernel and ramdisk)
unbootimg boot.img
mkbootimg --output boot.img --kernel kernel --ramdisk ramdisk.cpio.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=dlx user_debug=31' --board '' --base 80600000 --pagesize 2048
Any tips would be great so I can finish up and share. Seems so silly that I can't even remake a working boot.img after spending 20+ hrs working on CM10. It seems I'm a bit slow to get back into the swing of things since taking a hiatus from programming for several years.
Click to expand...
Click to collapse
I have gotten to the same point as you in my AOSP venture with the DNA. From my findings, without the correct kernel drivers being administered from the gate, the USB (debugging) features are not going to work properly. I am in the process of finding a kernel developer who is familiar with Sense (HTC) devices to build the proper kernel to make this possible. With the help of Dr_Drace I was able to put together a working DLX build tree and have successfully compiled FactoryROM (which is 4.2 AOSP based) but am stuck at the end of the boot process. And like you, I am unable to gather any logs due to the lack of USB access. We need a reliable kernel developer to get us past the hurdle. Unfortunately I am not one of them. As far as RIL, it's anyone's guess as to its functionality once we get things booting correctly. We have all of the drivers, it's just making them work together. :fingers-crossed:
MyComputerDoctor said:
I have gotten to the same point as you in my AOSP venture with the DNA. From my findings, without the correct kernel drivers being administered from the gate, the USB (debugging) features are not going to work properly. I am in the process of finding a kernel developer who is familiar with Sense (HTC) devices to build the proper kernel to make this possible. With the help of Dr_Drace I was able to put together a working DLX build tree and have successfully compiled FactoryROM (which is 4.2 AOSP based) but am stuck at the end of the boot process. And like you, I am unable to gather any logs due to the lack of USB access. We need a reliable kernel developer to get us past the hurdle. Unfortunately I am not one of them. As far as RIL, it's anyone's guess as to its functionality once we get things booting correctly. We have all of the drivers, it's just making them work together. :fingers-crossed:
Click to expand...
Click to collapse
I'm just going to try stripping as much away as I can to boot and then slowly add things back in. On a side note, I've made a working version of touch clockworkmod recovery. I am going to modify it to add some additional options before sharing (unless someone gets around to it before I do).
What I suggest doing is mounting /dev/block/mmcblk0p24 manually via working recovery. This is the log partition; system.log and kernel.log are written to it.
Please keep us updated on your progress. It would be greatly appreciated. And yes you may be part god.
Please try to keep this thread focused on development and free of clutter. The Thanks button still works just fine.
Do either of you have the device/vendor posted to Github by chance? I actually started putting one together but haven't had much time to actually make progress.
Which kernels have you used with source built Rom? Tried the stock kernel by chance? I always feel its a good starting point. Have either of you uploaded the zip? I can flash and take a look... They say two heads are better then one so if we're all working on the same thing I'm sure progress will be made! Lol
Sent from my HTC6435LVW using Tapatalk 2
Ill try to get it up or post a zip tonight (not workable, but see if you can troubleshoot ). I was off for a bit bit but now working four long shifts in a row.
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
leech2082 said:
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
Click to expand...
Click to collapse
Thanks for helping out anyway you can. Now that I've completed my work stretch, I can go back to working on this a bit. What he is saying is essentially what I am doing, however, the simple fact of taking a working boot.img, splitting it up, then remaking with zero changes and it it not working anymore has eluded me.
drewX2 said:
Thanks for helping out anyway you can. Now that I've completed my work stretch, I can go back to working on this a bit. What he is statins is essentially what I am doing, however, the simple fact of taking a working boot.img, splitting it up, then remaking with zero changes and it it not working anymore has eluded me.
Click to expand...
Click to collapse
Wink, wink!
D
.
dsb9938 said:
Wink, wink!
D
.
Click to expand...
Click to collapse
Haha judging by the amount of thanks I think we are all hoping that aosp is coming really soon for xmas and you guys are just playing us, haha. Thank you for your amazing work bringing the world of real android closer to reality
leech2082 said:
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
Click to expand...
Click to collapse
Leech I actually worked with him two weeks ago to build an Tiamat AOSP kernel for the DNA. Since then I've had my birthday and 3 family members birthdays and now Christmas. The zip is still on my system waiting to be flashed We'll get it to work. The dudes built kernels for every single HTC device to date practically. I have faith.
Kernel building no longer issue. I just had one command left out which kept giving me a PITA. Now to find out which things can be eliminated from HTC and still boot.
And now to get the hardware to work properly lol. Battle has just begun. Great work guys. Will be downloading and attempting to fix some things after Xmas.
Sent from my DNA.
When did they add xxhdpi to aosp?
Sent from my SGH-I747 using Tapatalk 2
idkwhothatis123 said:
And now to get the hardware to work properly lol. Battle has just begun. Great work guys. Will be downloading and attempting to fix some things after Xmas.
Sent from my DNA.
Click to expand...
Click to collapse
Do you really have to wait until after Christmas? Come on.
:victory:
{
"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"
}
CarbonRom KitKat for Nexus One!
Fits on 220mb HBOOT!
7/15 Update:
4.9 toolchain
Heads Up notifications (as opposed to Hover)
updates to random other stuff as well
From Carbon themselves:
CarbonRom is an aftermarket firmware based on the Android Open Source Project.
We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn’t been mentioned here. If you feel you have been unfairly left out, please – let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
https://carbonrom.org/features/ (Pretty much everything.)
Nexus One specific:
Trackball wake toggle (Settings -> CarbonFibers -> Buttons)
Download here.
Read instructions before installing.
Installation:
If you don't know what hboot is, please read this first: http://forum.xda-developers.com/showthread.php?t=1270589
HBOOT /system size 220
I recommend cache at 10mb
Wipe data.
This must be done before flashing zips if you want Mounts2SD to work properly, as Mounts2SD's zip writes to /data.
Install ROM.
(Optional but highly recommended) Install ext script such as Mounts2SD download here - same zip as my CM11)
You will need an ext partition on your SD card.
You can customize the settings after installation with the Mounts2SD app. You may want to move application libraries, for example.
TWRP also seems to not like Mounts2SD. CWM and 4EXT seem to work fine for me.
Known Bugs:
Don't even try screen recording
Evervolv base
HWA video recording/playback not working
no MMS
wifi tethering not happy - only works on no password
Keyboard
If system language is set away from English because of SIM card, keyboard will crash. Set up phone in English.
I myself am having some trouble downloading large applications, not sure where this problem is from
Big thanks to:
Evervolv - device/kernel/other repos. They're the guys that keep the old Nexus One going 4 years after it came out.
CarbonRom and all those who maintain the sources they use (Slim, PA, AOKP)
WoH, csytracy who helped me earlier on
dk_zero-cool, for mounts2sd.
spezi77, for maintaining some handy sources with qsd8k mods
Some of my sources are available on github: https://github.com/parkedraccoon/android_device_htc_passion/tree/kitkat-carbon, https://github.com/parkedraccoon/android_packages_apps_CarbonFibers
Carbon is just about as slim as CM, but does not include a music app. That's how I left the boot animation and some audio files in there.
Old downloads:
https://drive.google.com/folderview?id=0B6H3m9ss3c8scnRKMGRPLS1QaW8&usp=sharing
Old Mounts2SD:
Some have reported problems with the current Mounts2SD script. Attached to this post is an old installer I used to use back in the 4.1 days that seems to work on sd cards that the new Mounts2SD does not. It is an Aroma installer - I recommend default settings except check dalvik along with apps.
Why is this not the main zip? Because it takes more effort and the current Mounts2SD script seems to work fine for most.
Looking for ART? I have not been able to make ART boot on Carbon, even when using the exact same method as with CM. I may continue playing around but I doubt I'll find anything.
Thanks, I try it now!
---------- Post added at 11:18 AM ---------- Previous post was at 10:42 AM ----------
Riddle78 said:
Thanks, I try it now!
Click to expand...
Click to collapse
It should not be, the same problem of CM11. After following the procedure, the system remains locked on the opening!
Riddle78 said:
Thanks, I try it now!
---------- Post added at 11:18 AM ---------- Previous post was at 10:42 AM ----------
It should not be, the same problem of CM11. After following the procedure, the system remains locked on the opening!
Click to expand...
Click to collapse
Check the second post. I added an older M2SD script that is more of a hassle to set up, but seems to fix problems I had on my older sd cards.
parkedraccoon said:
Check the second post. I added an older M2SD script that is more of a hassle to set up, but seems to fix problems I had on my older sd cards.
Click to expand...
Click to collapse
Ok, I try and let you know!
For the keyboard I can directly install the apk?
Nice
Thanks for let nexus one live
Would ask is there wifi region setting
http://forum.xda-developers.com/showthread.php?p=50152996
pretty look! nice work, thanks you!!!
So, it works very well apart from the usual problems. Try not to abandon it because it is really wonderful!
Is the system font does not contain Asian Languages?
I could not see any Chinese/Japanese characters by using this ROM
downloading... will install soon and will provided the feedback later. thanks for the rom!
---------- Post added at 03:46 AM ---------- Previous post was at 03:43 AM ----------
i think the zip ( m2sd Aroma) should be on the cm thread rom too. just to mention.:good:
Lockscreen setting Force Close.
When i jump to Lockscreen > Notification in Carbon Fibers, its Force Close. I try to disable widget on lockscreen to avoid camera widget.
There is a problem on the volume of notifications! Although the volume is set to maximum, the notification sms is very quiet!
carbon setting FC so i cant disable poket mode
Hi, great !!!!
I also have the audio notification problem !! Any Idea to solve it??
rs1turbo said:
Hi, great !!!!
I also have the audio notification problem !! Any Idea to solve it??
Click to expand...
Click to collapse
Riddle78 said:
There is a problem on the volume of notifications! Although the volume is set to maximum, the notification sms is very quiet!
Click to expand...
Click to collapse
I'll look into it, but I'll be busy this weekend.
Akram-aat said:
carbon setting FC so i cant disable poket mode
Click to expand...
Click to collapse
It's an issue in Carbon itself, actually. I'll try and make a workaround if I have time this weekend (again, I'll be busy)
It's beautiful.
The Carbon ROM is the ROM that has more style, so far, to Nexus One But most important is fluency. So I want to ask:
Is it as smooth as CM 11?
Anyone who can answer estrablecer diferecencias Thanks beforehand.
Theericgames said:
The Carbon ROM is the ROM that has more style, so far, to Nexus One But most important is fluency. So I want to ask:
Is it as smooth as CM 11?
Anyone who can answer estrablecer diferecencias Thanks beforehand.
Click to expand...
Click to collapse
In test carbon for hour and I thing cm more stable cuz wifi region my phone freeze and become unstable
New update posted! Lots of new things. I love removing things from the Known Bugs list!
ROM itself:
Gesture typing fixed!
The ROM is not so tightly bound to 220MB, so it will take less time to install. Recommended hboot size is still 220.
Default ringtone not existing fixed. (This fixes the 'soft,' actually completely silent, notification sound, at least in some cases.)
I have fixed the error in CarbonFibers on Notifications menu where it crashes.
I may push my fix upstream to Carbon but for devices that do not require slimming, it is not needed.
Carbon:
Force high gfx mode (transparent status bar/navbar) is now officially part of Carbon. Performance -> Force high-end graphics. Surprisingly enough our very own drewis/texasice's commit is used!
Slim's PIE added
Lots of small tweaks, etc.
Check first post for update link.
Cool
Thanks for the new arrangements, and say why do not you fix some.
For the mistake of downloading large apps, you can use this page to download applications from the PC and then transfer them to your smartphone:
APK Downloader WEB
Well, if I find a solution for an error, or find a new error, the report you.
After Installing Mount2SD Skype Restart Mobile ... Plz Fix ... Grt RoM
{
"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"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimLP is the project name for SlimRoms based on Android 5.0 Lollipop and offers the following original features:
Slim Dialer
A full replacement of the official Google closed source dialer with added features. - We've got you covered.
Privacy guard
Disable unnecessary permissions set by app developers. - Privacy is part of the experience.
Slim Center
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticons..etc. - You'll be tapping away to your heart's content.
Custom Shortcuts WIP
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - Customize it the way you like it.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
--------------------------------------
Instructions:
Recovery: use my TWRP 2.8.1.0 recovery.
Make sure you're on the UCMD3 radio
Format /system, /data and /dalvik
Flash the ROM
It's recommended to reboot and let it settle!
Reboot to recovery
Flash GApps if desired
Reboot
ROMS
Slim-quincyatt-5.1.1.beta.0.9-UNOFFICIAL-20151010-1515.zip
GAPPS
Gapps
What works?
RIL
MMS
Camera
Video Recording and Playback
What doesn't work?
1080P video recording
flashlight
you tell me?
USE_ONLY_THIS_UNOFFICIAL_TWRP!!!!!
TWRP 2.8.3.0
I tried the 0221 build and had the wake issues. I'm gonna try the 0342 build and see if that does it! I've been experimenting building kernals for the S3 and XT912 to learn! I'm gonna start working on the I717 tonight and see if I can help everyone out! And thanks again for all of the hard work gimmeitorilltell!
Sent from my DROID SPYDER using XDA Premium 4 mobile app
SgtTeabag said:
I tried the 0221 build and had the wake issues. I'm gonna try the 0342 build and see if that does it! I've been experimenting building kernals for the S3 and XT912 to learn! I'm gonna start working on the I717 tonight and see if I can help everyone out! And thanks again for all of the hard work gimmeitorilltell!
Sent from my DROID SPYDER using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, the 342 seems to work, but also has wake issues after a while. And looking forward to testing your Kernals :good:
Will try NOW and use it from tomorrow daily driver to test from MIUI!
[ Updated! ]
1. Updated to TWRP 2.8.1.0 recovery.
2. Not sure for i717 => 'UCMC1 radio"
3. Tried Both builds
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0342.zip
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0221.zip
=> Keep rebooting as soon as it boots to home screen after you click "power" button to turn off and try to wake up back.
Still it was enough excitement feeling to see the LP home screen on i717!
Hope we could see working build soon.
P.S. Can any developer could also change PIT(partition modification original 2GB limit) specially for new build?
pointdooly said:
Will try NOW and use it from tomorrow daily driver to test from MIUI!
[ Updated! ]
1. Updated to TWRP 2.8.1.0 recovery.
2. Not sure for i717 => 'UCMC1 radio"
3. Tried Both builds
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0342.zip
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0221.zip
=> Keep rebooting as soon as it boots to home screen after you click "power" button to turn off and try to wake up back.
Still it was enough excitement feeling to see the LP home screen on i717!
Hope we could see working build soon.
P.S. Can any developer could also change PIT(partition modification original 2GB limit) specially for new build?
Click to expand...
Click to collapse
After Exact Step of flashing, I could load 0342 firmware without reboot issues.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install SlimFast zip from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
11. Flash SuperSU
12.Wipe Cache/Dalvik
13. Reboot
Wow! It is really working LP except except internal & external sd cards which is important.
=> Can't use camera and video camera at all since it can't save to internal SD.
When you open camera app, you will receive this errir "Camera app says "Insert an SD card before using the camera"".
everything seems to work fine but no audio
kukke5 said:
everything seems to work fine but no audio
Click to expand...
Click to collapse
pointdooly said:
After Exact Step of flashing, I could load 0342 firmware without reboot issues.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install SlimFast zip from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
11. Flash SuperSU
12.Wipe Cache/Dalvik
13. Reboot
Wow! It is really working LP except except internal & external sd cards which is important.
=> Can't use camera and video camera at all since it can't save to internal SD.
When you open camera app, you will receive this errir "Camera app says "Insert an SD card before using the camera"".
Click to expand...
Click to collapse
All the issues we're having with this lovely rom, @gimmeitorilltell is trying to fix. We have to wait for the next update. Hopefully @SgtTeabag has a Kernel for us to fix some of the issues
New build in OP! Wake lock issues squashed! Still no audio! Videos play except 1080, camera works... Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-2324.zip
New BUILD with Audio
OP has it with audio, video recording & playback!
following your progress with great interest! Thanks again.
installation went without a hitch.
i used cwm 6.0.4.3
i wasn't able to setup an apn.
the screen said that the apn settings are not available for this user.
tried to add them anyway but wouldn't save.
gimmeitorilltell said:
OP has it with audio, video recording & playback!
Click to expand...
Click to collapse
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
beenkenobee said:
installation went without a hitch.
i used cwm 6.0.4.3
i wasn't able to setup an apn.
the screen said that the apn settings are not available for this user.
tried to add them anyway but wouldn't save.
Click to expand...
Click to collapse
Is your baseband working ?
TeamAndroid14 said:
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
Is your baseband working ?
Click to expand...
Click to collapse
nope
TeamAndroid14 said:
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
Is your baseband working ?
Click to expand...
Click to collapse
beenkenobee said:
nope
Click to expand...
Click to collapse
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
My device is on UCMD3 version.
gimmeitorilltell said:
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
Click to expand...
Click to collapse
@gimmeitorilltell , Thanks brother, I think the audio isnt working still, im not sure if its my phone.
gimmeitorilltell said:
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
Click to expand...
Click to collapse
Don't know if this helps, but no audio or baseband on Validus or Broken either.
Sent from my SM-T310 using XDA Premium 4 mobile app
TeamAndroid14 said:
@gimmeitorilltell , Thanks brother, I think the audio isnt working still, im not sure if its my phone.
Click to expand...
Click to collapse
dparrothead1 said:
Don't know if this helps, but no audio or baseband on Validus or Broken either.
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have audio on my device, can you all confirm whether you do or don't?
gimmeitorilltell said:
I have audio on my device, can you all confirm whether you do or don't?
Click to expand...
Click to collapse
I am on the 342 build...it has no audio of any kind.
Sent from my Nexus 6 using XDA Premium 4 mobile app
{
"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"
}
Sailfish OS’s heritage lies in Nokia times, especially in the MeeGo operating system. Prior to 2011 Nokia and Intel had a vision of an open mobile operating system. Together they invested around 1 billion USD to the project and created an open source based operating system called MeeGo, which was used as a basis for several devices, such as the iconic Nokia N9. Although the Nokia N9 became the beacon of open source operating systems, Nokia decided to end the project and chose instead to continue with Microsoft’s Windows Phone OS. The rest of that is another story.
For more information about SailfishOS click here.
SailfishOS has now been successfully ported to Redmi 2 and here I am sharing the steps to install it on your phone.
Code:
Disclaimer: Your warranty is now void. You will lose all your data on your phone and may render it unusable. This software is provided as is without any warranty of any kind whatsoever. The user shall solely be reponsible for any consequence arising out of following this guide. I, or anyone else shall not be held responsible for bricked devices, dead sd-cards, thermonuclear war, you getting fired because the alarm app failed or any other consequence of following this guide. The linked zip contains some proprietary files.
tl;dr I wont be held responsible for any unfortunate incidence.
I'd like to thank the following for their support and sources. (In no particular order) -->
@mal-, @kimmoli, @stskeeps, @Litew, @jusa_, @nokius, @sledges, @ketut.kumajaya, all other SailfishOS porters and The Cyanogenmod Team.
Prerequisites -->
1) Latest TWRP recovery installed (Others may work too but I haven't tested). You can get it here-->http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
2) cm-12.1-20151014-UNOFFICIAL-wt88047 zip by kumajaya. You can get it here--> http://forum.xda-developers.com/redmi-2/development/rom-cyanogenmod-unofficial-builds-t3200883
3) SailfishOS zip file. Download link given below.
This is not an Android ROM and thus the instructions to install are quiet different. Follow them carefully.
1) Boot to recovery. Wipe cache, dalvik-cache, system and data.
2) Copy the Downloaded files to the sdcard via USB.
3) Install cm-12.1-20151014-UNOFFICIAL-wt88047. Do NOT reboot after installing.
4) Install SailfishOS zip file. The installation will take around 10 minutes so don't think that its stuck. Ignore any errors about being unable to mount data partition.
5) Reboot System when installation succeeds.
Screenshots-->
Some more Screenshots here courtesy of @Innfinite4evr
Notes-->
1) This is not an Android ROM. Android apps will not work right now. But a way for Android apps to work is being developed by some community members and will soon be available.
2) Music player is not available by default. You can get it by opening the terminal (in-built) and and running " devel-su zypper in jolla-mediaplayer ". It will ask for a password which can be set in Settings>Developer Options. It will be there from next version.
3) For advanced users, you can ssh into the device after setting a password in Developer options using ssh [email protected] over USB.
4) Do not register for a Jolla account. You will get an error about failed IMEI registration. This will be fixed as soon as Jolla allows ported devices to be registered.
5) The Store will not work. It needs a Jolla account. You can however use the openrepos warehouse for installing apps. https://openrepos.net/content/basil/warehouse-sailfishos . You can either go the link via the browser on your device and download it. Then go to Settings>Transfers and click on the file name to install it. Another method to install it is to download it to your computer and use scp to transfer to to /home/nemo/ and use " pkcon install-local <name of file> " via an ssh terminal.
6) MTP over USB does not work. (Mass Storage technically works but is unusable for all practical purposes)
7) The battery life is currently being affected by the sensors. It will probably be fixed in the next version.
Download Link -->
https://www.androidfilehost.com/?fid=24580943222146342
DO NOT SHARE MY WORK WITHOUT MY EXPLICIT PERMISSION. IF YOU ARE SHARING, LINK TO THIS POST.
UPDATE--> New kernel released.
* For fixing bluetooth and Flashlight, use kumajaya's cm-12.1-20160318 as the base. then install SailfishOS and finally flash the new kernel ( https://www.androidfilehost.com/?fid=24591000424942423 ). Bluetooth will not work after a reboot. To make it work again, use " devel-su rfkill unblock bluetooth " and reboot. Camera will break and to fix it, use vim to make the changes from ( https://github.com/adeen-s/droid-config-wt88047/commit/ecda269bd120405a5ff3ab985e558abcfe93c916 ) in /etc/dconf/db/vendor.d/jolla-camera-hw.txt
and then execute ( dconf write /apps/jolla-camera/primary/image/imageResolution "'3264x2448'" ).
The new image will contain these changes already but I need some more time before releasing it.
Bugs or issues? & BTW can we use it in multi rom if yes then can u pls guide
Great Job @adeen-s !
Would definitely give this a try and report back soon.
Peace out ✌
Most innovative Os finally for redmi 2 thank you so much dev for this awesome os .
Thank u.. gonna try!!!?
Z.E.U.S said:
@salahXDA6805
This is on behalf of the whole Redmi 2 community.
Pls stop spamming threads and asking unnecessary questions to the devs.
This irritates them (as @s.sawrav).
As in this case multirom works only on MM based roms and this is not based on android.
Pls do some research first , Google will help you !
Hope you understand this .
Peace out
Click to expand...
Click to collapse
Im just asking my query not spamming so pls and im not irritating anyone and sailfish works with multi rom but i want to know about the procedure so pls stay out dev is there to answer me and i didn't asked u whether it works with multirom or not
Wow,seems amazing and i will give it a try...thnx for bringing this os to our little beast....and that click here is not working i think............to know more about sailfish os "click here"... :‹
revelation
adeen-s said:
This is not an Android ROM
Click to expand...
Click to collapse
hats off for this brave move!
i've been waiting for sailfish since forever (oviously like many others)
although these days i need a fully functional phone (w/ andro-apps) i'm looking forward to further development << hope you will keep up your work and scratch those issues one-by-one
Q: since i've never played with an actual sailfish os, logically i'm not aware of the (dis)advantages/performance; but i did give a go to he modified launcher [you can find an old version here, and a mutant on the play store - stella launcher]; so is there any possibility to port it to our beloved redmi2? i know it would be much appreciated by the community
thank you once again for your valliant effort!
:good:
Finally something new in our redmi 2 community. Keep up the good work @adeen-s. Looking forward to this thread. ✌?
salahXDA6805 said:
Im just asking my query not spamming so pls and im not irritating anyone and sailfish works with multi rom but i want to know about the procedure so pls stay out dev is there to answer me and i didn't asked u whether it works with multirom or not
Click to expand...
Click to collapse
MultiROM supports Sailfish but right now, it is only available for MM based ROMs on Redmi 2. If it supports LP based ROMs, it will be made available.
adeen-s said:
MultiROM supports Sailfish but right now, it is only available for MM based ROMs on Redmi 2. If it supports LP based ROMs, it will be made available.
Click to expand...
Click to collapse
Thanks bro for your repli:good:
salahXDA6805 said:
Thanks bro for your repli:good:
Click to expand...
Click to collapse
Although, there is a way to switch between CM-12.1 and SailfishOS just like MultiROM, only a bit more tedious. You can extract boot.img from cm zip and hybris-boot.img from Sailfish zip. Flash boot.img when you want to boot to CM and flash hybris-boot.img when you want to boot to Sailfish.
Also, I'd prefer if you press the thanks button instead of replying like this.
@adeen-s can I use newer builds of cm12.1? The one you mentioned in your thread is quite old.
Sent from my 2014818 using Tapatalk
Ashish94 said:
@adeen-s can I use newer builds of cm12.1? The one you mentioned in your thread is quite old.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
You can try. However, it won't matter as CM is used only for the Android HAL. It has got nothing to do with how Sailfish works. It just acts as a bridge between Sailfish and the hardware which was meant to run Android.
If you try with a different CM-12.1, could you please post the output of " /usr/libexec/droid-hybris/system/bin/logcat " You can access the terminal via "telnet 192.168.2.15 2323" or via ssh as mentioned in the OP. If you cannot connect using these ways, you could check the output via the terminal app and tell if it has some errors mentioning AKMD2 .
hey thanks for this fluid rom.i hope bugs will be fixed soon ...some more ss for those who wanna see.....https://drive.google.com/open?id=0B_zOA86X6Ez_WGJORkhvMDAxV2c Hi thanks if u like it
Innfinite4evr said:
hey thanks for this fluid rom.i hope bugs will be fixed soon ...some more ss for those who wanna see.....https://drive.google.com/open?id=0B_zOA86X6Ez_WGJORkhvMDAxV2c Hi thanks if u like it
Click to expand...
Click to collapse
Please list all the bugs that you noticed. I haven't noticed anything besides high battery drain and lack of USB MTP. Also thanks for the screenshots, Do you mind if i link them in the first post ?
i faced these bugs
adeen-s said:
Please list all the bugs that you noticed. I haven't noticed anything besides high battery drain and lack of USB MTP. Also thanks for the screenshots, Do you mind if i link them in the first post ?
Click to expand...
Click to collapse
never mind PS-add ss in post
bugs:camera,calling not working and single sim only
and warehouse should be included by default or else people will become mad......
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
Innfinite4evr said:
never mind PS-add ss in post
bugs:camera,calling not working and single sim only
and warehouse should be included by default or else people will become mad......
Click to expand...
Click to collapse
i used cm12.1 20160318
Innfinite4evr said:
never mind PS-add ss in post
bugs:camera,calling not working and single sim only
and warehouse should be included by default or else people will become mad......
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
i used cm12.1 20160318
Click to expand...
Click to collapse
Strange, they should work perfectly. Have you tried restarting the phone.
If a restart does not change anything, then post the output of "journalctl -f -l -a" . To get root access, use "devel-su" in terminal. You can set password for root in developer options. Also post the output of " ls -l /dev/ "
Innfinite4evr said:
never mind PS-add ss in post
bugs:camera,calling not working and single sim only
and warehouse should be included by default or else people will become mad......
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
i used cm12.1 20160318
Click to expand...
Click to collapse
Since you're using a different CM version than specified, could you also post the output of " /usr/libexec/droid-hybris/system/bin/logcat"