Database Info

[ROM][AOSP] [Nightly/Release] CarbonRom JB [xt897/xt897c]

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.
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.
Screenshots
{
"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"
}
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 Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
http://goo.im/devs/carbon
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
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 goo.im page linked above. It's new, but expanding fast. Just like us!
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?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
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!
​

BUGS​
Some (not all) seem to experience issues with GPS. If you have issues with GPS, please RSD the JB image and then flash Carbon. GPS should work now. (I've also heard you can just restore a stock backup, get a lock, then flash Carbon again...)
Haptic feedback on soft keyboard is not provided when enabled (which it is by default)
While capturing a picture to send via MMS, ensure HDR is deselected - Gallery will cause a force close if HDR is enabled!! (Note - HDR works for normal still photos, just not MMS.)
Update Google Search (manual update), or else any voice searches will fail with FC. Update the app, and it is resolved.
Caps lock LED doesn't seem to work properly...
Camera button doesn't work? Cam/camcorder works fine, but the physical camera button does not seem to function (in Carbon).

Reserved

Also reserved

1st to try it out. Slide out keyboard light does not work.

Great! Now we as CDMA user have much ROM options to choose. Carbon seems a big hit nowadays along with Paranoid with its Halo features. Thanks a lot for the port.

gtownswagga said:
1st to try it out. Slide out keyboard light does not work.
Click to expand...
Click to collapse
Ah, I did not notice that. Should be easy to fix, it's probably a liblights issue... as I cannot adjust the brightness either
Edit - fixed the brightness issues, and added back the multipress options... but I am still missing the keyboard backlight! I will keep working at it, and keep this thread updated.
Edit 2 - welp, looks like there are some frameworks/base hacks required. I will upload the build I am running now, everything with liblights is fixed (brightness of the display, notification LED) are fixed but keyboard backlight is not. Working on fixing that now.

Figured I would post again - as liblights should be completely fixed now folks .
I probably need to test MMS again, I'm trying to think of what else I could have missed... let me know what you find broken guys! I'm also curious if this works on the GSM hacked variants, or if I have to run another build for that group.
Edit - just tested outbound MMS (which is all I can test), it seemed fine.

First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2

dwaynet89 said:
First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2
Click to expand...
Click to collapse
Now don't quote me on this, but isn't that kernel for 4.0.4?

dwaynet89 said:
First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2
Click to expand...
Click to collapse
dpwhitty11 said:
Now don't quote me on this, but isn't that kernel for 4.0.4?
Click to expand...
Click to collapse
Well, I have a few kernels. There's one I released for CM, and my kernels that have their own thread (which are for stock).
Unfortunately I will probably have to release a separate kernel for this, as any time the kernel modules change, wifi will be broken if you don't keep up with it (this is why your wifi is broken dwaynet89.)
I assume you were using the CM kernel? That would be the only one having a chance at working. I can whip up another one for this build too if needed

arrrghhh said:
Well, I have a few kernels. There's one I released for CM, and my kernels that have their own thread (which are for stock).
Unfortunately I will probably have to release a separate kernel for this, as any time the kernel modules change, wifi will be broken if you don't keep up with it (this is why your wifi is broken dwaynet89.)
I assume you were using the CM kernel? That would be the only one having a chance at working. I can whip up another one for this build too if needed
Click to expand...
Click to collapse
I'm sorry for not making that clear but yeah I was talking about the cm kernel. If you don't mind I would love one of your kernels for this rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2

Installed and running nicely. Can confirm also that face unlock through the normal system settings does not work and force closes. Might it be related to the camcorder video issues? Doesn't impact me a whole lot as one of my wifi network requires secure credentials and won't allow any security less than a pin. Will look for other bugs but looks really solid to begin with. Thanks for all your work!
Sent from my XT897

This ROM seems really cool and i like most of it so far. FYI starting from stock and letting GPS lock before installing the ROM works here too. No problems with GPS for me. One thing i am missing and maybe its just me but is there a menu for changing launcher settings in this one like there is in CM? I always remove the google search bar and increase the grid size. Short term fix for me was i backed up trebuchet with all of the settings like i like it in CM 10.1 and restored it in carbon. Thanks for the work on this and if you need help with testing stuff i'll be glad to help.

Mordannon said:
This ROM seems really cool and i like most of it so far. FYI starting from stock and letting GPS lock before installing the ROM works here too. No problems with GPS for me. One thing i am missing and maybe its just me but is there a menu for changing launcher settings in this one like there is in CM? I always remove the google search bar and increase the grid size. Short term fix for me was i backed up trebuchet with all of the settings like i like it in CM 10.1 and restored it in carbon. Thanks for the work on this and if you need help with testing stuff i'll be glad to help.
Click to expand...
Click to collapse
There's a TON of settings. Check the 'Carbon Rom' menu.

disconnecting wifi
Hi first off amazing job on this rom arrrghh. The only issue I'm having with this rom is when connected to my WiFi it will just randomly disconnect and go back to my lte service. And to re-enable it I have to go to settings>WiFi>and connect to my WiFi again. Not a big deal for me, just wanted to let u know this issue occurs. Also the issue I had with the supersu on the cm10.1 rom isn't happening on this rom. And I did clean fresh install no dirty flashing. But other than that problem everything works amazing. Keep up the good work ur the best.

sk8rguy05 said:
Hi first off amazing job on this rom arrrghh. The only issue I'm having with this rom is when connected to my WiFi it will just randomly disconnect and go back to my lte service. And to re-enable it I have to go to settings>WiFi>and connect to my WiFi again. Not a big deal for me, just wanted to let u know this issue occurs. Also the issue I had with the supersu on the cm10.1 rom isn't happening on this rom. And I did clean fresh install no dirty flashing. But other than that problem everything works amazing. Keep up the good work ur the best.
Click to expand...
Click to collapse
Hm, now I've heard on stock people having issues with wifi turning on & off.... but I don't think they had to actually re-enable it in settings.
So you say the wifi is not only disconnecting, but it is being disabled as well? IE when you go into settings, wifi is set to 'off' and you have to flip it back 'on'? Or are you just cycling it off/on in order to get it working again...

One bug that I am noticing with the latest build is in portrait mode the bottom corners of the screen do not respond to touches. In the screenshots below it shows me touching the search option in the phone app, the #'s button on the keyboard to change to using #'s and the save in the lockscreen shortcut options. I had to hit these repeatedly to get the screenshots and they still were not responding to touches.
I never dirty flash and I tried rebooting and also wiping and reflashing but dosen't resolve the inssue.
Sent from my Motorola Photon Q LTE using Tapatalk 2

dwaynet89 said:
One bug that I am noticing with the latest build is in portrait mode the bottom corners of the screen do not respond to touches. In the screenshots below it shows me touching the search option in the phone app, the #'s button on the keyboard to change to using #'s and the save in the lockscreen shortcut options. I had to hit these repeatedly to get the screenshots and they still were not responding to touches.
Click to expand...
Click to collapse
Hm, I don't think I noticed this. I'll check it out, thanks.

arrrghhh said:
Hm, I don't think I noticed this. I'll check it out, thanks.
Click to expand...
Click to collapse
It may be a hardware issue (hopefully not) I just flashed previous build before the bug and now I'm having the same issue. I'm going to restore a backup of cm 10.1 and see if its there also.
Sent from my Motorola Photon Q LTE using Tapatalk 2

BeanStalk Build *Developers ONLY* Updated 12.9.2015 - Support and Assistance Thread.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread has been opened to help avoid clutter in the original BeanStalk thread and to provide a centralized place to assist developers and porters with any issues they may be having with providing BeanStalk versions to their devices.
I will try my best to help out with any issue that is listed, but please remember that there are things that may be out of my control or things that im not aware of. I am hoping with creating a centralized thread for developmental discussion, other developers will also be able to assist when issues arise.
BeanStalk sources can be found HERE
UPDATE 12/14/2015
FYI... Beanstalk 6.01 was launched for nexus 6 (angler) this past weekend... Please take a moment to view the thread a d follow the new OP design (obviously change what's needed for your device) if building for a new device http://forum.xda-developers.com/nexu...2015-t3269156/
UPDATE 12/9/2015
Good news BeanStalk builders... After what seems like forever, its safe to say that BeanStalk is up and running and ready for android Marshmallow 6 builds. It is still based on CM as prior versions have been. I am taking a bit of a different approach this time though. Instead of having a specific menu from the main settings screen with the extras that I am adding in, I decided to integrate all the additional features into the existing CM settings menus... So added features will be in all areas of the build. I am going to be maintaining for the Nexus 6P (Angler) and plan on opening the OP Thread later this evening (time permitting of course)... The big change is going to be where the BeanStalk files are stored. With the fall of Goo manager, I had to find another file server. I am registered with a few files servers, but decided to use romwarehouse and would like to try to keep the builds from other devices stored there as well (for OTA purposes). This is the main address where the device folders will be listed http://romwarehouse.com/scott.hart.bti/beanstalk/
Please contact me via hangouts or gmail ([email protected]) so that I can setup your device folder and provide username and password information.
I will need to create a new OP for the BeanStalk threads. If anyone would like to get something created, that would be a big help. Once the OP is created, I would like everyone else to use the same format.
Important build related Info and fixes:
BeanStalk builds will not be implementing any of the new cmparts code. Instead, BS will keep the old format with the advanced device settings options. This means that you need to make sure that your device repo has the advanced settings code available and you need to make sure you revert any changes that you pull from CM that are for the new cmparts... if you have the cmparts commits in your device repo, it will cause build errors since it wont be in the frameworks/settings repos.
If you are a current BeanStalk builder/maintainer: I currently was setup with a website thanks to a friend of mine and it is located at www.scotthartbti.com. The main point of me setting up a website is a way to centralize all the different beanstalk builds out there. So, what im going to need from you guys... Please email me at [email protected], gtalk me at [email protected], or message me on xda with the device you build for and a link to where your zip files are located for download. I will then add a link to my website to your downloads.
So your interested in Building/Porting for another device?! Follow this guide! **Please make sure to give proper credits and Use the layout i have in the first post.** - If you need assistance, please send me a PM, do NOT post questions in this thread. I may open a general porting/building thread in another section depending on how this goes. You must have some general experience/knowledge in this area to complete this. Building from Linux platforms. In particular Ubuntu 10.04
Setup to build - This section can be skipped if youve ever built anything before. This is for first time build setup.
1. From your root terminal location, type the following: sudo apt-get install curl git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
2. Type: mkdir ~/bin
3. Type: PATH=~/bin:$PATH
4. Type: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
5. Type: chmod a+x ~/bin/repo
From terminal
1. type 'cd'. This will bring you to your root folder.
2. type 'mkdir beanstalk'. This will create a folder named beanstalk.
3. type 'cd beanstalk'. This will take you to the beanstalk directory created from previous step
4. type 'repo init -u git://github.com/scotthartbti/android.git -b cm-10.1'. This will setup the folders to be synced.
5. type 'repo sync'. This will sync the folders to your beanstalk directory. Note - This will take some time depending on internet connection. Be patient!
6. After the repo sync finally finishes, all you need to do is add your device, kernel, vendor specific files for the device you are building for. (You must know what these are, dont bother asking me if your not sure.)
7. Make sure all your device specific files are setup as if you were going to build for CM.
8. Outside of terminal, navigate to beanstalk/vendor/cm. Double click on the get-prebuilts file and select run in terminal. This will fetch necessary files needed to build and place them where they need to be.
9. Type '. build/envsetup.sh && brunch "device name"'
10. Previous step will start building beanstalk for your device. The process takes anywhere from 1 - 3 hours depending on your computer.
11. Once completed, it will say package complete and you will have a beanstalk named zip file in your out folder.

scott.hart.bti said:
Honestly... Unfortunately there isnt an EASY way. Basically... Just need to watch what we pull into our source files and if you get a build error, check out the CM side of things... Chances are it was an addition on the CM end that was not added to the Beanstalk side of things yet... In this latest case, CM added the privacy guard to their frameworks/settings/browser/contactsprovider/telephonyprovider... We use the telephonyprovider and browser directly from their repo... So it was kind of impossible to avoid issues until I was able to add in the necessary changes to the other repos... Which i have done so now so we are good to go.
Click to expand...
Click to collapse
Thanks man,
I read that when I managed to get a working build, good experience for the future
I reverted the privacy guard in
Browser
https://github.com/CyanogenMod/andr...mmit/2a654f8713cc3af108192dd33517d363e20b9984
CalendarProvider
https://github.com/CyanogenMod/andr...mmit/c3ad288607c873c90e50ee8ac3d3aa3f5aa0e5e2
TelephonyProvider
https://github.com/CyanogenMod/andr...mmit/60511cf58e4308cef91b817ee546fee2040f4b69
Good thing it should be fixed for easy building now

willl03 said:
Thanks man,
I read that when I managed to get a working build, good experience for the future
I reverted the privacy guard in
Browser
https://github.com/CyanogenMod/andr...mmit/2a654f8713cc3af108192dd33517d363e20b9984
CalendarProvider
https://github.com/CyanogenMod/andr...mmit/c3ad288607c873c90e50ee8ac3d3aa3f5aa0e5e2
TelephonyProvider
https://github.com/CyanogenMod/andr...mmit/60511cf58e4308cef91b817ee546fee2040f4b69
Good thing it's fixed for easy building now
Click to expand...
Click to collapse
Yea... Most of the time you just need to keep an eye out on the commits device/kernel side, but this was a rare case where there was a CM change that expanded across numerous packages.... Maybe i just need to be quicker with adding in all the changes.. Ha.
Only other alternative i could use would be to add EVERY entity to the BeanStalk repo and manually add every change... but since im only one person and not a team of numerous people, that would literally take FOREVER... I am sure i can find a script to help take care of things quicker, but still...

Thanks Scott. Glad to see this. No issues so far on the N7000 with the latest build.

asf58967 said:
Thanks Scott. Glad to see this. No issues so far on the N7000 with the latest build.
Click to expand...
Click to collapse
Glad to hear! I should have done this a WHILE ago, but havent had much free time... My son is due in a little less then a month now... I can only imagine how hard its going to be to find time then.... I get no sleep now as it is... Some fun times ahead... lol.

scott.hart.bti said:
Yea... Most of the time you just need to keep an eye out on the commits device/kernel side, but this was a rare case where there was a CM change that expanded across numerous packages.... Maybe i just need to be quicker with adding in all the changes.. Ha.
Only other alternative i could use would be to add EVERY entity to the BeanStalk repo and manually add every change... but since im only one person and not a team of numerous people, that would literally take FOREVER.
Click to expand...
Click to collapse
There is one last think I keep having to revert when I build
The gps for my device, since it was moved and updated with some new code from my device specific repo to my device qcom common repo, I have to revert all gps related changes in thrse two repos in the last month to get it working on beanstalk
You fixed a similar issue when we had trouble with samsung phones telephony fc'ing with a simple merge from CM, I don't know if it is possible for you to do a similar merge to get our gps working out of the box
Thank you for creating the ultimate rom out there!
Sent from my ATARI-JAGUAR using 64bit Mathematics
---------- Post added at 04:06 AM ---------- Previous post was at 04:04 AM ----------
scott.hart.bti said:
Glad to hear! I should have done this a WHILE ago, but havent had much free time... My son is due in a little less then a month now... I can only imagine how hard its going to be to find time then.... I get no sleep now as it is... Some fun times ahead... lol.
Click to expand...
Click to collapse
Hehe good luck!
Sent from my ATARI-JAGUAR using 64bit Mathematics

scott.hart.bti said:
Glad to hear! I should have done this a WHILE ago, but havent had much free time... My son is due in a little less then a month now... I can only imagine how hard its going to be to find time then.... I get no sleep now as it is... Some fun times ahead... lol.
Click to expand...
Click to collapse
I figured I'd pop in and say all is good with the galaxy s4. Just like old times on the Infuse..only now with a quad core beast.
And Scott, best of luck with your son!

I have a very minor issue with BeanStalk since I started building it,
Chrome browser and the others based on it's engine have no momentum in scroll. As soon as you take your finger off it stops scrolling completly, no scrolling continuity
Is it specific to my device build of beanstalk or it's also true for you

willl03 said:
I have a very minor issue with BeanStalk since I started building it,
Chrome browser and the others based on it's engine have no momentum in scroll. As soon as you take your finger off it stops scrolling completly, no scrolling continuity
Is it specific to my device build of beanstalk or it's also true for you
Click to expand...
Click to collapse
It happens on my build too. Never really looked into it, but it is a little annoying.

willl03 said:
I have a very minor issue with BeanStalk since I started building it,
Chrome browser and the others based on it's engine have no momentum in scroll. As soon as you take your finger off it stops scrolling completly, no scrolling continuity
Is it specific to my device build of beanstalk or it's also true for you
Click to expand...
Click to collapse
Ill look into it... Since its only happening with Chrome based browsers, id have to think its an issue on that end of things... but ill see what i can find.

@willl03 did u try the idea for maybe a stylus gesture fix I PM'd you?
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

asf58967 said:
@willl03 did u try the idea for maybe a stylus gesture fix I PM'd you?
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
Click to expand...
Click to collapse
Is it possible to use overlay's to disable some of the settings options.
I'm building on Maguro and we don't have physical keys so it annoys me seeing the settings entries for them

Is this familiar to anyone? I clobbered and resynced first thing and this is the result:
Code:
[email protected]:~/beanstalk$ repo sync
Fetching projects: 100% (359/359), done.
core/java/com/android/internal/util/cm/QSConstants.java: needs merge
packages/SystemUI/res/values/cm_strings.xml: needs merge
packages/SystemUI/src/com/android/systemui/quicksettings/QuickSettingsTile.java: needs merge
packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java: needs merge
error: you need to resolve your current index first
Syncing work tree: 100% (359/359), done.
error: frameworks/base/: scotthartbti/android_frameworks_base checkout a880f03be35ccbc3c6d7a3373e9cb0e688cc48ae
[email protected]:~/beanstalk$
Is there more going on overnight that I've missed? I took a quick look at CM review and didn't immediately see anything....

BMP7777 said:
Is this familiar to anyone? I clobbered and resynced first thing and this is the result:
Code:
[email protected]:~/beanstalk$ repo sync
Fetching projects: 100% (359/359), done.
core/java/com/android/internal/util/cm/QSConstants.java: needs merge
packages/SystemUI/res/values/cm_strings.xml: needs merge
packages/SystemUI/src/com/android/systemui/quicksettings/QuickSettingsTile.java: needs merge
packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java: needs merge
error: you need to resolve your current index first
Syncing work tree: 100% (359/359), done.
error: frameworks/base/: scotthartbti/android_frameworks_base checkout a880f03be35ccbc3c6d7a3373e9cb0e688cc48ae
[email protected]:~/beanstalk$
Is there more going on overnight that I've missed? I took a quick look at CM review and didn't immediately see anything....
Click to expand...
Click to collapse
I'd delete everything and make a repo sync from scratch, all is fine on my side
Sent from my ATARI-JAGUAR using 64bit Mathematics
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
willl03 said:
I'd delete everything and make a repo sync from scratch, all is fine on my side
Sent from my ATARI-JAGUAR using 64bit Mathematics
Click to expand...
Click to collapse
With v1.253, I see that Tasker can not detect the running app
I have a ton of profiles for specific apps and none of them work. Looks like the "top window" is not seen as the foreground app anymore. I tried disabling halo and no change.
I don't have any clue, works fine on v1.240 and previous. Tasker app detection works for you guys on v1.253?
Sent from my ATARI-JAGUAR using 64bit Mathematics

sykomaniac said:
Is it possible to use overlay's to disable some of the settings options.
I'm building on Maguro and we don't have physical keys so it annoys me seeing the settings entries for them
Click to expand...
Click to collapse
You can apply a patch to remove he settings entry. I will try to find the guide when I get to my office later.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

willl03 said:
I'd delete everything and make a repo sync from scratch, all is fine on my side
Click to expand...
Click to collapse
I assumed that is what was needed, so I make clobbered first thing and resynced; no love. But, maybe I'll have better luck when I get home....

BMP7777 said:
I assumed that is what was needed, so I make clobbered first thing and resynced; no love. But, maybe I'll have better luck when I get home....
Click to expand...
Click to collapse
More than a repo sync, delete your whole beanstalk folder and start from scratch. Had to do this a few times to get things working in the past
About tasker, can anybody let me know if the app detection works on your side
There's a trial of tasker available here if you don't use it
http://tasker.dinglisch.net/download.html
I really need to get this working, it's the single most important app I'm running on my phone
Thanks
Sent from my ATARI-JAGUAR using 64bit Mathematics

This is not really an error but more of an aesthetic issue. When I click on About BeanStalk, the images don't load. The code looks good, maybe it's just an issue with my phone trying to dl the pics?

willl03 said:
More than a repo sync, delete your whole beanstalk folder and start from scratch. Had to do this a few times to get things working in the past
About tasker, can anybody let me know if the app detection works on your side
There's a trial of tasker available here if you don't use it
http://tasker.dinglisch.net/download.html
I really need to get this working, it's the single most important app I'm running on my phone
Thanks
Sent from my ATARI-JAGUAR using 64bit Mathematics
Click to expand...
Click to collapse
Do mean the multi task manager when long pressing the home button? All good here.
And yeah, I deleted my entire build folder a couple of times. A fresh repo helps.
Sent from my SAMSUNG-SGH-I717 using xda premium

patch_Adams said:
Do mean the multi task manager when long pressing the home button? All good here.
And yeah, I deleted my entire build folder a couple of times. A fresh repo helps.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
The Tasker app to automate actions, it is for sale in the play store or there is a trial in the website I linked
Sent from my ATARI-JAGUAR using 64bit Mathematics

[ROM][Unofficial]Firefox OS 2.0 Pre-Release for Kindle FIre HD 7[5/22 Alpha]

*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THIS SOFTWARE OR SOMETHING ELSE SUDDENLY FRIES YOUR DEVICE. ***
Firefox OS
Download Info:
Latest Build: [2014-05-22] Alpha 2.0 Pre-Release
Links:
Dev-Host: Download
Md5sum: 1b9e59c7af3ef6f481f736c207dce1df
Older Builds:
[2014-05-20]
Links:
Dev-Host: Download
Md5sum: cf1cabaa21cd4b3767449bc7300666b0
[2014-03-12]
Links:
Dev-Host: http://d-h.st/1qH
Md5sum: 8799eafb470354ad0ecc717f0fb3ad88
[2014-02-36]
Links:
Dev-Host: http://d-h.st/gkB
Md5sum: 8c1635cf11375db632b0f5f3f4897737
Ok i have been working on this for a few months and finally got around to uploading my latest build and decided to make this public. This is Firefox OS ported to Kindle Fire HD 7". It is still quite buggy but I believe alpha status sounds about right at this point. Here's some info about this OS in case people want to know the technicalities. This OS is based on AOSP 4.3 using hashcodes cm 10.2 device tree with some modifications. While it is based on AOSP Android, this OS is only based on it in the sense its core is based on android, it has no dalvik virtual machine so don't even bother flashing a gapps package with it, it wouldn't even recognize it inside the OS.
I have to give a big thanks out to Hashcode, for putting up with all my questions in the irc about building rom's considering i'm totally new to compiling an android os, much less troubleshooting the technical things. Also have to give a big thanks to the Mozilla dev's in their irc because they helped me quite a bit in figuring out how to get past the main bug i was having(especially gerard-majax). For those of you who weren't in the testing you would'nt know but the original builds of this would boot up to the firefox boot animation, flash a white screen and then blank. Managed to work around this rather than fix it for now thanks to them, along with answering alot of my questions that are more inside Firefox OS's realm rather than android's. Now that i mentioned that i have to thank all my tester that helped me get this project off the ground by testing the rom out and reporting any bugs, along with just reporting if the latest build worked. These people include but not be limited to: Jserrano56, LinearEquation, Ph0enix_216, r3pwn, viktormax3, trinaldi, south956, and Latonya1. If i left anyone out i'm sorry, i grabbed everyone's names from my sent items rather than browsing the entire thread where everyone volunteered. I will add screenshots as soon as i can.Screenshots added! Sorry for there not being any lockscreen pics, i can't take them because the shortcut for screenshot in Firefox OS is power + home button, and there are no softkeys in the lockscreen for homebutton...
Screenshots:
{
"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"
}
Now let me list some bugs it has that are currently being worked on to the best of my limited capabilities:
[Pre-2/26]
Battery Gauge doesn't work - Fixed sorta (see new bug below that was caused by fixing this)
[2/26]
Gralloc is disabled because of bug with sgx gpu's so theres some laggyish graphics < Fixed [2014-03-12] (thank you mozilla devs for patching this!)
"Insert SIM Card" message is displayed on drop down menu and lockscreen < I'm looking into this, all i know is i need to figure out how to disable RIL
Camera is broken - now compiles sucessfully but still doesn't work (mediaserv crashes and burns)
Video Playback wont even initiate < still not sure about this problem, trying to look into it- Fixed [2014-05-20]
Issue where device tends to not want to come out of sleep mode unless plugged into charger < Looking into - Fixed [2014-05-20]
Bluetooth isn't working yet - Fixed [2014-05-22]
Miscellaneous GUI glitches < These are more than likely mainstream since version 1.3 was being stabilized until recently.
Charging Loop on lockscreen when charged by usb low power < still looking into this
sdcard is a bit glitchy
mtp isn't working (adb works fine though)
usb connection restarts every so often < probably related to why mtp isn't working
small boot animation < not sure if i should stretch this or fill in the background with blue or see if mozilla devs have a higher res version somewhere
Note that like i mentioned in the bugs, this is based on a 1.4 Pre-Release, which isn't exactly the most stable branch. If you are wondering why i used an unstable branch the answer is simple, 1.3 is based on ICS sources, and i didn't have an ICS device tree to work with. At this point i guess you could say this OS is comparable in a sense to Ubuntu Mobile OS, simply because android is more popular, but as i like odd things i decided to go for it with this ROM, so I will say this, if all you use your Kindle for is email, browsing the web and listening to music, then this ROM would be good for that, it was designed to be Completely html driven. It should run smoother than it does now in the coming updates.
So without further ado let me post some instructions for flashing this ROM:
***Notice*** Please make sure you have at least twrp 2.6.3.1 installed or you may encounter problems.
Download the ROM above and place on sdcard
Boot into twrp
Do a factory reset
Hit Install
Choose the ROM
Reboot
Profit!
Notice: I am looking for developers that would like to help me with this project as i don't know any C++ or C coding, so the bugs i can fix are limited to what i can find that is simple or simple enough in C++ that i can change a string here or there. So please if you aren't busy or are interested i would love some help fixing things.
Now for any developers that are interested here is a small tutorial on how to download and compile this because the process is slightly different than the android setup by a little:
First off i suggest reading the setting up the build environment herethat Mozilla made, but keep in mind some things when following their instructions, their build instructions were designed around the stable 1.3 branch which I'm not using, so certain things like the compiler versions they list are incorrect so for what they call for using as gcc and g++, install the 4.7 version. Another thing they don't mention because i stray from their path is you will in fact need Java, so make sure that's installed. i included a preset .userconfig to specify the correct version of gcc and g++ to be used, if its in a unusual path or something look in the .userconfig file to change it(its in the root folder of the build environment). I also advise setting the ccache higher than they put it at, it usually works at what they set it to but recently i couldn't get it to build until i set it to 5GB. One last thing i haven't automated yet is because this was a non Java using OS the signapk.jar file doesn't get auto-copied to the folder it needs to be in when the otapackage is made so if you ever make clobber or its your initial build remember to
Code:
cp tool/update-tools/bin/signapk.jar out/host/linux-x86/framework/signapk.jar
Ok that paragraph appears to be a bit of a mess but i think i put the core info for setting up a build environment in there. Next how to download and set everything up. First off goto the folder you want to set this up in(for me it was my home folder) and run
Code:
git clone https://github.com/stunts513/B2G.git
once that is done run this:
Code:
./config.sh tate
Now go do something for a few hours because its going to download a lot of data.
Now that it is done downloading there is something important you need to do or it will complain about missing dependencies, go into the frameworks/base/graphics/jni folder and rename Android.mk to Android.mk.disabled or just delete it. I suggest if you want to put this in another name other than your login name on Linux to "export USER=blah". Ok now things get different but simple, run this
Code:
./build.sh -jX
where X is the number of physical + logical cores your pc has. Once the build process finishes run
Code:
./build.sh otapackage
Once that is done you would think "yay my build is complete", but no it never could be that simple, lemme explain the next steps to do until someone helps me recode some python scripts.
Now that we have a signed apk we need to add some things to it to get it finished because the python scripts need some editing i don't know how to do. Go into the out/target/product/tate folder and open the zip file it created up, add the data folder into it. Now open the META-INF/com/google/android/updater-script and find this line
Code:
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_dir("system", "/system");
right after it add these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata", "/data");
package_extract_dir("data", "/data");
and don't forget at the end to add the
Code:
unmount("/data");
before the
Code:
unmount("/system");
Now that that is over with grab the last command you see outputted in the terminal about running java -jar signapk.jar and modify it so it doesn't have the /tmp directory as the input file, and make the output filename whatever you wish. Tada theres a successful build for ya. if you want to look at it i have this info on my github wiki for b2g in case i either left something out or had extra info on there.
XDA:DevDB Information
Firefox OS, ROM for the Amazon 7" Kindle Fire HD
Contributors
stunts513
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 2nd bootloader and twrp 2.6.3.1 or higher
Based On: AOSP and a CM device tree
Version Information
Status: Alpha
Created 2014-02-27
Last Updated 2014-05-27

Nice work stunts!!
Sent from my Nexus 4 using Tapatalk

Thanks! Hopefully this will attract some dev's and some people might get interested in this os. I find this is very interesting in the sense that all the apps are literally coded in JavaScript and html5, so practically anyone could learn simple languages and make apps, I already have been learning a bit of JavaScript myself so I can understand what's going on in Gaia a bit better (Gaia is what the ui is called for those not informed). Learning JavaScript is kinda interesting because its the first object oriented language I've learned I believe. Anyways things I'm going to need a dev's help with more than likely are the camera, the Bluetooth, and the video playback issue. I have some leads with video playback but haven't had very much luck with figuring it out. Anyways I hope to see more people posting in and their thoughts plus any bugs they found/I forgot to mention. By the way I recommend trying the games out, they run quite smoothly considering I have gralloc disabled, I was surprised that games like solitaire actually had dragging and such, I'm kinda new to html5 so it actually surprised me.
Sent from my Amazon Kindle Fire HD using Tapatalk

Great job, stunts. I'm definitely gonna give this one another go.
Sent from my iPod touch using Tapatalk

upload pics please ! great work !

Thanks, BTW I did upload pics, because this is a devdb thread it has a screenshots button up at the top so I didn't think I really needed to put pics in the main post but I guess I can because they aren't exactly in your race the way it is. I'll link them into the post when I get on my PC.
Sent from my Amazon Kindle Fire HD using Tapatalk
Edit: ok i put linked the screenshots that were there already so they show up on the main post, if you think i put too many or they are too big or somethign please feel free to tell me so.

This is just AWESOME!! Thank you for this
Sent from my LG-E430 using XDA Premium 4 mobile app

stunts513 said:
Thanks, BTW I did upload pics, because this is a devdb thread it has a screenshots button up at the top so I didn't think I really needed to put pics in the main post but I guess I can because they aren't exactly in your race the way it is. I'll link them into the post when I get on my PC.
Sent from my Amazon Kindle Fire HD using Tapatalk
Edit: ok i put linked the screenshots that were there already so they show up on the main post, if you think i put too many or they are too big or somethign please feel free to tell me so.
Click to expand...
Click to collapse
exellent work. keep like this !

Thanks for the support! I have been looking into disabling ril so that annoying insert sim message will go away, I kinda made some progress on it but its kinda half and half progress, I'm twiddling around with gaia's innards, and someone mentioned there's a way to build Gaia that's meant for a tablet so I tried it, here's the upside so far about it, it took the annoying sim message away, and has a slightly different layout with only 2 pages on home screen and I think the search box was disabled. This is the downside, it took away the games collections and such, the icon for insert sim is still on the status bar and the lock screen still says no sim. Even worse than that was the fact I believe the only way I can put it into practical flashing use is to make a production build rather than a user debug build, in order for me to even test it I had to wipe data, and then run a make file that pushed the needed files via adb. Even weirder to me is I found out as it is right now I was thinking I need to edit hashcode's python scripts for building the otapackage to include /data to be auto included in the packaging process, and after seeing how a production build is made I see why it's unnecessary, a production build actually puts them on the system partition. Might still add a command line option to the scripts for if its a user debug build to do so. Sorry if this seems like confusing ramblings, I find it fun talking about technical things.
Sent from my Amazon Kindle Fire HD using Tapatalk

Haha stunts, the beauty of having your own rom thread is you can ramble all you want! Thanks for your efforts, I'll be checking it out!
Sent from my MB865 using xda app-developers app

Looks promising. Be keeping an eye one this. Once it turns beta I'll give it a try. Keep up the good work.
I checked this out I really like it. Hope you keep up with this.
Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app

Update!
Ok, here's an update, have a major bugged fixed in this release as well as minor graphical bugs.
Update: [2014-03-12] Alpha 1.4 Pre-Release
Links:
Dev-Host: Download
Md5sum: 8799eafb470354ad0ecc717f0fb3ad88
Whats fixed in this update:
-gralloc works now (thank you mozilla devs for fixing this)
-misc gaia(the homescreen/gui) fixes.
What these fixes mean:
With gralloc functioning now, the graphics are much much less laggy, and i can also start troubleshooting the video playback issues a bit more than previously. You will now notice a nice artifacting loading logo on videos in youtube, and on games like safecracker it will be a nice big fullscreen artifact on the screen while sound is playing.
Gaia misc fixes from upstream, they are nice little things that needed fixing that now work correctly, like that little bar of bleed through from the homescreen on certain apps and games is gone, things like that. I will update my screenshot now so that actually looks nicer.
Thanks to this update some things were brought out that i now can start throwing some guesses around as to whats up with video playback and the games and such that are artifacting. It probably has to do something with a buffer, but i have said this before i need a dev that will help patch this kinda stuff, i have no clue how to myself. All i know is most of the problems i'm having with video playback issues and artifacting and such are probably caused by the fact Mozilla has their own custom framework/av folder, which in turn i believe has its own custom libstagefright, this also i think had something to do with why i couldn't get the camera's hal module to compile. So if any dev is willing to take a look at this please help me.

Finally had a good time to test this out (if you call Argumentative Writing class a good time). Flashed well, booted without a hitch, and the setup wizard or whatever it's called went smooth. I've gotta say, nice job Other than the bugs you've already addressed, my only complaint was that the music app went into a scrolling loop when in the album art view, then crashed.
@stunts513, be proud of yourself - this is quite the accomplishment I only wish I could do something as awesome as this.

Thanks, I'm thinking about trying to build it for the other devices as well sometime this week to test it out and commit any tweaks I may need to make to compile for those devices. I've been doing other things lately so I haven't been booted into Linux much this week and my debugging hit a bit of a standstill, I'll try debugging it again soon and see if I can fix anything else.
Sent from my Amazon Kindle Fire HD using Tapatalk

Bump?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

Can't wait till this reaches its beta stages. Would definitely use it!
Sent from my Amazon Tate running CyanogenMod 11

Same here, I enjoyed watching it but the YouTube no video was the killer for me, does hulu work on it by any chance even thru chrome cast
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

Funny it would get bumped today. I've been upgrading to a cm 11 device tree kitkat based build for about 4 or 5 days. Been having to debug a error for the past few days that was driving me nuts and I finally got passed it. Even more surprising is the fact I didn't have to disable the camera and I think it compiled its module successfully. I just finished a build a while ago and plan on testing it tomorrow once I make a nandroid backup. My main issue is as it turns out from multiple devs telling me(hashcode and gerard-majax) I added some unneeded stuff to the manifest back in the jb builds. Apparently just because the compilation process requests it and errors out without it doesn't mean its required(this really surprised me). Long story short some llvm and clang related stuff was being compiled thanks to some librs related stuff and erroring out for some reason and it turns out I had to kill it at the source. Let's hope my build works, I'll try to post the results depending on if I go shopping for parts for my microwave or not.
Edit: oh and as to the video, I have not heard of b2g having chromecast. I don't know if they would support it or not considering its based on googles work but forked in a different direction. And no as of that last build no video was working. I think it was something with ducatti not working right so none of the video would even decode and there was some kinda buffer error with I think open on related animations so even of the decoder worked I think it would a been artifacting like the YouTube play button and such. Hopefully the cm 11 builds will work better. I still don't have a dev to help me with this so progress is kinda slow seeing as I don't know c++ I can't do too much. I'm just glad all the devs have put up with my questions up until now as I know how annoying I can get. It's not often I find tech savy people that know more than me about PC's as i come from a small town so I tend to have a million questions when I find someone smarter than me.
Sent from my Amazon Tate using Tapatalk

UPDATE!
Download Info:
Latest Build: [2014-05-20] Alpha 1.4 Pre-Release
Links:
Dev-Host: Download
Md5sum: cf1cabaa21cd4b3767449bc7300666b0
Update info:
-updated to a kitkat build with the cm 11 device tree
Fixes:
-Fixed video playback - (actually hashcode did, i just pulled in changes from his repo and it worked)
-Camera doesn't work but the module is compiling now so camera *may* work soon, don't hold me to it.
On another note, i noticed while atleast video playback is working not all video files are openable, but i haven't tried much outside of a random file left over from a android game that it found so i don't know the extent of what can and can't be played. The file i played had audio and no video.
Oh and something important you need to do when you first boot into it, enable soft home from settings>developer options, for some reason the previous method i used involving a build.prop property didn't work this time around. Kinda annoying...
Todo:
- In the next few days i'm going to sync up my sources with hashcodes again becasue he said he's got some camera fixes he's working on that might help.
- See if the hwc will build and load on cm11 builds as it may fix the artifacting on certain games

Nice will try asap, today's too late and I just saw......imma download though
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

[TEMPORARY HALT][ALPHA][3.4][ZRAM][SDCARDFS]Experimental Nexus 7 kernel build

Code:
*** Disclamer ***
[U][COLOR="red"]NOTE: This is an experimental build with some bleeding edge features enabled.[/COLOR][/U]
I'm not responsible for anything that may happen to
your tablet as a result of installing custom roms and/or kernels.
You do so at your own risk and take the responsibility upon yourself.
CREDITS:
Ziyan , Sheffzor for setting up their Unlegacy Android project, which is the base of this experimental build.
If you can afford to support some of the developers, please donate to them instead of me.
Shout-out to:
AndDiSa, ParrotGeek, daniel_hk, and franciscofranco for their involvement in Nexus 7 kernel/ROM development.
Features:
The same as Unlegacy Android's kernel, with the addition of ZRAM & ZSMALLOC from upstream kernel 3.10 , and with the addition of SDCARDFS.
Installation:
0. MAKE A BACKUP
1. This kernel is compatible with Unleagcy Android's ROM only, and nothing else.
2. If you have the above mentioned ROM installed, boot in to bootloader mode and flash the boot.img with the following fastboot command:
Code:
fastboot flash boot boot.img
3. If you were previously rooted, don't forget to re-apply root to avoid any related boot loops.
4. Altough ZRAM is added as a feature you have to actually set a size to it in Kernel Adiutor (or some other similar kernel manager app)Download#1/Download#2 and tick "Apply on boot" and reboot your device to turn it on.
Or alternatively create an init.d script to enable it with your desired size at boot.
You can verify if your swap/zram device is working by typing "free" or "vmstat" into a terminal emulator.
If the size of the swap device is anything but 0, it will work.
{
"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"
}
Zram is set to LZ4 compression and 4 streams by default, swappiness is set to 50.
5. [Optional] SDCARDFS is enabled by default , you can verify that its working by typing the following commands into a terminal emulator:
Code:
su
df -t sdcardfs
If some lines shows up like on the picture below then SDCARDFS works just fine.
6. Various ramdisk scripts like re-mounting the drives and trimming are currently not added, to avoid any bug reports related to these additions. You can still use SSD Boost or FSTrimmer app to achieve these effects. If this build proves to be stable enough we can look in to adding the scripts to the ramdisk.
7. Have fun
Bugs:
Same as on the base 3.4, for example I rarely encounter a hang/freeze with some graphical glitches, but it's pretty much the same with the unmodified base version.
Due to the lack of a Tilapia device, I was only able test the kernel on a Grouper.
SDCARDFS is highly experimental, it caused some issues on other devices for some users (like space not freeing up after deleting some files), although it works fine for me, you should bear this in mind when you install this kernel.
As mentioned above, you have to either enable swap for zram via an init.d script or via a kernel manager app like Kernel Adiutor.
This is despite the fact that the block device is added to the fstab and swapon_all is added to the init.grouper.rc . Still have to figure out how to get around this, but currently i don't have the time to do so.
Downloads:
Check the downloads tab at the topic title, or
click here for the download link
Sources:
https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Changelog:
2017.06.26
Initial release
Added and enabled ZRAM & ZSMALLOC from upstream 3.10
Added and enabled SDCARDFS
Enabled F2FS for both Cache & Data
XDA:DevDB Information
[TEMPORARY HALT][ALPHA][3.4][ZRAM][SDCARDFS]Experimental Nexus 7 kernel build, Kernel for the Nexus 7
Contributors
namerke, Ziyan, Sheffzor
Source Code: https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Kernel Special Features: SDCARDFS, ZRAM, F2FS CACHE/DATA
Version Information
Status: No Longer Updated
Created 2017-06-26
Last Updated 2017-11-10

Reserved

Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).

Geko45 said:
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Click to expand...
Click to collapse
Well, as said in the list of bugs, tilapia is not tested at all due to lack of device.
But if you didn't perform a clean install than it can take it's time to get through the bootloader screen, even on grouper. So make sure you wait there for a while.
On clean install I didn't encounter this issue.

Aside from the freezing issue, this is way smoother than stock.
My current config includes
200MB Zram (swappiness 100 - like Andisa's)
CPU quiet policy: runnable (experiment in reducing the freezes)
interactive perameter 'midrange_go_maxspeed_load' reduced to 90 from its default of 95.
Root Killing SystemUI when the screen is off (Again to try to prevent freezing/need for manual reboot)
SSD Boost
Running this command at startup :
Code:
service call SurfaceFlinger 1009 i32 1
(old habit - suggestion of parrotgeek's to speed up rendering of transparency)
Current result: freezing maybe eliminated, time will tell...
Current theory: Freezing may be due to excessive background cpu load, ie. the system trying to do too much at once. SystemUI may have nothing to do with it, but I still have my suspicions.

35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...

adstraylight said:
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
Click to expand...
Click to collapse
why the force gpu 2d rendering?

abhifx said:
why the force gpu 2d rendering?
Click to expand...
Click to collapse
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs ?

adstraylight said:
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs
Click to expand...
Click to collapse
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.

abhifx said:
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
Click to expand...
Click to collapse
Amateurs of the world unite!?
It was something I remembered from trying to optimise MM on grouper that made a lot of difference at points.

So I've stopped killing the systemui, rebooted, and have had 19hrs of uptime since, so I think we can discount that as a cause.

I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good ?

adstraylight said:
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good
Click to expand...
Click to collapse
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again

abhifx said:
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
Click to expand...
Click to collapse
My guess is that they're already aware of what's been posted here, how are you finding it?

adstraylight said:
My guess is that they're already aware of what's been posted here, how are you finding it?
Click to expand...
Click to collapse
they are relying more on changes pushed to their gerrit rather than tracking all the thread. so i dont know posting in their thread is also a good idea.. but hey its better than nothing.

@namerke great to see someone build something off of the work the 3.4 guys achieved. This was the sort of thing we hoped for from the beginning and I really am surprised that you're the only one so far, years after the project started, to brave the source code and use it for a project.
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream? Cheers

I am running @adstraylight suggested tweaks and its running Rock Solid. The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy. After the initial start the tablet stops having any system ui, force close, or mtp reboot issues. Boot is much faster and functions more like a normal tablet. I would recommend these changes to be incorporated into grouper unlegacy because as of now, running stock unlegacy with updated builds still has freezing, random rebooting and general issues with slowdowns. Honestly I still don't know why F2FS got scrapped for data and cache. I get that they are working on adding support for a lot of devices but it's just not useable in its current form with stock Unlegacy, unless you are okay with systemui freezes and random reboots.

New version is up, please refer to the #1 post for the updated changelog.
adstraylight said:
My current config includes
200MB Zram (swappiness 100 - like Andisa's......
Click to expand...
Click to collapse
Hi @adstraylight , thanks for all the feedback, it's been helpful , really, since i don't have much time to pressure test our device.
New version is including some of your suggestions to the interactive governor + some adjustments to it from Unlegacy-Android gerrit.
Also, @AndDiSa uses 250MB of ZRAM with swappiness of 60 by default , therefore this is the way I have configured the latest version since it seems to work just fine on 3.1 .
Number of ZRAM streams have been reduced to 1, just like @AndDiSa 's config, again , to reduce CPU load.
HTCDreamOn said:
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream?
Click to expand...
Click to collapse
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
chosin137 said:
The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy.
Click to expand...
Click to collapse
@chosin137 , thanks for the feedback. As it turns out, based on my experience F2FS on cache causes some instabilities on this version too, therefore I have removed the option to use in in fstab.grouper on the updated version.
Also, this way it will be closer to the base , which can help with merging if @Ziyan and @sheffzor decides to go that way.
Thank you all for the feedback, happy testing

Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
Click to expand...
Click to collapse
Makes sense, I've seen a lot of kernels using zram and similar from 3.10. That could be it, it doesn't look like zram is enabled at all in the default kernel but I find it odd that it would be missing the files. I only just flashed the recent version of the ROM a few days ago so it's running fine on the stock kernel, will give yours a go once I've bogged it down with some more apps though.

sadly my experience is on the negative side as i can easily completely freeze my tablet. only reboot is the solution. i guess i have seen this issue more in the stock 3.4x kernel too so i guess its more of a rom / memory leakage issue. However the tab does feels smother than other 3.1x kernel based rom. so the tweaks does seem to help more. i might try flat rom+kernel for while, if things are better then i can blame gapps and remove it altogether (although i do want maps for navigation purpose)

[ROM][UNOFFICIAL][7.1.2][NX551J][OMS] CarbonROM 5.1 for Nubia M2 [28/07/18]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM 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, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
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!
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) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend OpenGApps.
What Works
Wifi
Cameras
Fingerprint (But it's a bit fiddly)
Softkey LED's
Basically the vast majority of stuff
What doesn't work
Bluetooth
Playback of FLAC music files through the stock music player and some apps like BlackPlayer
Rotation
You Tell me
Download
Join the CarbonROM Discord server
GitHub
Gerrit
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!
XDA:DevDB Information
CarbonROM, ROM for the Nubia M2
Contributors
tuxdude143
Source Code: https://github.com/CarbonROM
Kernel: https://github.com/HighwayStar/android_kernel_nubia_msm8953
Device Tree: https://github.com/HighwayStar/android_device_nubia_nx551j
Vendor Blobs: https://github.com/HighwayStar/android_vendor_nubia_nx551j
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.18.x
Based On: AOSP/CAF
Version Information
Status: Beta
Created 2018-07-28
Last Updated 2018-07-28

Personal Donation Link: https://paypal.me/tuxdude
Don't feel like you have to donate anything. I'm just happy to know that people are using the stuff I work on.
Come and join the Nubia M2 English Development Telegram Group: https://t.me/joinchat/C3fXPhDRoLRN5sBmm8lsfg
Please report any bugs you find in the thread in detail

wow, great work @tuxdude143!!
cant wait to try this rom, keep the good work bro...

Updated the opening post to reflect that music playback does actually work but FLAC files seem to be a bit fiddly. They refuse to work in the stock music player and some apps like BlackPlayer but they will play just fine in other apps like VLC or Foobar2000. Your mileage may vary.
MP3 playback works absolutely fine in all apps.
In the next build I plan to have bluetooth and rotation working and I'll try and bundle the nubia camera and gallery into the rom itself.

Thanks for your effort to develop for this device. Hope to try your rom as soon as my device arrives

Thanx
dmilz said:
Thanks for your effort to develop for this device. Hope to try your rom as soon as my device arrives
Click to expand...
Click to collapse
Thank you Tuxdude for making a custom rom for our Nubia M2.
i did install the rom and seems to be a beginnig of a good rom for our phones
unfortunatly i can not test this rom for long because bluetooth is not functioning and i need my bluetooth every day so i hope this will be solved soon
so i can do some long term testing and use it as dayly rom to help to find the bugs left and give more imput

tuxdude143 said:
In the next build I plan to have bluetooth and rotation working and I'll try and bundle the nubia camera and gallery into the rom itself.
Click to expand...
Click to collapse
Thank you Tuxdude. And thank you to Roland for make me aware of this ROM.
Do you have an idea of when do you plan to post the new build? Bluetooth is really necessary.
Anyway, I'll test it, as I can live without Bluetooth for the next few days. I hope there'll be few days
EDIT: I've been trying out the ROM. So far, so good. I don't have those reboots that I had with Lineage using substratum. Almost every hour I had a reboot. Not with Carbon.
EDIT 2: After more than 24 hours of use and two times charged, I can tell that battery use, even as we know that we have to let the ROM settle, is very high. From 100% to 15% in just 5 hours. Two times. Also, it is not a fast ROM. It takes a couple of seconds to register touch and launch the app. It still needs several maintenance and work. But on the plus side, substratum keeps working like a charm.
The only other bug that I found is that the Menu/Recents button doesn't work, even if I change their settings. Changing settings work for the menu button.

estuardo4 said:
Thank you Tuxdude. And thank you to Roland for make me aware of this ROM.
Do you have an idea of when do you plan to post the new build? Bluetooth is really necessary.
Anyway, I'll test it, as I can live without Bluetooth for the next few days. I hope there'll be few days
EDIT: I've been trying out the ROM. So far, so good. I don't have those reboots that I had with Lineage using substratum. Almost every hour I had a reboot. Not with Carbon.
EDIT 2: After more than 24 hours of use and two times charged, I can tell that battery use, even as we know that we have to let the ROM settle, is very high. From 100% to 15% in just 5 hours. Two times. Also, it is not a fast ROM. It takes a couple of seconds to register touch and launch the app. It still needs several maintenance and work. But on the plus side, substratum keeps working like a charm.
The only other bug that I found is that the Menu/Recents button doesn't work, even if I change their settings. Changing settings work for the menu button.
Click to expand...
Click to collapse
Thanks for reporting these bugs. At the moment I'm looking into fixing bluetooth, rotation etc and hope to have them working in the next build.
Battery usage is also something I'm working on. I know Deep Sleep works fine but battery management isn't the greatest. I'll try and either fix that in the next update or the update after.
Thanks for the feedback!

tuxdude143 said:
Thanks for reporting these bugs. At the moment I'm looking into fixing bluetooth, rotation etc and hope to have them working in the next build.
Battery usage is also something I'm working on. I know Deep Sleep works fine but battery management isn't the greatest. I'll try and either fix that in the next update or the update after.
Thanks for the feedback!
Click to expand...
Click to collapse
Bluetooth is really important, so please help us solving this issue first.
But the reliability and choppiness issue is huge on my phone. Even with the ROM installed and no other app or tweak on it, it is really slow to launch a default app. Also, I'm using OpenGapps because on the link that you wrote for MindtheGapps, I cannot install it. The Play Store is there, but as soon as I launched it, a message saying that I don't have Google Play Services installed pops out. And going to recovery to reinstall it gets me on the same message. I even tried to install both ARM versions that are on the site, but with the same results. And in one instance, I just installed the ROM with no Gapps, and the same slow launching times happen, even launching the calculator app takes a few seconds.

estuardo4 said:
Bluetooth is really important, so please help us solving this issue first.
But the reliability and choppiness issue is huge on my phone. Even with the ROM installed and no other app or tweak on it, it is really slow to launch a default app. Also, I'm using OpenGapps because on the link that you wrote for MindtheGapps, I cannot install it. The Play Store is there, but as soon as I launched it, a message saying that I don't have Google Play Services installed pops out. And going to recovery to reinstall it gets me on the same message. I even tried to install both ARM versions that are on the site, but with the same results. And in one instance, I just installed the ROM with no Gapps, and the same slow launching times happen, even launching the calculator app takes a few seconds.
Click to expand...
Click to collapse
I'm using opengapps as well. I just did a copy and paste of the thread template for carbonROM when I made the thread which is why the reference to using mindthegapps is there.
I'll probably update the OP to say you should just use openGapps since those seem to work absolutely fine.
Also apologies for no update this week. University has been keeping me busy so I've been juggling around a lot of stuff. I'll look into repairing the major bugs and releasing an update as soon as possible though

tuxdude143 said:
Also apologies for no update this week. University has been keeping me busy so I've been juggling around a lot of stuff. I'll look into repairing the major bugs and releasing an update as soon as possible though
Click to expand...
Click to collapse
Take all the time you may need. As long as it's as soon as possible
I understand. I just wish more people could download and test the ROM, but I suspect Bluetooth is really needed to be working.
I'm using it as my daily driver and I can cope with the glitches, as long as my substratum themes keep working. Also, many people probably don't know this, but with Carbon OS, if you install a layer, there's no need to reboot the system to apply it.

hi guys I want to give you great news ... the automatic rotation works ... you just have to activate all the rotations from the settings :laugh:

WHEW things have been quiet. Sorry for not having posted an update in so long. University has been preventing me from really doing any solid work on this.
I'm planning on trying to make some new builds based against the new device tree, kernel etc that highwaystar is using for the new builds of LineageOS 14.1. The hope is that will fix some of the bugs currently present. I currently have no real ETA for when I'll get that build all sorted out what with being up to my neck in university work but I'll try and get it out there at some point.
Thanks for all your patience, I know how restless you must be for an update and I can understand that. Once I have some more time on my hands then I should be able to pump out a new build