{
"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
Related
This thread is meant for discussion of the in progress Kit Kat port for the Nook Color.
Updates
If you want updates on the progress you can check this post and fattire's post immediately folllowing this. We'll both be posting updates periodically here.
You can also follow me on twitter @dalingrin
You can follow fattire @ fat__tire
Please don't ask me for ETAs or status updates. I will post them as I post them
Source code
Device source code will be temporarily hosted on fattire's github @ http://github.com/fat-tire/android_device_bn_encore
Things to expect
Nothing
Things not to expect(for now)
*Fully accelerated composition of the UI - this is not likely and may be dependent on 3rd party closed source EGL libs getting updated
*Accelerated video playback and overlay - This has changed quite a bit and may take some time to get working
*Polished release soon - Don't ask, don't tell
{
"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"
}
UPDATE 11/24/13 -- So CM 11.0 is out and building nicely on Nook Color. Look here for the link to the build instructions. If you are building CM 11, you will probably want to use cm-11.0 as the name of the branch when initializing.
STATE OF THE UM, STATE OF THINGS
So I was curious how many noob types, who always beg for nightlies and builds and stuff-- I wondered if they (you?) could be encouraged to learn and get involved in the process of building Android. Which, as I've expressed in an infamous ramble, I think is important to the future of our culture and how it it deals with technology-- and who will control it. So I asked normal non-dev people to try building-- to give it a shot.
I think the experiment, which quickly became OUR experiment, has been a massive success. Far beyond what I'd imagined. Hundreds of people have gotten off their asses-- many of whom had clearly never touched Linux or a compiler before, and most were successful in building CM9/ICS from scratch.
That is not a small deal. And no, it's not just following a list of instructions by rote. People had to think about and solve a million different problems-- installing VMs, updating packages, choosing linux distributions, understanding the command line, etc. Scary stuff if you've never done any of these things before.
So it's been a month or so now, and I think we've reached the stage where aside from minor enhancements and fixes, the build looks pretty sweet. The major stuff is there and working. Yeah, DSP/hardware-accelerated video is something we're going to have to wait for TI to add to their omap3 repositories, and there are likely other things wrong. I've heard rumors of sleep-of-deaths or quicker-than-usual battery consumption, etc. There are numerous things to be fixed, but these are all issues that may or may not be worked out over time... As major new enhancements come to the CyanogenMod project, they will come to the encore version, and your build, automatically.
No secret links this time. As before, I'll spell out the bottom line explicitly for ya here in the middle somewhere. And I'll even underline it.
I hereby decree, in so far I am able, my humble request for "no posted builds".... is ended.
Back to your regularly scheduled forum. Go to it.
I encourage you to pass any valuable improvements you make to the code "upstream" via the gerrit review system at review.cyanogenmod.com for inclusion in the main CM project. You already know how it works. And some, God love ya, have already started. Not everything you submit will get accepted, but it's a good way to "pay it forward". And in the same vein, consider helping someone on IRC. Or be a big brother or big sister. Or donate blood. And to quote Steven Soderbergh, or whomever, you don't have to brush ALL your teeth, just the ones you want to keep.
Thanks as always to dalingrin, keyodi, nemith, verygreen, arcee, deeper-blue, unforgiven512, the gang on irc, and the CM Team generally for keeping this fun. And thank YOU for the lulz, Internet.
ft
Remember, there's NOTHING quite like running your own build, piping-hot, and fresh from the oven.
----
I am also releasing a first pass at a how-to-build walkthrough. It is available here:
walkthru (rough draft)
This doc will be updated and evolve with your input. It is meant to help people feel confident that they can build an operating system from scratch, and hopefully encourage them to participate, learn, and even make contributions.
If you need assistance, you must rely on each other.
Here is an equally unreliable clockworkmod, v5.5.0.4:
uRecRam
You may be asking, where is the issue queue? There is no issue queue. You are on your own here.
Recent automated builds (unofficial, unsanctioned, untested, uneverything else) from Forum member Samiam303 is here.
-----------everything below this line is sorta old and outdated--------------
So there's apparently been some bit of controversy related to my request that people try to build themselves rather than someone posting a pre-made update.zip file. Let me go more into detail about what this experiment is about, at least from my perspective. But first, I do want to thank everyone for respecting the request so far-- I know it's not the traditional way of doing things, but I think it's been very fruitful and personally rewarding to see so many people who have never built jack before take on a project like this and be successful. I've received an enormous number of messages, both PMs here as well as in IRC, to the effect that this finally got them to try to build for the first time. It's introduced many people to actually using Linux, others may be having their first encounters with the command line, or git, or looking at source code, or learning about the build process in general. Whether or not the majority go on to become "devs" is irrelevant-- what I have been trying to encourage is curiosity and experimentation, and most of all a deeper understanding that your phones and "ereaders" are in fact full-fledged computers, not "appliances" or limited-purpose devices that others get to control. It's your property, and it can do a lot. There is an effort underway to discourage people from thinking of their devices this way or discouraging them from experimenting and learning with them. This IMO is an extremely harmful practice-- take a look at Cory Doctorow's recent speech on this subject. I could go on and on, but it seems important enough to me to make this request, and hopefully some of you are even subconsciously appreciating the awesomeness of what potential these general-purpose gadgets will have on society. So that's a lot of philosophizing, but there you go. And while I'm not naive enough to think that plenty of people aren't trading the file "under the table" at it were, for a variety of reasons, I do think that in a way they're cheating themselves; those who give building a shot are finding that learning is a reward unto itself. Those who are persistent, who pay attention, who don't give up, not only get a build at the end, plus the experience of doing it, plus the knowledge they picked up along the way-- they also discover things in the most unexpected of places, as in the link in the period at the end of the third sentence in this post. And while there's been some discussion of what a "dev" is and whether or not this is a gateway to bigger and better things, all I can assume is that if 5-10% of the people who built are intrigued enough to take it a step further, and maybe a step further than that... then we might end up with some new devs who appreciate the value of open source and whose contributions we can look forward to with eagerness in the future. Plus-- it's more fun this way.
I do hope this sounds good to everyone. If you understand what this post is about- no need for long, drawn-out elaborate responses... a simple "I got it" will do.
More source is forthcoming... Thanks to dalingrin, arcee, keyodi, nemith, Scepterr, unforgiven512, etc. Oh, and shh.
--------------------------
update-cm-9.0-0-encore-emmc-sneakpeek2-fullofbugs.zip
md5: 536d589c59ea5711a17a3d976f0638fa
update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip
md5: 85294ad91e2601beb737cf723b9fb9d6
(note this URL is likely to change)
Note: You are advised NOT to try to install this. This update.zip will **overwrite** as in erase whatever data you have on your emmc, so if you are trying this, you are advised to back it up first so you can recover. Install entirely at your own risk, and do a factory wipe first. This software is likely to be terrible and cause problems including permanent data loss, hair loss, and/or the destruction of your property and the death of your pets. You assume all risks involved in your use-- or even attempted use-- of this file. I disclaim any and all responsibility for your decision to try it.
*** Really. This build is buggy. It is a work-in-progress. It is only a snapshot of where things stand right now, and it's possible it'll never go further. ***
here's what's working:
* bluetooth (pairing/file transfer only confirmed)
* wifi (full it seems but it's brand-new to the kernel so who knows how stable anything is)
* backlight
* accelerometer
* improved stability (but not perfect)
* gapps
* setcpu/overclock
* real data usage info (not stubbed out)
* battery levels/charging
* physical menu button
* touchscreen
* 3d games
* usb gadget in kernel (ie, mounting your sdcard to your computer)
* screenshots
* build system (to auto-create update.zips)
* sound
(note: for all the above features, you must build yourself! See below for rationale & more)
For sure not working yet:
* video
* full 2d acceleration (esp on complex web pages)
* and much much more
These things may/may not be added at some point in the future. You should have no expectations that they will. Anyone who asks for an ETA for something or other gets collectively stoned by the crowd.
I'm sometimes on #nookcolor in freenode.
Thanks to keyodi, unforgiven512, arcee, toastfch, d0nk`, dalingrin, nemith, the rest of the cm team/TD, and anyone else who I've forgotten. We stand on the shoulders of giants.
MUST READ:
Why there have been no additional zips posted lately.
How to use Gerrit (the CM9 review system)
how to make an update.zip
[*]beagleboard patches
Again, don't install this. And please don't "rom" this (as in change the font or background) and then ask for donations for your "hard work". This is a preview of a work in progress, not a final product, and it's not meant for people to use day-to-day. Don't be a ****. Thanks.
--------------------screenshots---------------------
About screen, wifi scanning, & bluetooth....
I'm no dev so can't help.
But thanks a ton. You'll give a new life to the NC!
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
luigi90210 said:
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
Click to expand...
Click to collapse
Performance is hard to tell without any apps on it really and with the legacy hack being goofy. Dalingrin's going to fix the ts driver tomorrow he says. It needs to be updated for anything close to usability. I think though it's not too far off from cm7 but again *REALLY* hard to say without having something to run on it.
I did notice that if you put a background on the screen it only stays for like second before disappearing. No idea what that's all about.
Update:
So update on progress tonight
* misc fixes
* got wifi working for keyodi
* got glx working for keyodi
* fixed bluetooth pairing again. Ran into trouble trying to send a file connection refused (111) or something like that.
* got freecpu working, needed to chmod 4755 /system/xbin/su and also add Superuser.apk-- but now overclocked to Dalingrin's cm7 settings. It feels pretty good.
(that's actually set to highest stepping but it's not currently maxed out)
* quadrant runs-- looks fast to me-- but bombed out on the network part at the end:
E/c*.a*.q*.c*.c*.Abstrac*( 4126): Failed to retrieve benchmark score
E/c*.a*.q*.c*.c*.Abstrac*( 4126): java.net.SocketException: socket failed: EAFNOSUPPORT (Address family not supported by protocol)
So I don't have a score. Not that Quadrant is particularly valuable. but the staircase works, the planets spin, etc.
Prolly won't work on it most of tomorrow.. just sayin'. Dalingrin will tho hopefully and keyodi too.
BTW, dalingrin-- temporary fix for wifi: assuming you use WPA-PSK, push this into /data/misc/wifi/wpa_supplicant.conf as the default in the device needs to be fixed manana:
Code:
ctrl_interface=tiwlan0
update_config=1
network={
ssid="your_ssid"
psk="your_password_in_plaintext"
key_mgmt=WPA-PSK
priority=1
}
Finally, if recovery.c tanks out, it's the last commit I made tonight. Sorry. I didn't think it was going to build it. Just back out changes to that file.
Yay!
Ian
sent from my ereader
Fantastic work. Didn't thought quadrant would run fast this soon. If wifi, touchscreen and 3d work, we have the most important things working (save for ui acceleration). I don't even care much about sound.
Looking forward to the first kangs =)~
Sweet! Lookin' pretty good. I hope the binaries for the UI acceleration get updated. Has the nook tablet source and files dropped yet? I seem to remember the NC and nook tablet having similar video hardware. Could be wrong. Are those binaries in that tablet as well?
dalingrin said:
Things to expect
Nothing
Click to expand...
Click to collapse
Noted, but that said I love this kind of technical tinkering and knowing this is being done is awesome. Looks pretty slick, I look forward to seeing how this develops.
no test zip? I would like to test, Im not one of those people that wont reprt back, i will tell what i find wrong
just wondering, will this truetouch driver update (https://github.com/martinezjavier) be incorporated and will it improve the screen sensitivity, esp. around the edge, for the nook? thx.
i'm excited!!
thanks in advance for all the hard work!!
I've only just started noticing the lack of activity in this device's community, so while I would love to tinker around with ICS on my Nook I understand how it may not a very big priority for developers. Do what you guys can with the knowledge, technology, and time you have and maybe I'll get new software to play with, but maybe I won't. This device has already been made a far better device than B&N intended it to be anyway.
Thanks for all the current and future work you guys devoted to this device
Sent from my NookColor using Tapatalk
Whoareyou said:
no test zip? I would like to test, Im not one of those people that wont reprt back, i will tell what i find wrong
Click to expand...
Click to collapse
Finding whats wrong isn't a problem right now, which is exactly why they didnt release flashable zip file. They did however post a link to the source, which if you know how to compile that, you know how to get it running on your device and may actually be of some use to the devs in getting other things working.
gamer.pro.2000 said:
Sweet! Lookin' pretty good. I hope the binaries for the UI acceleration get updated. Has the nook tablet source and files dropped yet? I seem to remember the NC and nook tablet having similar video hardware. Could be wrong. Are those binaries in that tablet as well?
Click to expand...
Click to collapse
The nook tablet uses an OMAP4 es ("enhanced security") from Texas Instruments that has a signed bootloader, which is checked on boot at the hardware level. The signed bootloader (u-boot) in turn checks the signature of the kernel and the ramdisk. Which means, fwiw, that you can't easily replace the bootloader or kernel (or basic startup sequence in the ramdisk) without it being signed by Barnes & Noble.
That said, people have run stuff "around" the existing kernel/ramdisk as nemith has done with cwm. Or you can just run apps you want within userspace (ie, using their kernel/ramdisk) by rooting Android with Zergrush and then installing the market or sideloading or whatever as several threads on this site tell you how to do. There were also several articles on this recently.
Interestingly, the signed kernel does load unsigned kernel modules, meaning a specially-crafted module can theoretically be written to "kexec" (ie, run) a 2nd, unsigned kernel/ramdisk "from the inside" of the kernel. That "second boot" possibility would facilitate the running of alternate OSes, and there have been attempts to do this with the Motorola Milestone. And finally, if anyone finds an exploit in uboot (such as improper validation of input, say while it reads bootcnt or bcb files or something), this too might also be another way to get a "normal", unsigned kernel/ramdisk to run, and therefore ICS would be a lot easier and control would be restored to the owner of the hardware.
That said, a philosophical opposition to DRM has lead a lot of people I've talked to to just say "F the nook tablet" and not purchase one in the first place. Dunno.
unsivil_audio said:
Finding whats wrong isn't a problem right now, which is exactly why they didnt release flashable zip file. They did however post a link to the source, which if you know how to compile that, you know how to get it running on your device and may actually be of some use to the devs in getting other things working.
Click to expand...
Click to collapse
I know how to, but my new laptop (HP Pavilion G6) dosent like linux well, and i cant get wifi to connect, networks show up, but it never connects So, i cant d/l the source ((
Great work so far.
Umm... is there a donation address set up so I can send a touch of... encouragement? Stimulus? Call it what you want. Beer fund.
fattire said:
The nook tablet uses an OMAP4 es ("enhanced security") from Texas Instruments that has a signed bootloader, which is checked on boot at the hardware level. The signed bootloader (u-boot) in turn checks the signature of the kernel and the ramdisk. Which means, fwiw, that you can't easily replace the bootloader or kernel (or basic startup sequence in the ramdisk) without it being signed by Barnes & Noble.
That said, people have run stuff "around" the existing kernel/ramdisk as nemith has done with cwm. Or you can just run apps you want within userspace (ie, using their kernel/ramdisk) by rooting Android with Zergrush and then installing the market or sideloading or whatever as several threads on this site tell you how to do. There were also several articles on this recently.
Interestingly, the signed kernel does load unsigned kernel modules, meaning a specially-crafted module can theoretically be written to "kexec" (ie, run) a 2nd, unsigned kernel/ramdisk "from the inside" of the kernel. That "second boot" possibility would facilitate the running of alternate OSes, and there have been attempts to do this with the Motorola Milestone. And finally, if anyone finds an exploit in uboot (such as improper validation of input, say while it reads bootcnt or bcb files or something), this too might also be another way to get a "normal", unsigned kernel/ramdisk to run, and therefore ICS would be a lot easier and control would be restored to the owner of the hardware.
That said, a philosophical opposition to DRM has lead a lot of people I've talked to to just say "F the nook tablet" and not purchase one in the first place. Dunno.
Click to expand...
Click to collapse
there have been talks about kexec on the nook tablet but from last i read is that kexec was disabled in the kernel so they were looking into 2nd init
ON TOPIC: i would donate if there is a donate link set up
Speaking for myself, I ask that you consider donating to the Electronic Frontier Foundation -- Eff.org -- they help keep our right to hack/jailbreak/root our own hardware safe and legal when corporations or government (usually under heavy lobbying from corps) try to infringe on it. And to that end, they also take up the legal defense of folks who are threatened or sued unfairly, such as just a few days ago with the security blogger who posted a spyware/rootkit warning and was hit with an intimidating takedown legal threat by the company he outed. They also fight laws that would censor or wall off parts of the Internet.
Donations to the EFF are tax deductable for US residents as well. They are one of the few organizations concerned with defending the Internet and digital-related interests of normal citizens and consumers, and a donation to them is really doing yourself a big favor.
Plus I think they'll send you a hat.
/end of pitch.
fattire said:
Speaking for myself, I ask that you consider donating to the Electronic Frontier Foundation -- Eff.org -- they help keep our right to hack/jailbreak/root our own hardware safe and legal when corporations or government (usually under heavy lobbying from corps) try to infringe on it. And to that end, they also take up the legal defense of folks who are threatened or sued unfairly, such as just a few days ago with the security blogger who posted a spyware/rootkit warning and was hit with an intimidating takedown legal threat by the company he outed. They also fight laws that would censor or wall off parts of the Internet.
Donations to the EFF are tax deductable for US residents as well. They are one of the few organizations concerned with defending the Internet and digital-related interests of normal citizens and consumers, and a donation to them is really doing yourself a big favor.
Plus I think they'll send you a hat.
/end of pitch.
Click to expand...
Click to collapse
im gonna look more into that but ill probably donate to that foundation
thanks for the info and i wish you luck with ics fattire
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'.
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.
{
"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"
}
What is Omni?
Omni Gerrit Review
Disclaimer
Code:
#include
/*
* 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. Hard. A lot.
*/
DOWNLOADS:
omni-7.0-20161022-mako-HOMEMADE.zip
Because of the nature of Xposed framework, NO SUPPORT will be given to those running Xposed framework on Omni 6
CHANGELOG:
Code:
[CENTER]
2016-10-22:
-Video recording fixed on stock camera (snapdragon camera still have some issues there, jerky video)
-Omni features progressively backported
2016-10-4:
Initial Release[/CENTER]
You MUST DO A FULL WIPE, whether you are coming from homemade builds (aka my builds), or a previous version of OmniROM. Be certain to do a full backup of your data, apps, call logs, sms/text and so on before flashing.
GAPPS must be flashed BEFORE initial boot, they will NOT work properly if you flash them afterwards !!!
KNOWN BUGS:
Code:
[CENTER]- Camera recording only works with Google Camera
- Screen rotation isn't working
[/CENTER]
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
RECOMMENDED TWRP
Source
OmniROM Source
Only a few changes are taken from CyanogenMod, but thanks to them for those
CyanogenMod Source
XDA:DevDB Information
OmniROM 7, ROM for the Google Nexus 4
Contributors
kldoc, MaR-V-iN, Maxwen, Entropy512, Xplodwild, Jiangyi
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-04
Last Updated 2016-10-21
Wow.... already?
Thanks for the hard work! Any features?
ddaggebi said:
Wow.... already?
Thanks for the hard work! Any features?
Click to expand...
Click to collapse
More or less the same features than in Omni 6, everything is being backported.
Battery led and custom notification led will be there in next build.
We expect android 8
Why such a hurry !?
Before you refine the A-7 will have A-8.
Of course it was a joke, but journalists already predict the future:
Android 8 : ce que l'on attend
ze7zez said:
Why such a hurry !?
Before you refine the A-7 will have A-8.
Of course it was a joke, but journalists already predict the future:
Android 8 : ce que l'on attend
Click to expand...
Click to collapse
Mostly because I'm in vacations, and got the time this week to do the bringup for Nexus 4, then OmniROM got gerrit fixed so we could merge everything that needed to, from there, things go quite fast, team is actually quite efficient
I noticed a few kernel side commits i didn't merge yet, so tomorrow's build, you should expect a few things fixed, rotation should be fixed, and some omnigear stuff are coming back
Do you know if the future official omni 7 will require full wipe if coming from official omni 6???
Sent from my Nexus 4 using Tapatalk
mandgeo said:
Do you know if the future official omni 7 will require full wipe if coming from official omni 6???
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I think I stated it the header, yes, it will be needed to avoid any problem, Android 7 has a lot of changes.
New build delayed for tomorrow, have been hard at work trying to solve the camera video recording, failed. Rotation is fixed.
Video recording seems to be a recurring issue on Android 7 for older devices, and none of the ROM I checked managed to really fix it for good. From there, I'm not actually certain it will ever get fixed, and because of this, I don't know if Nexus 4 will reach nightlies or not. I will publish builds as OmniROM features get backported, but won't go any further than this.
Given Google's pricing for Pixel, I am soon buying a Oneplus 3, and will switch to it for OmniROM support.
I'm not giving up totally on Nexus 4, but dev won't be as up to date as it was when I did Marshmallow or Lollipop.
Hi all! I have been wondering if Snapdragon camera is included, cuz that's the only thing stopping me from switching to Omni 7 or CM 14?
Chefov01 said:
Hi all! I have been wondering if Snapdragon camera is included, cuz that's the only thing stopping me from switching to Omni 7 or CM 14?
Click to expand...
Click to collapse
Yes, Snapdragon Camera is included, it's actually replacing the stock AOSP camera, only video recording is broken on Nexus 4 atm, that's what I was mentioning earlier, no one has this properly working 100%, camera itself is able to take pictures, no issues there, but just video recording isn't possible atm.
I remember stepen wolf with cm 14 unofficial figuring on how ot fix it. but I am not sure if he has done so as of yet or not. but he di state it was on hhis list of things to do to fix the rom. so whwho knows between you and stepean with cm14 you guys can figure it eventually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:18 PM ----------
just read his post he still has the same issue with camera video recording having issues it will record in 720 p ok but with 1080p has issues. so he will be working on it. so hopefully between kldoc and stepan the issue will get resolved.thats the only issue with nexus 4 having had the AOSP 7 rom on my nexus 4 over 2 months now. kldoc I am also agreeing with you google made a big disservice to the developer by raising the price of the pixel for the development community. as soon as I have some fund I will be joining in support and getting a 1 plus 3 as well. the only thing will be to get older nexus device and keep them up to date and then going forward go with other vendor to prove to google that they are not the only premium product with a outrageous price that the development community cant afford and then will end up jumping ot other product lines to support going forward in the future . that's one thing that google has now gotten out of touch with its community. they are forgetting that the development community got them to the big Android dance. The developers developers . I respect what all you guys and gals do here on XDA for all of us!!!!
mrk2815 said:
I remember stepen wolf with cm 14 unofficial figuring on how ot fix it. but I am not sure if he has done so as of yet or not. but he di state it was on hhis list of things to do to fix the rom. so whwho knows between you and stepean with cm14 you guys can figure it eventually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:18 PM ----------
just read his post he still has the same issue with camera video recording having issues it will record in 720 p ok but with 1080p has issues. so he will be working on it. so hopefully between kldoc and stepan the issue will get resolved.thats the only issue with nexus 4 having had the AOSP 7 rom on my nexus 4 over 2 months now. kldoc I am also agreeing with you google made a big disservice to the developer by raising the price of the pixel for the development community. as soon as I have some fund I will be joining in support and getting a 1 plus 3 as well. the only thing will be to get older nexus device and keep them up to date and then going forward go with other vendor to prove to google that they are not the only premium product with a outrageous price that the development community cant afford and then will end up jumping ot other product lines to support going forward in the future . that's one thing that google has now gotten out of touch with its community. they are forgetting that the development community got them to the big Android dance. The developers developers . I respect what all you guys and gals do here on XDA for all of us!!!!
Click to expand...
Click to collapse
Feedback i have, is most devices actually have camera issues on Android 7, things will eventually smooth out and get polished
I still have a build to publish today, been working on that camera issue, but also working on cleaning up stuff to get that on OmniROM's gerrit and github.
I checked his work, but he's more or less at the same point everyone else is, sill no real solution atm.
Oh and by the way, my builds are also Selinux enforced
will be patiently waiting ot test the next build you have out for nexus 4.thanksfor maintaining and building android 7 for nexus 4.
Uploading the new build as we speak, Battery light are back, Custom notification lights are also back (didn't in Omni 6).
Rotation is fixed, battery display is back, and a lot of Omni features are back, doze mode isn't there yet, but should be soon.
EDIT: Link in the OP updated, enjoy
Have fun with OmniROM !
P.S.: I merged my commits on Omni repos for kernel and device trees
Awesome ROM, keep up the good work.
However, there are some issues I noticed;
1. Can't seem to change the SELinux mode to Permissive with SELinux mode changer.
2. Permission requests appear as in the screenshot with no way to take an action (can grant from settings though).
Btw, is SuperSU integrated into the ROM?
kanishkad said:
Awesome ROM, keep up the good work.
However, there are some issues I noticed;
1. Can't seem to change the SELinux mode to Permissive with SELinux mode changer.
2. Permission requests appear as in the screenshot with no way to take an action (can grant from settings though).
Btw, is SuperSU integrated into the ROM?
Click to expand...
Click to collapse
No you will not be able to change SELinux to Permissive rom within the system, if you want to run OmniROM permissive, you need to build it by yourself, OmniROM (not only me) is really strict about this. The initial build was permissive, but it was a proof of concept. Android N changes a lot of things, there might be bugs here and there, but SElinux is relatively working well now.
Permission granting, i will have to check things on that, but ROM is barely coming together, 80% of our maintained devices are barely uploading a semi working build, will ask your for a bit of patience
Supersu never was a part of OmniROM, and probably won't be anytime soon (if ever).
A screenshot without a logcat is more or less useless ...
kldoc said:
No you will not be able to change SELinux to Permissive rom within the system, if you want to run OmniROM permissive, you need to build it by yourself, OmniROM (not only me) is really strict about this. The initial build was permissive, but it was a proof of concept. Android N changes a lot of things, there might be bugs here and there, but SElinux is relatively working well now.
Permission granting, i will have to check things on that, but ROM is barely coming together, 80% of our maintained devices are barely uploading a semi working build, will ask your for a bit of patience
Supersu never was a part of OmniROM, and probably won't be anytime soon (if ever).
A screenshot without a logcat is more or less useless ...
Click to expand...
Click to collapse
Just to clarify if my post seemed like a complaint, this is awesome work and really glad that devs like you are keeping a 4 year old device alive Just wanted to point out the issues I faced in order to help you make it better..
I was able to set it to permissive by the command "setenforce 0". Need it to get Viper4Android working
I will post a logcat if I encounter any issues. Keep up the good work :good:
kanishkad said:
Just to clarify if my post seemed like a complaint, this is awesome work and really glad that devs like you are keeping a 4 year old device alive Just wanted to point out the issues I faced in order to help you make it better..
I was able to set it to permissive by the command "setenforce 0". Need it to get Viper4Android working
I will post a logcat if I encounter any issues. Keep up the good work :good:
Click to expand...
Click to collapse
Oh, I wasn't aware Viper4Android was still being maintained, external modifications aren't something we bring support to, mostly because it changes initial behavior and it's hard to predict what changes towards drivers support throughout system updates.
Someone in Omni pointed me at a modified video recording handling ( coming from slimrom actually), will give it a shot tomorrow.
I'm also planning to enable LTE support for those who need it in the future, even though I won't be able to test it (China's network don't handle those frequencies)
kldoc said:
Oh, I wasn't aware Viper4Android was still being maintained, external modifications aren't something we bring support to, mostly because it changes initial behavior and it's hard to predict what changes towards drivers support throughout system updates.
Someone in Omni pointed me at a modified video recording handling ( coming from slimrom actually), will give it a shot tomorrow.
I'm also planning to enable LTE support for those who need it in the future, even though I won't be able to test it (China's network don't handle those frequencies)
Click to expand...
Click to collapse
Your existing build actually already picked up LTE for me, with no modifications needed. Working just fine on my end
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
Your existing build actually already picked up LTE for me, with no modifications needed. Working just fine on my end
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Good to know, wasn't intended If it works well, glad that you're happy with it
So I really don't know what's going on and what's happening behind the stage.
Obviously alonsoj636 decided to discontinue and abandon his greatly admired LineageOS builds from the past months.
I haven't found any notes or statements as to why he finally has decided to do so and I was not able to reach him on xda because he blocked PMs. If you read this, maybe you want to be so kind and give us some hints what's happened!
Anyway...
we, as the RM10 LineageOS community, have to face reality and that means: currently there is no LineageOS rom build and maintained by anybody. That either means sticking with old versions, changing ROMs/GSI or switching the phone completely.
While alonsoj636's versions are still working very well, they eventually become outdated sometime.
This thread should be used to coordinate discussions about future LineageOS development (if there is enough interest and people).
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Alright, so the cat is out of the bag on this one:
While I'm really happy that Alonso kept maintaining the ROM for a while, the reality is that he wasn't interested to go official anytime soon and kept being vague about it.
As for me, I'm building up the courage to do MPK99 recommendation and go with GSI. Apparently GSI works like old ROMs, and it doesn't nuke TWRP, so that seems nice.
Try GSI. It's perfect.
MPK99 said:
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Click to expand...
Click to collapse
I'm pretty aware of that, however all new ROMs are tagged as development on this xda forum so I used this wording.
I think all 3 mentioned options are valid.
I could build it myself, however the time is the problem. Finding someone else building lineage in the future seems to be difficult. The past showed there aren't as many people interested and even less have the time and skill to build it.
GSI sounds like a wonder bag to me. while it's great to always have the latest updates, it might lack of the features LineageOS had for years. (i think of things like os-level online permission per app (wifi/cell), permission center, etc.). you can workaround that with 3rd party tools maybe, but it's cumbersome again.
Also GSi still sounds like a bit of an unpolished OS for this specific phone, with some kind of bugs and lack of features (compared to LOS). it's everybodys own decision to put priority on either that or on latest updates, though.
I might as well give it a try sometime, but I'll need enough spare time for experiments, so it won't happen soon.
my hopes are low, but maybe someone will step up and also build new LOS roms in the future.
Zirila said:
however all new ROMs are tagged as development on this xda forum
Click to expand...
Click to collapse
They're all namesake
Zirila said:
it might lack of the features LineageOS had for years
Click to expand...
Click to collapse
Lineage is lineage whether it's a gsi or a cusrom
Zirila said:
still sounds like a bit of an unpolished OS
Click to expand...
Click to collapse
Those are false claims. You need to use it before committing on it.
Zirila said:
I'll need enough spare time for experiments, so it won't happen soon
Click to expand...
Click to collapse
There's nothing to experiment, as user's experiments are logged on my thread. You can follow them. I'm myself a gsi user for an year long btw. As for the time, it'll take not more than 10 minutes. And I've laid out post configuration & fixes on the thread which'll be another 5 minutes.
well what I meaned with unpolished is what I've red in your thread about bugs like -don't touch screen while booting- etc. I haven't installed it so I solely say that by reading these posts.
and experimenting is synonymous with taking time to clean flash and reinstall everything again while learning and fixing problems with new OS/roms/GSIs.
I'll have a look sometime and I'm grateful there is progress.
Atleast I was transparent about the bugs on it.
Zirila said:
bugs like -don't touch screen while booting
Click to expand...
Click to collapse
Not touching the screen 'while booting' is an easy fix & you won't often reboot your device while work in the first place.
Zirila said:
learning and fixing problems with new OS/roms/GSIs
Click to expand...
Click to collapse
Just the procedure would be new. Rest of it would be your same old preferred AOSP derivative (lineage).
you did well. nothing to complain.
the more I dip into the topic the more I think it might be worth a try. don't count the time till I can focus on it, it'll take a while. but it sounds more and more promissing and the overall experience might as well get even better with time.
regardless of the GSI option, let's still have this thread and discussion opened for the case of some future LineageOS-CustomROM progress.
I'm very sorry for my abrupt decision to kill Lineage.
some personal and family problems made me think that I couldn't continue with this (nothing too big, don't worry... typical family fights)
after some messages I decided to get back to the action.
I will upload a new build with improvements once I unlock my bootloader (not very soon) as my RN10 is my only source of internet and I can't use the Mi Unlock Tool.
Thread will remain locked until the new build is done.
Thank you for your understanding and sorry for my bad steps ....
Regards
Thanks for the informational update
no worry, we are all human. as software engineer and project maintainer in troubled times it's often better to just keep calm, step back for a while, let the projects delay or freeze, that won't really hurt anyone. and then check back later to make a judgement if the project(s) really have to end.
It wasn't that bad for us either, in the meanwhile some of us learned a bit more of the GSI option which might also be a viable way to run LOS in the future. But everything has up- and downsides.
I'm glad we get to see a few more updates for the LOS custom rom.
lineage is alive again
new update is up ... waiting for shadowstep to open the thread again
Changelog
* Switch to SkiaGL Threaded
* Optimize package manager dexopt properties
* Kernel upstreamed to v4.14.295
* Kernel built with Clang 15.0.2
* Enable config_avoidGfxAccel
* wifi: Disable TDLS offchannel
* Disable few debug services
* Don't enable iostats
these are only for LineageOS 19.1
No changes for 18.1
Lineage OS for Mojito - Browse /Lineage at SourceForge.net
LineageOS for Redmi Note 10 (mojito/sunny)
sourceforge.net
Deleted.