Disclaimer:
Code:
[FONT="Book Antiqua"][SIZE="4"]All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking your device.[/SIZE][/FONT]
{
"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"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Features:
-- Odexed for faster performance (only in official releases, nightlies are deodexed)
-- Incremental updates
-- OTA updates - update on the fly!
-- Native exFAT support (Samsung devices only)
-- ListView animations
-- Calendar - with lunar and solar calenders
-- Bulk SMS recipients
-- Adjustable SMS font size
-- SMS sending delay
-- Smart dialing
-- Speed dialing
-- IP dialing
-- Custom carrier name
-- Network speed in status bar (upload and download!)
-- Built in timer in Apollo - determine when to stop playing music
-- Unique Power Saver functions!
-- Custom screen off animations
-- Lockscreen notifications
-- Multiuser support
-- Smart Lock
-- Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Links:
-- Official website
-- Google Plus Community (join us for faster response!):
-- Statistics
-- Official Build Status
-- Bug Tracker
-- Changelogs
-- MoKee Github
-- MoKee Code Review
Downloads
-- ROM - UnOfficial - n7100
-- ROM - UnOfficial - t0lte
-- Latest Google Apps for Lollipop
Donations:
-- All donations will be used for build server.
You can scan this QR CODE to donate me by Alipay.
Installation Instruction
-- Make a backup of your ROM
-- Wipe data/factory reset
-- Format /system
-- Flash ROM
-- Flash Gapps
-- Reboot
Notes/Faqs
-- First boot might take a while around 5 to 10 minutes so don't panic, it will boot fine.
-- This ROM has not been tested with dual sim, so flash it by your own risk.
-- Working and Not working list is as same as CM12 unofficial Build
-- Restore from 4.4.4 rom is not recommanded (Do it at your own risk).
-- Download google camera for photos and video.
-- Use search button for your errors first and than put a query in here.
-- Do not ask ETA, it will not make release any faster than what it is.
Credits:
-- MoKee Developers
-- CyanogenMod
-- AOSP
-- Koush for open-sourced SuperUser
-- Slim Roms
-- OmniROM
从我的 iPhone 发送，使用 Tapatalk
Great to see new lollipop rom for n7105
---------- Post added at 05:24 PM ---------- Previous post was at 05:00 PM ----------
[/COLOR]Downloading now. Will report
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
King Kaze said:
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
Click to expand...
Click to collapse
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
I'm glad you said what I was thinking.
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
'tis up to you. I know I wouldn't use a ROM, no matter how good it is, if it's XDA thread was sloppy. That is, after all, the most important thing when it comes to ROMs. I mean, if a builder insists on spending so much time to perfect the build that they cannot cater the thread to anyone and everyone, they shouldn't even bother.
Have a good one.
Features I didn't like...
Lot of Asian characters in settings and in some popups ..
Packaged with some search engine in Asian language.
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
R0B3RTF1SH3R said:
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
Click to expand...
Click to collapse
Not a asian language. this is chinese. and I agree with that because the third party app comes with chinese. third party app in AOSP rom...well...
Guys just freeze the Chinese apps or uninstall. I'm sure you guys knew that. The KK version of Mokee was nails. I'll wait for more features to start using this build, but I'm looking forward to it.
In Samsung the word Note 2 is pronounced t0lte.
King Kaze said:
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
Click to expand...
Click to collapse
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
dicksteele said:
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
Click to expand...
Click to collapse
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
King Kaze said:
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
Click to expand...
Click to collapse
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
dicksteele said:
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
Click to expand...
Click to collapse
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
msm86bp_1032,365.70.00R
Click to expand...
Click to collapse
R0B3RTF1SH3R said:
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
Click to expand...
Click to collapse
The screenshot does not come from a N7105, but from a MotoG
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
ddaazzzzaa said:
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
Click to expand...
Click to collapse
skip all. goto input settings, keyboad, advanced, enable hardware keyboard.
Where is N7100 one?
NisseCool said:
Where is N7100 one?
Click to expand...
Click to collapse
i think if u have a n7100 modem and kernel handy u can use any n7105 rom. dont quote me but im pretty sure.
Related
First of all I want to make some things clear:
This is my own custom build I made with the help of this great tutorial: http://forum.xda-developers.com/showthread.php?t=775505
This has nothing to do with the offical nightly build from Cyanogen and his team.
I won't provide any support for this. If you want to flash this you should know what you do. Don't ask me anything like "How do I flash this?".
This could be even more unstable then the official nightly build since I add commits that are not merged. It's a great feature preview, but I can't guarantee anything. I can't tell you if the features you see here will make it into any official build.
What is it?
Its a custom build of the latest Cyanogen sources spiced up with some not (yet?) merged patches.
What's inside?
A basic ROM with "a2sd light" and without g-apps. I removed ADW Launcher too since it's lags, included is the stock Android Launcher2.
I also removed CMStats since this one isn't anything official and could be more buggy then anything else.
Whats "a2sd light"?
Its like the original a2sd from here: http://forum.xda-developers.com/showthread.php?t=715940
but I removed all things that handle the dalvik-cache. I tried the original a2sd and didn't like it since it moved the /cache/dalvik-cache/ back to /data. Don't know if thats the way it should be.
I don't know how often I will make new builds, it depends if I find new things I want to try. If there are no new commits that interest me I won't make a new build.
I will only upload builds that work for me. So the basic stuff should work for everyone, if it doesn't try to wipe before flashing. If it still doesn't work use the official nightly/RC/stable/whatever... (Thats the point with "I won't provide any support").
So whats inside today/night?
All commits that were made until 28.Nov 2010 05:00pm (look here to get some details: http://review.cyanogenmod.com/#q,status:merged,n,z)
+ updateted gesture support on Lockscreen
+ custom app for lockscreen messaging slider
- User can now define unlock and sound toggle gestures.
- Lockscreen tabs can now be fully disabled, but ONLY if there is
some other method of unlocking the device enabled. This includes:
Trackball unlock, menu key unlock, and gesture unlock.
- Changed default gesture sensitivity to 3
Allow the user to specify which application to launch using
the lockscreen messaging slider.
Link:
http://www.multiupload.com/P00AYOA42T
Thanks to the devs of CyanogenMod and all other people contributing in this!
{
"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"
}
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
awesome idea for a thread!
daedelus82 said:
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
Click to expand...
Click to collapse
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
simms22 said:
awesome idea for a thread!
Click to expand...
Click to collapse
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
g4rb4g3 said:
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
ive been flashing quite a few custom cm builds lately and been finding it very refreshing
btw... it looks like you picked up that stupid lockscreen grass wallpaper bug
g4rb4g3 said:
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
Well, if support is your sticking point, then even using the cyanogen nightly is something you should avoid. This is just a user posting his creation if someone wants to play with the ROM. Happens all the time here. That's why this is a great site. Pick your poison. All about choice. Ignore what you don't want to use. I don't think the OP tried to pass this off as better than anything else. Just offering something to play with. I thought it was communicated very clearly.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
some people, obviously not you, experience the joy of flashing a rom for the sheer pleasure of flashing a rom. you dont have to flash it, or even read the thread(thats an absolute right that you have). but, i do see the worth in it. if not for anything else, the op is learning about building roms and has other people, like me, to test them out. i believe that it brings the op joy in building them and sharing. since its his own personal build, he can not post them in the official nightly thread. i was posting custom cm nightlies in the official thread and was asked to make a separate thread, and never did. btw, there are nights that there are no nightlies, so does the name of that thread have to change also? anyways, if you do have a good idea for the name of the thread, let the op know. maybe he will change it
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
A lot of people are asking about the lockscreen options in the Nightly thread. This should shut them up for now.
There's also no real need to support this at all. It's based on a nightly that is oudated in a few hours and it only has a couple patches. If anything is wrong he's not the developer of this ROM so there isn't anything for him to fix. It's just CM 6.1 built from source with new commits that aren't yet merged.
Just a taste of whats ahead.
P.S. <3g4rb4g3 <3simms22
Thanks to the OP for posting this. I like all the other flashing addicts find it refreshing trying out others peoples builds. Plus I have serious respect for the time, energy and hard drive space that goes into making these. Nice job.
Great job, I love the lock screen!, works perfect.
Last time I checked, Cyanogen nightlys were not supported either! just saying!
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
I don't care if you think it's worth flashing or not. I make my own "nightly" builds for several weeks already. Since some people asked I started this. Seems like there are people out there willing to try it. If you want to wait do so and keep it for yourself.
It seems you have a bad life, complaining about things that you don't like/think they are not worth trying... Try to read only topics that you are interested in. If you aren't interessted in this shut up, stop posting, go away and hate someone else.
I don't want to call it the best thing ever or anything else. This is just a feature preview. Maybe the features make it into a official build, maybe not. I don't decide that. But I decide which commits I want to use...
And about the "nightly" tag, I use it since I use the same sources for it. It should tell the people that this is nothing that got tested several days and it could contain bugs. (Like the stupid gras wallpaper on the lockscreen)
i think its a great idea, there is no need to bash someone for posting a modified nightly, this is a common thing in the open-source community
also there are many things you can merge and play with.
i for one merge some webkit stuff (from official webkit repo) when i get the chance , you should look into that.
- 2 pages of spam only
- great idea "g4rb4g3" keep it up!
New version, updated first post.
g4rb4g3 said:
+ White energy widget icons if you select the STOCK_Black theme in Settings>CyanogenMod settings>User interface>Tweaks extras>Select a theme.
This patch was made by me, I commited it and hope it will get merged.
Click to expand...
Click to collapse
That's awesome! If I hadn't gotten swept up in the whole MIUI craze, I would give it a go
updated first post
Great work, but i think that is better waiting for RC2 official release for mod it.
matiu said:
Great work, but i think that is better waiting for RC2 official release for mod it.
Click to expand...
Click to collapse
Of course you can wait, I couldn't
Cyanogenmod 9 Codename: Nebula for the YP-G1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hey guys here's what you have been waiting for. The unofficial official release of CM9 for the Samsung Galaxy Player/S Wifi 4.0 (a.k.a YP-G1). The TeamSupernova is proud to be the first of porting it.(with some exterior help) It is built on the latest commits from the stable CM9 4.0.4 source tree. This rom isn't different from any other stock CM9 but it's more streamlined and it's more official to release it like this.
Here's the context of how we have made it possible (thanks Hanthesolo for this story):
Firstly, excuse my cheesy biblical writing, I just have always wanted to write something in that format .
In the beginning (march 2012), there was hanthesolo. He saw the Galaxy Player forums, and all that he saw was good. This man started creating new work for the Gplayer forums, a and gained a small following. There was just one issue that concerned him: NO ICS!
In light of this, this man created a thread, to collect all ICS development, into one easy-to-read forum. Other began to follow him, zaclimon, Ijimaniac, and several others. Ideas flew fast and furious, but hope was waning quickly. A kernel would have to be created from scratch, a monumental task that had not been undertaken by any man so far.
All was quiet for awhile, and people began to slowly fade out, until only hanthesolo and zaclimon remained, slowly trading ideas and guesses over several weeks. Then a new disciple arrived: neyodmium. This korean (?) developer brought a different kind of kernel experience to the trio, and development began in earnest, with zaclimon and neyodmium trading work, while hanthesolo contributed where he could. One unsurmountable issue arose: this magnificient kernel, the likes of which had never lit up these forums before, would merely boot into recovery, not into Android.
Then Oisis came around, hearing our desperate cries for help. Like a moses, he guided his flock in the right direction, squashing issue after issue, until a monumental day arrived: August 13, 2012. On this day, ICS was finally created in Cyanogen's own image, and it was good.
Then increased development began, with hanthesolo squashing CM9 bugs, while zaclimon, neyodmium, and Oisis working feverishly on the kernel.
But an issue occurred, a wrench in the works. Thine enemy's name is GL, SuperNOva. GL would not cooperate, acting as a barrier between usable ICS, and frustrated efforts to fix it. But one day, the magical variable was flipped, and the builds booted! About this time there was a github mishap involving a bad I9000 push that stopped things for about a week, but that's another story.
What happens next? I dunno, but I will update this story when it happens .
NOTE: This does NOT represent anyone's political or religious standpoint, or the way anyone is viewed. It was created as a humorous way to explain our situation to users.
Click to expand...
Click to collapse
What's working:
Boot
Wifi
GPS
ADB
Accelerometer
Sound (voodoo module is included inside the kernel)
H/W acceleration (75/80% complete, video acceleration missing)
Deep sleep (MUCH better battery life than older ICS builds)
Native USB mount storage
FM Radio (download the spirit fm radio app from the store)
OC up to 1.2 gHz.
You tell me
What's not working:
Bluetooth
Camera (rendering is pretty crappy)
Recovery (well it does work but it can't reboot correctly to the system)
US home button (I do have a workaround for the moment)
Built-in CPU tuner (for OC/UC)
You tell me
Changelog:
Code:
Beta 1:
Initial release
Instructions
Note: Please backup your efs in case of something goes wrong (the zip should backup it but we're never too sure) To do so execute this command:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
You will need heimdall for this, if you don't know how to use it here's a guide on how-to:
DISCLAIMER: if you don't know how to use heimdall to reflash to stock (if needed) then you shouldn't flash this rom.
http://forum.xda-developers.com/showthread.php?t=1922461
1. Unzip the package which contains the zip and the boot.img.
2. Put the rom zip into the root of the sdcard.
3. Flash the rom using CWM. If you don't have it, please flash a custom kernel .(I recommend terrasilent)
4. When you're in CWM6, reflash the rom again.
5. After the second flash, flash the gapps zip. (if you have it)
6. Wipe your data.
7. Reboot into download mode and flash a GB kernel. (preferably the one you had before)
8. Reboot again into download mode after getting into CWM5.
9. Flash the boot.img included in the package by using heimdall at the KERNEL partition.
10. It should reboot and you will have your bit of Icy sandwich!!
NB: If you want the soft keys, (regardless of the reasons, RECOMMENDED FOR US PLAYERS, download the zip for the keys and flash it over CWM)
Here's the instructions in a more concrete way (Thanks Daniel644 for the video)
For those having problems with the encryption thing, here's the fix (Thanks Goldflame09)
For those if you who install and get the encryption error, follow these steps and it will work.
1) Hit reset tablet on the error page.
2) Go into recovery
3) Wipe data/factory reset.
4) Reboot system now.
5) As soon as the screen shuts off, go into download.
6) Flash terra silent kernel.
7) Let it boot into recovery and ignore all the errors.
8) Go to advanced and reboot download.
9) Flash the boot.img again.
10) Should be all set as long as you don't go into recovery.
Click to expand...
Click to collapse
Sources
Because we need to comply with the licenses and if you want to use our sources for something else here they are:
Device tree: https://github.com/TeamSupernovaSGP/android_device_samsung_ypg1
Kernel source: https://github.com/TeamSupernovaSGP/android_kernel_samsung_ypg1
Signature banners
Here's a banner made by LuthicaBlue (Big thanks to him!! )
{
"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"
}
Thanks
Samsung
Google
TeamHacksung
Pawitp (without him, ICS wouldn't have been what it is now big props to him!!)
Jt1134
Cyanogenmod
Supermaster34
Tdmcode
Downloads
B1
Gapps
Gapps Download
Software Key Mod
Soft Key Download (On-Screen buttons)
Screenshots
reserved, just in case .
reserved (watever that means)
but can i be a tester?
the playa! said:
reserved (watever that means)
but can i be a tester?
Click to expand...
Click to collapse
reserved means that I reserved the post in case I have more to put into the thread (han made it too so idk why you put reserved too )
Also there's already the beta 1 of ICS for the 4.0 here:
http://forum.xda-developers.com/showthread.php?t=1712668&page=113
zaclimon said:
reserved means that I reserved the post in case I have more to put into the thread (han made it too so idk why you put reserved too )
Also there's already the beta 1 of ICS for the 4.0 here:
http://forum.xda-developers.com/showthread.php?t=1712668&page=113
Click to expand...
Click to collapse
i didnt know that...
So, is this going to be apart of supernova, or your own separate project?
Can't wait.
iJimaniac said:
So, is this going to be apart of supernova, or your own separate project?
Can't wait.
Click to expand...
Click to collapse
You'll see.
zaclimon said:
You'll see.
Click to expand...
Click to collapse
in how long?
the playa! said:
in how long?
Click to expand...
Click to collapse
No ETA's
Seriously, I think there are way to many s flying around
iJimaniac said:
No ETA's
Seriously, I think there are way to many s flying around
Click to expand...
Click to collapse
yeah, ikr?
thats sad though.. no ETA's.. watever then.
Yes, no ETA's. Me, zaclimon and Oisis are all balacing ery busy schedules to get this to you guys as fast as possible. Me and zac stay up until almost midnight many nights testing and developing, and Oisis has to be up a 2-3 in the morning JUST to be able to talk to us, not to mention having to balance a VERY busy school schedule, our individual social lives, etc.
So please stop asking us for ETA's, or if this will be fixed by X, or that by Y, because we're developing this for the benefit of the community. We're not getting paid, or gaining any tax breaks, we're just a couple of guys who have decided to unlock the complete potential of this device, and if I do say so myself, I think we're doing a pretty dang good job on it, all things considered.
My rant is done, but guys, please understand what we're going through to be able to get this to you.
hanthesolo said:
Yes, no ETA's. Me, zaclimon and Oisis are all balacing ery busy schedules to get this to you guys as fast as possible. Me and zac stay up until almost midnight many nights testing and developing, and Oisis has to be up a 2-3 in the morning JUST to be able to talk to us, not to mention having to balance a VERY busy school schedule, our individual social lives, etc.
So please stop asking us for ETA's, or if this will be fixed by X, or that by Y, because we're developing this for the benefit of the community. We're not getting paid, or gaining any tax breaks, we're just a couple of guys who have decided to unlock the complete potential of this device, and if I do say so myself, I think we're doing a pretty dang good job on it, all things considered.
My rant is done, but guys, please understand what we're going through to be able to get this to you.
Click to expand...
Click to collapse
i understand. sorry about all my fuss that i created.
please forgive me.
the playa! said:
i understand. sorry about all my fuss that i created.
please forgive me.
Click to expand...
Click to collapse
No problem, it's not directly directed at you, it's just directed at the entire community. It's an unfortunate fact that most people these days forget how much time devs spend working on this stuff for them, which is understandable, since we don't share the development process with you guys. Just keep in mind that it's normally a lot more time-consuming to accomplish a task then we let on.
hanthesolo said:
Yes, no ETA's. Me, zaclimon and Oisis are all balacing ery busy schedules to get this to you guys as fast as possible. Me and zac stay up until almost midnight many nights testing and developing, and Oisis has to be up a 2-3 in the morning JUST to be able to talk to us, not to mention having to balance a VERY busy school schedule, our individual social lives, etc.
So please stop asking us for ETA's, or if this will be fixed by X, or that by Y, because we're developing this for the benefit of the community. We're not getting paid, or gaining any tax breaks, we're just a couple of guys who have decided to unlock the complete potential of this device, and if I do say so myself, I think we're doing a pretty dang good job on it, all things considered.
My rant is done, but guys, please understand what we're going through to be able to get this to you.
Click to expand...
Click to collapse
hanthesolo said:
No problem, it's not directly directed at you, it's just directed at the entire community. It's an unfortunate fact that most people these days forget how much time devs spend working on this stuff for them, which is understandable, since we don't share the development process with you guys. Just keep in mind that it's normally a lot more time-consuming to accomplish a task then we let on.
Click to expand...
Click to collapse
Rectum dictis! :good:
(Sounds dirty, right? It's actually Latin for, "Well said!")
Just thought I'd brighten the mood with some humor.
well this time, i think asking ETA is less reproachable. The team or zaclimon individually already posted the new thread about the coming ROM.
It's like advertising Avengers 2 is coming out but not telling people when it will be available.
it's natural for people to question when is it actually going to come out.
I think it's different from the typical ETA inquiry that i usually encounter.
stylemate said:
well this time, i think asking ETA is less reproachable. The team or zaclimon individually already posted the new thread about the coming ROM.
It's like advertising Avengers 2 is coming out but not telling people when it will be available.
it's natural for people to question when is it actually going to come out.
I think it's different from the typical ETA inquiry that i usually encounter.
Click to expand...
Click to collapse
No, sir, I do believe ANY ETA inquiry is against the forum rules.
XDA does not operate like the movie industry, nor like any commercial industry for that matter.
Outside of XDA, teasers and release announcements lead to inquiries, which may or may not be answered. Within XDA, teasers, promotions, and/or announcements are for the sole purpose of notification only. When the project is ready, it is ready. No questions asked.
Higgs_Boson said:
No, sir, I do believe ANY ETA inquiry is against the forum rules.
XDA does not operate like the movie industry, nor like any commercial industry for that matter.
Outside of XDA, teasers and release announcements lead to inquiries, which may or may not be answered. Within XDA, teasers, promotions, and/or announcements are for the sole purpose of notification only. When the project is ready, it is ready. No questions asked.
Click to expand...
Click to collapse
As I think more, I'm not sure if the question"(coming soon) in how long"? can be even considered as ETA inquiry. (connotatively)
There was no mention of WIP nor that the work is not complete yet.
In CM9's Camera's case, I'm also opposed to ETA inquiries.
People know that the work is in progress and the time required is indefinite.
But in this case, there was no hint that the work was unfinished nor about the uncertainty of completion.
zaclimon said that it's coming soon.
In Supermaster's thread about Camera WIP, none says "coming soon"
I think the term "coming soon" should be used more carefully because it means that the producer is somewhat ready and definite that the work is going to be finished and released on the specific time.
and i don't think that asking when the producer would wish to release is the "ETA inquiry" that people get attentive of.
I'm not trying to provoke any fight in this forum, I don't want to flame anyone and cause trouble.
I admire you guys' work because I'm a complete noob.
Of course i've never been developer and never felt how it would be to be asked of ETA.
But I just want people to ease up the tension in this forum.
Peace.
My apologies if my words appeared as flaming. Never were my intentions to flame you, I only wanted to point out that XDA is a not-for-profit forum/project, and all of the work that the developers do here is on a goodwill basis.
Those who ask for ETA's do not realize how much work it takes for a GOODWILL developer to manage life, work/school, and development on their own dime and time.
It's like a homeless person coming into your house, just after you've worked a full day and managed family and other obligations. You've just started cooking dinner, but you're all ready stressed and tired from a full day when the homeless person asks, "Hey, bud! When's dinner going to be ready? I'm hungry! C'mon Hurry up!"
Just sayin'.
About Carbon
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. and on our Gerrit CarbonDev Gerrit.
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, PA, 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
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All official Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
For mondrianwifi downloads:
CARBON-KK-UNOFFICIAL-20140429-0035-mondrianwifi.zip
CARBON-KK-UNOFFICIAL-20140612-2345-mondrianwifi.zip
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Reserved
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Thanks for developing for this device, will flash when I get a chance.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Does this ROM remove multi-window?
KrazyAttack said:
Does this ROM remove multi-window?
Click to expand...
Click to collapse
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Thanks so much for the time and work you put into this. I love seeing more roms for this great device!
Sent from my SM-T320 using Tapatalk
arrrghhh said:
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Click to expand...
Click to collapse
Yeah I assumed it did, I wish I could run a nice feature rich rom but I use multi window probably 80% of my time on this tablet. I almost always have YouTube on one half and chrome the other like right now haha. Wish there was a way to keep it or an alternative but thanks anyways.
Luckily my nexus 5 feeds my rom itch nicely. For now I'll just stay with CleanROM.
arrrghhh said:
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Click to expand...
Click to collapse
Dear @arrrghhh I am not a developer, but I have a little guess as to what might be causing the FC's on the google keyboard. The keyboard learns the user style and way of writing (if you see the T it has many settings that are probably intefering with the absence on Knox.
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
JaylanPHNX said:
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
Click to expand...
Click to collapse
CarbonFibers has a FC issue which has been resolved... but some of the customizations are still lacking because the CF app isn't really setup for tablets at the moment... so the experience is a bit off. I didn't see the value in updating until the issue is completely fixed, as most of the reason to run the ROM is in that area .
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
JaylanPHNX said:
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
Click to expand...
Click to collapse
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Cool. Thanks for the heads up.
From my Pro Tab 8.4
arrrghhh said:
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Click to expand...
Click to collapse
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
crpalmer said:
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
Click to expand...
Click to collapse
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
arrrghhh said:
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
Click to expand...
Click to collapse
I wonder if SlimKat will have better luck, since it doesn't centralize all of its features into one thing like Carbon Fibers. I think they just added the 2014 Note 10.1 as officially supported. I have no idea if there's any similarities between that and our Tab Pro or if that would help even if there were.
From my Pro Tab 8.4
Who wants to try out multiwindow?
{
"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"
}
It's definitely a bit quirky - and the issue with CarbonFibers is still present... but Bluetooth works great, so my builds of Slim must be missing something else outside of the device tree...
Great Rom
Just flashed new build. Works great so far. Thanks for the work.
So is this ROM finished now where there are no more updates going to be done?
{
"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"
}
About Us:
Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
It has been an awesome learning experience and is still not over! We are still learning every day and continue to move forward. Lastly, we DO NOT accept, nor ask, for donations. We don't believe in that. Everything that is necessary to keep this project going is out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc. We will never ask for a dime. All we do ask, is that you have patience, search, read and try to enjoy the process with us!!
Kernel Source:
https://github.com/CyanogenMod/android_kernel_lge_g3
Flashing Instructions:
- Verify that you're using the latest version of TWRP
- Perform a FULL WIPE as described below if coming from another ROM or a different version of Android
(A full wipe is when you wipe system/data/cache)
- Flash the latest version of this ROM
- Flash recommended GAPPS linked below
- Reboot and ENJOY!!
**If you fail to follow these instructions, please don't bother reporting any bugs**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
Change Log:
Code:
[B]Version 10.5 [/B]
[I][U]07 Aug 2016[/U][/I]
- Synced with DU source
- Version bumped to 10.5
- For a detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]DU gerrit[/URL]
[B]Version 10.4 [/B]
[I][U]14 July 2016[/U][/I]
- First build
- For a detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]DU gerrit[/URL]
Credit and Thanks:
We would like to give thanks to everyone that contributes to the Android community, big or small because every bit counts. Although we can't list each and every contributor within the Android community, we would like to highlight some of the teams and individuals that have made it possible NOT only with just this version of DU but throughout the years because we don't ever want to forget where we came from nor those that have helped us!
Special thanks to:
@ishanbhatnagr96 for testing the ROM :good:
That said, on behalf of the DU team we say THANKS to....
JMZ Software
Baby Jesus
Code Aurora Forum
Omni ROM
Android Open Kang Project (AOKP)
Android Ice Cold Project (AICP)
XDA-Developers
SlimROMs
Preludedrew
Max Weninger
Team Black Out
CyanogenMod
Pure Nexus Project
**If we have left someone or some team out, we apologize and please PM us**
Download Links:
Version 10.5 - https://www.androidfilehost.com/?fid=24591000424952756
GAPPS - http://download.dirtyunicorns.com/files/gapps/
Frequently asked questions:
The download link is slow, can you provide a mirror?
From time to time, we perform maintenance on our website but we do not authorize any mirrors. Please have patience!
I'm on a TEST BUILD and have this bug, can you help?
Please keep any discussion about test builds in the G+ community!
How can I get Viper4Android working?
Check this thread out https://plus.google.com/+JasonPasch5/posts/6JDRjdL2mKM
Are you coming from a ROM with Layers?
Make sure you remove your 'overlay' folders and perform a FULL WIPE
My battery stats are all messed and reporting the wrong percentage, what can I do?
Stop using another kernel. Do a FULL WIPE and flash the ROM again
Is this ROM CM based or AOSP based?
This ROM is based off AOSP
Does this ROM have layers or the CMTE?
This ROM uses the CM theme engine
Pulse doesn't work with [insert music app]
Check this thread out https://plus.google.com/101146731143183859725/posts/TcSzc61xuVx
I'm getting a FC from the theme chooser, what gives?
This is due to restoring data/apps from Google. Go ahead and clear data and cache for theme chooser and theme provider then reboot you should be good moving forward.
I changed my LCD density and now the navbar looks weird, what gives?
This is currenly an issue that we are aware of and addressing. For now after you changed density reset navbar layout or stay on the stock density.
Other Links:
G+ community - https://plus.google.com/u/0/communities/109738128866939227235
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
Jira (Bug Report / Feature Request) - http://jira.dirtyunicorns.com/
XDA:DevDB Information
[ROM][6.0.1][Unofficial] Dirty Unicorns for LG G3 [F400], ROM for the LG G3
Contributors
nitin.chobhe
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Testing
Created 2016-07-15
Last Updated 2016-08-09
Thanks @ishanbhatnagr96 for the Screenshots
One more if needed
Good stuff man! Loving the smoothness of DU ?
Sent from my LG-F400 using Tapatalk
@nitin.chobhe, can you tell me if laser AF is working?
Thanks, I hate any stock firmware and I may consider to switch.
Then... regarding modem, the 21C needing still exists?
Simone98RC said:
@nitin.chobhe, can you tell me if laser AF is working?
Thanks, I hate any stock firmware and I may consider to switch.
Then... regarding modem, the 21C needing still exists?
Click to expand...
Click to collapse
Laser autofocus does work fine. And this is a F400 thread. Please ask that question in the appropriate thread
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Laser autofocus does work fine. And this is a F400 thread. Please ask that question in the appropriate thread
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
Ah ok... sorry and thanks for the reply
Switching from Fulmics 5.3
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
ronmarccharlesms said:
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
Click to expand...
Click to collapse
Are you rooted? If yes, then you can get the Titanium Backup and backup all the apps that you want, flash DU and restore the apps :good:
@ishanbhatnagr96 can you help him about camera?
Nitin
ronmarccharlesms said:
I have been a fan of AOSP and CM-based ROM since I started fiddling Android devices. But for the first time, I used stock rom in LG G3 due to the fact that the camera performs better (according to my readings) than AOSP-based rom, mainly shooting 4K videos, time-lapse and slow-mo. But I hate the fact that the battery drains fast, overheating issues, and it lags a lot, as in a lot. I have to restart a couple of times to get my phone to work on some time.
I used Dirty Unicorn on my previous Android device (HTC One M7), and I was happy with its performance. So I'm considering this ROM, but I use my phone as a daily driver, so reinstalling apps is a bit hassle, especially coming from stock ROM. And I use camera a lot, so is there any alternative to this?
Thank you for those who will answer
Click to expand...
Click to collapse
Well the camera which comes with this ROM is snapdragon camera which is by far the best I've used on any AOSP/CM rom. I'd also suggest Google camera.
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Well the camera which comes with this ROM is snapdragon camera which is by far the best I've used on any AOSP/CM rom. I'd also suggest Google camera.
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
does it support 4k shooting? what is the average screen on time, if you mind? mine last only for about 2 hrs, with just browsing and music (with v4a).
ronmarccharlesms said:
does it support 4k shooting? what is the average screen on time, if you mind? mine last only for about 2 hrs, with just browsing and music (with v4a).
Click to expand...
Click to collapse
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Sent from my LG-F400 using Tapatalk
nitin.chobhe said:
Are you rooted? If yes, then you can get the Titanium Backup and backup all the apps that you want, flash DU and restore the apps :good:
@ishanbhatnagr96 can you help him about camera?
Nitin
Click to expand...
Click to collapse
yes i am rooted . uhmm, wouldn't that leave any traces of "stock" setting? I've read somewhere that one of the reason wiping cache is important is to remove all traces of previous rom, including the apps affected by it..or is it wrong?
and how about the SOT? does it last for 3h or more?and what kernel os recommended with this ROM?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
ooh. that is sweet thank you for that info. any kernel recommendation?
PS, I know that i shouldn't ask, as per stated on the post regarding DU, but is greenifying with xposed ok? have you tried it?
ronmarccharlesms said:
yes i am rooted . uhmm, wouldn't that leave any traces of "stock" setting? I've read somewhere that one of the reason wiping cache is important is to remove all traces of previous rom, including the apps affected by it..or is it wrong?
and how about the SOT? does it last for 3h or more?and what kernel os recommended with this ROM?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
ooh. that is sweet thank you for that info. any kernel recommendation?
PS, I know that i shouldn't ask, as per stated on the post regarding DU, but is greenifying with xposed ok? have you tried it?
Click to expand...
Click to collapse
I don't use xposed on CM/AOSP roms. Causes system to misbehave sometimes. But feel free to use it. And no, I don't use greenify. As per kernel, leave it to default and see how it performs
Sent from my LG-F400 using Tapatalk
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Sent from my LG-F400 using Tapatalk
Click to expand...
Click to collapse
yes thank you, but i am well aware of it eitherway, i think ill try it.
ishanbhatnagr96 said:
Yes 4K is there. As for battery, I average off anywhere between 3.5 to 4.5 hours.
TBH you just have to try it for yourself. If it suits your preference then good, otherwise look for something else. Usage and battery life depends on user to user. This is the only CM based rom which gives me good battery life along with temasek. So you should try everything as it'll give you a better insight
Click to expand...
Click to collapse
This is not cm based, it's based on aosp
Thanks for the answers man
Nitin
The best...
Glad to see new rom for f400.. So far so good thanks for this rom. Its rare to see new rom for korean variant. Keep up the good work dude!!!!
Thanks for the rom...
New build is up: https://www.androidfilehost.com/?fid=24591000424952756
Changelog:
- Synced with DU source
- For a detailed change log, check DU gerrit
Nitin
First of all I would like to thank the OP for his efforts.
Can you please continue porting DU to our f400 variants?. I can help you with testing if you need it
{
"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"
}
PixelExperience for Note 4
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
SE Linux Permissive
DON'T FLASH GAPPS, ALREADY INCLUDED
Download here
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
Android OS version: 9.0.0_r35
Security patch level: April 2019
Build author: Inkypen
Source code: https://github.com/PixelExperience
Device tree and kernel: https://github.com/triplr-dev
ROM Developer: jhenrique09
XDA:DevDB Information
Pixel Experience, ROM for the Samsung Galaxy Note 4
Contributors
Inkypen, tripLr, ripee
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-04-29
Last Updated 2019-04-29
File host changed to AFH, download link updated. Should be no more download errors
https://www.androidfilehost.com/?w=files&flid=293509
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
73sydney said:
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
Click to expand...
Click to collapse
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Click to expand...
Click to collapse
Inkypen said:
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
Click to expand...
Click to collapse
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
For clarity, heres my exact comments from the duplicate thread, please note that thread also included bug reports which i didnt repeat as they had already been expressed:
Tested this ROM, and heres my thoughts/criticisms:
* Inclusion of some G-Apps, while others which are more critical (Gmail most notably) are missing....for the huge download this oversight is really hard to fathom. 748Mb and no Gmail included? Also missing Android Webview.....kind of important
Instead all the stuff i normally weed out by never selecting it in Aroma G-Apps or usign the debloat magisk module if its built into a ROM is included...Device Health/Digital Wellbeing, and the google search app among them...if i wanted active spyware, id install it....instant downvote
For such a massive download, i cant see anything that would make me bother downloading further builds.
I do appreciate the dev building the ROM but, please consider leaving G-Apps up to the user, and thereby reduce the massive download size....
Update: curiously, some of my magisk modules which work on literally every other ROM ive ever used, fail on this one.....bizarre
About to test the dev's other ROM.....
Update: decided not to, apparently it has some of the same issues. Hope the dev can fix them and test before releasing next time....both ROMS cost me nearly 1.2Gb and both buggy....please test thoroughly before uploading.....
Back to RR for me again....
The best i had test at the moment, Stable, smooth, a Little bit of battery friendly, no overheating, no glitches, the only bug quiet anoying for me it's that I'm unable to activate the phone pressing the home botton, but the rest it's working nice as butter, sometimes the camera freeze taking a picture, thas a Little bit uncomfortable. nice job to all devs working on this rom.
73sydney said:
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
Click to expand...
Click to collapse
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Inkypen said:
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Click to expand...
Click to collapse
And again you insult me, among other things calling me "entitled"
You dont get to talk down to me...sorry, thats not happening, maybe when you release something without major issues you might get that privilege, but not before....
Last time, you will insult me and last time i want to hear your crap
Mate, ive flashed, contributed to, and tested more ROMs than youve had hot breakfasts
I wont be testing any more of yours given your attitude..
Especially when you totally discount the fact me asking you to actually test your releases before releasing them as in some countries like mine, bandwidth and data (especially for 700Mb+ ROMS) costs actual money. Your attitude on this, dismissing my data allowance out of hand (moaning about wasted bandwidth )is really quite insulting and rude. Its a valid criticism when its clear you havent properly tested your releases.
Good luck with your work, i wont be testing or recommending anything you release....
And quite frankly if i never come across you again, it will be too soon.....
Get over yourself, you rude self important newbie.
Congrats on being the 1st person ever on my ignore list, fool.
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Raven_999 said:
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Click to expand...
Click to collapse
That's done, and in AEX there's the even the option to toggle it on/off. Builds are running, will upload shortly.
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can I dirty flash this over the earlier version?
this is probably obvious but i cant find the settings for disabling hardware key lights and is there an on screen nav bar option?
note edge 915f is working hard only problem is the battery is not fully charged 92% 93 (lineage 16 also did not have this problem)
in this rom, camera works. (unlike other pie roms)
edge n915-t
sm-n910u
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Does the second sim working?
sm-n9100 trlteduos
mjhassanli said:
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably because your phone uses an exynos chipset and this forum is for snapdragon variants. Try this forum instead: https://forum.xda-developers.com/note-4/development
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Jack123hello said:
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Click to expand...
Click to collapse
Flash Magisk zip in twrp and then reboot your phone , this is how to root any rom