[ROM][4.4.2][jubei][Beanstalk and Fenris] - Nexus 7 (2013) General

Fenris https://en.wikipedia.org/wiki/Fenrir is one evil wolf.
ooops a little to evil i think, withdrawn until i review the buzz

Not a Moderator to Tell what to do but i think this is not correct place to start ROM thread
http://forum.xda-developers.com/nexus-7-2013/development
or
http://forum.xda-developers.com/nexus-7-2013/orig-development
i maybe completely wrong too

vinumsv said:
Not a Moderator to Tell what to do but i think this is not correct place to start ROM thread
http://forum.xda-developers.com/nexus-7-2013/development
or
http://forum.xda-developers.com/nexus-7-2013/orig-development
i maybe completely wrong too
Click to expand...
Click to collapse
yep thats what i thought to, then read this at the top of the dev forum
http://forum.xda-developers.com/showthread.php?t=2380904
which basically said if not you own it do not post it there, also suggested posting it here.
Since i only really tweaked the zip of beanstalk to produce Fenris, and just added a little bash code, dont know if it counts as my work, i did not compile anything at all.
Having said that am back at my linux box in 2 days and will compile it from scratch then

Fenris V6 up

First of all, thank you for your effort around making tweaking and modding BeanStalk rom.
After, regarding where it should go, I think it "Android Development" category would fit, but I'm sure someone will confirm and move there if necessary.

Sounds great, can't wait to get home and try it out. I'm currently using PAC, but it lacks a lot of the usual PAC features. Same is for paranoid for Flo, it's almost completely pure AOSP and lacks a lot of the usual features.
Sent from my Nexus 7 using XDA Premium 4 mobile app

What kernel should I use for this - CAF or AOSP?
Sent from my Nexus 7 using XDA Premium 4 mobile app

jubei_mitsuyoshi said:
Fenris V6 up
Click to expand...
Click to collapse
I'll be happy if it just doesn't random reboot like the CM11 does. So far, only stock is solid.

jmdearras said:
I'll be happy if it just doesn't random reboot like the CM11 does. So far, only stock is solid.
Click to expand...
Click to collapse
Nope zero problems for me
V6 semed to have got lost in the air somewhere , but v7 ( pretty stable i think just doing last of the tests ) is up and very very very good
A bit of a warning here, Fenris is not like other roms, to get the best out of it either read the setup instructions with a fine tooth comb, or be VERY familiar with lucky patcher already

Fenris V8 ( what i hope is the last version ) is up, so far no big bugs

jubei_mitsuyoshi said:
Fenris V8 ( what i hope is the last version ) is up, so far no big bugs
Click to expand...
Click to collapse
V8 fails to flash. Twrp gave me a failed updater binary error (or something like that) error.
Sent from my Nexus 7 (2013)

oadam11 said:
V8 fails to flash. Twrp gave me a failed updater binary error (or something like that) error.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Ok am on it, will have a look and fix if necessary within the hour,
There is a separate problem, the new build of beanstalk i am using seems to have broken bluetooth, i have just checked on a clean unmodified beanstalk / fresh flash and def something up with the Bluetooth, since im not compiling it yet doubt can fix, am revering back to the previous release and checking its working on that, if not going on that will be changing rom base.

Just flashed my local V8 with no problems, twice to check,
So has to be a upload/download issue, can you try re-downloading and try again ?, if still issue will re-upload file.
What does the TWRP window say ? does it fail at a script line or fail at the beginning ?

jubei_mitsuyoshi said:
Just flashed my local V8 with no problems, twice to check,
So has to be a upload/download issue, can you try re-downloading and try again ?, if still issue will re-upload file.
What does the TWRP window say ? does it fail at a script line or fail at the beginning ?
Click to expand...
Click to collapse
{
"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"
}
I redownloaded and tried it again. The attached picture shows the error I am getting. I am using multirom if that makes a difference
Sent from my LG-VS980

oadam11 said:
View attachment 2641154
I redownloaded and tried it again. The attached picture shows the error I am getting. I am using multirom if that makes a difference
Sent from my LG-VS980
Click to expand...
Click to collapse
hmm yes obviously an issue when flashing as secondary rom, maybe something to do with the new " check journals gone with a script " feature, will remove it and see if that makes a difference, will call it v8.1 and do it for tonight.
Ps seems Bluetooth does work, just the options>blutooth>on/of switch is flaky, can be swiched well with the drop-down panels.
Its a small bug and do not think its reason to switch base rom.
Have checked pairing with few devices,all pair, by no means a good spread

8.1 is uploaded , can i ask what TWRP you are using ? , i dont recognise your screenshots, is it the multirom app ? I use 2.7 multirom TWRP and it does not look like that ( in fact your screens look much better )

jubei_mitsuyoshi said:
8.1 is uploaded , can i ask what TWRP you are using ? , i dont recognise your screenshots, is it the multirom app ? I use 2.7 multirom TWRP and it does not look like that ( in fact your screens look much better )
Click to expand...
Click to collapse
I'm on the latest multirom 2.7. I use a twrp theme so that's why it looks different. Thanks. I'm going to try 8.1 once its done downloading
Here is the forum to the theme that I use
http://forum.xda-developers.com/showthread.php?t=2409432
[THEME][N7.2] TWRP Holofied - Black / Dark / Light / Play / XDA / MultiROM [12/03/14]
Sent from my Nexus 7

oadam11 said:
I'm on the latest multirom 2.7. I use a twrp theme so that's why it looks different. Thanks. I'm going to try 8.1 once its done downloading
Here is the forum to the theme that I use
http://forum.xda-developers.com/showthread.php?t=2409432
[THEME][N7.2] TWRP Holofied - Black / Dark / Light / Play / XDA / MultiROM [12/03/14]
Sent from my Nexus 7
Click to expand...
Click to collapse
Ahhh thank you very very much, must say one learns something new every day on XDA

Ok found/fixed the issue with Fenris and multirom, the multirom environment is incompatible with my ext4 journal fix, hence i have made a version without my ext4 fix, its in the same folder but with a "multirom" tag, just tested and will be good.
I do a fair amount of weird kernel tweaking in the init.d , no idea if any of that is multirom complaint, certainly have not tested it in that env

V9 is up, this is final stable version, which i use every day, lead post updated.

Related

[ROMs] 4.2.2 ROM's

I have two ROM's I thought I would share. They are both 4.2.2 ROMs; one is AOKP, and the other CyanogenMod. Niether have working Bluetooth and do have most of the current 4.2.2 bugs.
If anyone is curious they can see my Github, my username is CDMoncrieff
I've uploaded the files to Dev-Host under CDMoncrieff and the files are:
cm_tenderloin.april8.zip - 152.30 MB
aokp_tenderloin.april8.zip - 133.95 MB -been told it may wipe SD contents on some Touchpads. Back-up to your PC before flashing please!
Use a file explorer to drop this file in system/bin to fix the multiple light touches bug. ts_srv - 17.84 KB
{
"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"
}
CDMoncrieff said:
I have two ROM's I thought I would share. They are both 4.2.2 ROMs; one is AOKP, and the other CyanogenMod. Niether have working Bluetooth and do have most of the current 4.2.2 bugs.
If anyone is curious they can see my Github, my username is CDMoncrieff
I am not able to post links yet (<10 posts), but I've uploaded the files to Dev-Host under CDMoncrieff and the files are:
cm_tenderloin.april8.zip
aokp_tenderloin.april8.zip
Click to expand...
Click to collapse
Thanks for the Roms. Question, which gapps should we use? Thanks again.
chicle_11 said:
Thanks for the Roms. Question, which gapps should we use? Thanks again.
Click to expand...
Click to collapse
The 4.2.2 GAPPs package
A question for you, where did you learn to build ROMs for the HP touchpad? I've been googleing how to set up a build environment on Ubuntu, which I've nearly completed but then all guides on building cm10.1 (for example) only cover supported devices of which the Touchpad isn't.... I can't find much with Google at least on Touchpad specific ROM building.
Sent from my Nexus 4 using Tapatalk 2
Nathanation064689 said:
A question for you, where did you learn to build ROMs for the HP touchpad? I've been googleing how to set up a build environment on Ubuntu, which I've nearly completed but then all guides on building cm10.1 (for example) only cover supported devices of which the Touchpad isn't.... I can't find much with Google at least on Touchpad specific ROM building.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2043285
This is hands down the best guide for setting up your build environment. Its okay to be on 13.04 as well, you might just have some unmet dependantcies you need to install. You'll likely be told you are holding broken packages and will need to meet the dependencies before you can install the other packages.
sudo apt-get install gcc
sudo apt-get install g++
After following that guide you should be set up to build.
Building for unsupported devices depends on the ROM you are trying to create. Basically you just need to follow the file paths in your local repository until you find something out of place or missing, then fix it.
You can see my githib at github.com/cdmoncrieff where you can see some of the commits I made to build for AOKP to get an idea of the process. There is also a short build-instructions repo with a few details of the process for 4.2.2. If you have any questions, which if you are going to try building, I will be glad to help
I still need more posts before links, here's another!
OK that's great I will take a look, the main problem for me at the moment is time. I'm currently using Ubuntu 12.10 I'm hoping to at least compile cm9 or cm10 to start with as they are pretty much fully operational. SGA's efforts with 4.2 and yours have inspired me to have ago. I guess the battery life is the main item that needs work in 4.2.2 and working out how to get Bluetooth working. What are your plans? Do you intend to try to improve on the current builds?
Sent from my Nexus 4 using Tapatalk 2
Where I can :good:
These are the links?
http://d-h.st/search?search_by=2&search_for=cdmoncrief
Sent from my GT-N7000 using xda app-developers app
keenan316 said:
These are the links?
http://d-h.st/search?search_by=2&search_for=cdmoncrief
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, thanks!
This should be moved to development thread. You mind if I request that it is? By the way thank you for sharing!
nickster1 said:
This should be moved to development thread. You mind if I request that it is? By the way thank you for sharing!
Click to expand...
Click to collapse
Yes, but still no takers on the DL?
I will tonight when I get a chance.
CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
That sounds good.
Wich bugs 4.2.2 has?
Unpredictable power draw
No Bluetooth
Kind of flakey WiFi
Rotated camera preview
I think that's it...
CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
I downloaded the AOSP version earlier and will be flashing tomorrow.
Do I have to wipe / factory reset, format system, etc, or can I get away with just wiping cache and wiping dalvik cache.
Thanks.
Thread moved to development, now that the OP has permissions to post in dev forums
CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
I'm sure plenty of people will download it in next few days
Will be getting it myself later tonite just to try it out
Tried it on a mate's tp and seems very good
Sent from my LT26i using xda premium
I've looked at your github and there are some useful changes in there I may move over to my rom. I just started getting phantom touches in one corner so I'll try out the ts_srv.c change. I might try the system tunings to system.prop, why did you choose those changes?
Why did you disable backuptool in tenderloin_ota_from_target_files? It is what keeps your gapps when you flash. Does it cause you some problems? I find it works just fine.
good job on the rom.
By the way, the camera driver is consuming lots of power (90mA sleep) so I reverted those three commits. The camera doesn't work but I'm down to 19 and I hope to get back to 4. (it's in my new branch c10.1, I'm still new at git so I left my old tree with camera for those who want it and a new tree with it reverted for me.)
Keep up the good work.

[MOD] TabletUI for cm10.1 - android 4.2.2 (Updated 2013-08-05)

Hi everyone,
I used this tool i found here in xda ( auto-patcher thanks to all devs in there!) to create a update.zip that brings tablet UI back!
{
"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"
}
UPDATED:
Hi, i'd said i would be posting each week or so but i had to come back to cm 10 because of bluetooth support and didn't want to post any patch if i could not test it myself first. But now that jcsullins came back with a bluetooth enabled rom (yeaaah!!) ill be posting the table ui patches for 4.2.2.
Patch for jcsullins cm-10.1-20130804-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST :
update-cm-tenderloin-20130611-tabletUI.zip to enable tablet UI flash this
restore-cm-tenderloin-20130611.zip to go back to the stock UI flash this
nice ! thanks for this
Although I haven't tested it on the Touchpad, I've tested it on several other tablets running CM10.1 and the Tabletizer app should also work if anyone is interested. However, the other tablets I work on require a special signing key, so when I used it on those tablets I signed the zip manually. I don't know how signing zips works on the Touchpad.\
Anyway, thanks for this and for the future updates, I totally agree about the layout and I think TabletUI is a much better use of space as well.
fuser-invent said:
Although I haven't tested it on the Touchpad, I've tested it on several other tablets running CM10.1 and the Tabletizer app should also work if anyone is interested. However, the other tablets I work on require a special signing key, so when I used it on those tablets I signed the zip manually. I don't know how signing zips works on the Touchpad.\
Anyway, thanks for this and for the future updates, I totally agree about the layout and I think TabletUI is a much better use of space as well.
Click to expand...
Click to collapse
I tried tabletizer first and it didnt work for me when i ran the app , so i didnt look further to try to make it work (maybe it was just a little thing) because i found the other thread and it worked fine for me.
I tried to run the update patch without any luck.
Update: it worked once I was able to download the complete copy.
Sent from my TouchPad using xda app-developers app
quick tip, if you tap the app switcher button it'll bring back the top bar if it was hidden by the app
benru89 said:
Hi everyone,
One of the most annoying things i found when i switched to cm10.1 was the new ui layout. i didnt like to lose that space on top when there is enough space on the bottom bar, i didnt like having notifications on one side and quick settings on the other . It was annoying when i wanted to set the brightness of the screen because there is no slider, and in some apps when the top bar is hidden you cannot change brightness without leaving the app. So i used this tool i found here in xda ( auto-patcher thanks to all devs in there!) to create a update.zip that brings tablet UI back!
For those who want to try it, its very easy it only takes one command to build a flashable zip. You have to put the rom in the same folder you extracted the auto-patcher and run this:
Code:
./auto_patcher cm-10.1-20130604-UNOFFICIAL-tenderloin.zip tabletUI cm
Anyways I recommend you take a look on the auto-patcher thread if you decide to download it.
And for those that do not want to get their hands dirty ill be posting an update here every week or when there will be some mayor update, so you just have to download and flash it in cwm.
This one is for the 2013-06-04 nightly:
update.zip to enable tablet UI flash this
recover.zip to go back to the stock UI flash this
Click to expand...
Click to collapse
I tried to do it on my touchpad and it says permission denied. I have set the permission and everything properly. I wonder what I am doing wrong here.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Nevermind. I got it working. Ran the GUI version on the win7 desktop and I got two files.
Sent from my TouchPad using xda app-developers app
benru89 said:
Hi everyone,
One of the most annoying things i found when i switched to cm10.1 was the new ui layout. i didnt like to lose that space on top when there is enough space on the bottom bar, i didnt like having notifications on one side and quick settings on the other . It was annoying when i wanted to set the brightness of the screen because there is no slider, and in some apps when the top bar is hidden you cannot change brightness without leaving the app. So i used this tool i found here in xda ( auto-patcher thanks to all devs in there!) to create a update.zip that brings tablet UI back!
For those who want to try it, its very easy it only takes one command to build a flashable zip. You have to put the rom in the same folder you extracted the auto-patcher and run this:
Code:
./auto_patcher cm-10.1-20130604-UNOFFICIAL-tenderloin.zip tabletUI cm
Anyways I recommend you take a look on the auto-patcher thread if you decide to download it.
And for those that do not want to get their hands dirty ill be posting an update here every week or when there will be some mayor update, so you just have to download and flash it in cwm.
This one is for the 2013-06-04 nightly:
update.zip to enable tablet UI flash this
recover.zip to go back to the stock UI flash this
Click to expand...
Click to collapse
will this work for later nightlies if I just want to flash via CWM?
slicetwo said:
will this work for later nightlies if I just want to flash via CWM?
Click to expand...
Click to collapse
I've just updated it !
benru89 said:
I've just updated it !
Click to expand...
Click to collapse
you're a beautiful person.
Having so problem install.. Error set_perm: some changes failed
E:Error in /sdcard/download/update.zip (status 7).
Can u help
Sent from my TouchPad using Tapatalk HD
tighgup said:
Having so problem install.. Error set_perm: some changes failed
E:Error in /sdcard/download/update.zip (status 7).
Can u help
Sent from my TouchPad using Tapatalk HD
Click to expand...
Click to collapse
Thats weird...check in your pc if you can open the zip file...if you can't its because that was a wrong download (its hosted on dropbox so thats possible). Try downloading it again.
benru89 said:
Thats weird...check in your pc if you can open the zip file...if you can't its because that was a wrong download (its hosted on dropbox so thats possible). Try downloading it again.
Click to expand...
Click to collapse
Install it as a normal zip, not as a update one . In CWM chose the zip file and install it, but before doing this wipe cache partition and dalvik . Happy Flashing !
yay a proper tablet UI
Anyone else notice that the Battery Percentage setting is broken when using the autopatched status bar? As in, it no longer shows a percentage unless you select Circle w/ Percentage mode... the normal Percentage mode just shows the battery bar with no percent.
I'm running the latest July 23 nightly of CM 10.1. Will this mod still work with that?
Sent from my SAMSUNG-SGH-I747
OK, for future reference, do NOT flash this mod on newer nightlies. I just tried it on the July 24 build and CM wouldn't boot past the spinning ring screen...
Sent from my SAMSUNG-SGH-I747
WMH7 said:
OK, for future reference, do NOT flash this mod on newer nightlies. I just tried it on the July 24 build and CM wouldn't boot past the spinning ring screen...
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
You have to use to AutoPatcher (linked at the beginning of the thread) to create a flashable update for your specific nightly.
Sometimes that can work for multiple versions after, but as soon as the wrong thing changes upstream, you'll have issues.
lotherius said:
You have to use to AutoPatcher (linked at the beginning of the thread) to create a flashable update for your specific nightly.
Click to expand...
Click to collapse
Interesting, when I flashed the OP's zip it said that AutoPatcher was running. I guess I'll try again...
Sent from my SAMSUNG-SGH-I747

[ROM]4.3[OFFICIAL] Android Open Kang Project JB-Mr2

{
"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"
}
Device: Oppo Find 5
» Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP
Flash ROM
Flash Google Apps (GAPPS)
Reboot
Wait 10 minutes
Reboot again
Enjoy!
» Check merged commits on AOKP's Gerrit
Official Builds <<< THERE ARE NONE!
Official Nightlies
Unofficial JB-MR2 Test Builds
And don't forget to
Flash Gapps
» AOKP Gerrit
» AOKP on Github
» SOURCE on AOKP.co
We greatly appreciate your contribution in the form of code, or PayPal donations.
» Donation options on AOKP.co
Enjoy!
for science
Rules :
XDA 's rules are simple .
respect everyone and dont go off topic .
This is a development thread .
Enjoy .
so this will be official version to replace maxwen's one?
leungclj said:
so this will be official version to replace maxwen's one?
Click to expand...
Click to collapse
Oppo find 5 will be officially supported by AOKP yes ...
Afaik maxwen does his own thing and he' s pretty good at it . I doubt anyone will replace him ..
Now lets please get back to the topic .
Is there a reason why TWRP is needed? Just curious Really happy to see official AOKP support. I know sixstringsg was interested in bringing AOKP to the Find 5, so this is super cool! Thanks again.
Sent from my Nexus 7 using Tapatalk 4
Coreym said:
Is there a reason why TWRP is needed? Just curious Really happy to see official AOKP support. I know sixstringsg was interested in bringing AOKP to the Find 5, so this is super cool! Thanks again.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
probably to avoid people complains errors when flashing, like stock recovery will often fail on custom roms
thanks !! another 4.3 rom to try !!! great to see this one
The modem has to be 4.1? or worth the 4.2? thanks
leungclj said:
so this will be official version to replace maxwen's one?
Click to expand...
Click to collapse
if you read correctly
mine is named AOKP "based"
BTW:
I am not after donations but you will find a link in my profile
Sent from my Find 5 using xda app-developers app
anders3408 said:
probably to avoid people complains errors when flashing, like stock recovery will often fail on custom roms
Click to expand...
Click to collapse
AFAIK stock recovery won't flash custom ROMs at all. But that's no secret that a custom recovery is needed. Just wondering why step 2 says to make sure your using TWRP. Will it not work with CWM?
Sent from my Find 5 using Tapatalk 4
Coreym said:
AFAIK stock recovery won't flash custom ROMs at all. But that's no secret that a custom recovery is needed. Just wondering why step 2 says to make sure your using TWRP. Will it not work with CWM?
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
its just a preference really .
Cool.
Sent from my Find 5 using Tapatalk 4
vvaleta28 said:
The modem has to be 4.1? or worth the 4.2? thanks
Click to expand...
Click to collapse
hi , not sure , probably liek the other 4.3 roms , I had updated OTA my phone prior to modding it so not sure what my baseband version was to begin with
vvaleta28 said:
The modem has to be 4.1? or worth the 4.2? thanks
Click to expand...
Click to collapse
yes else wifi is still broken afaik
Sent from my Find 5 using xda app-developers app
DAGr8 said:
hi , not sure , probably liek the other 4.3 roms , I had updated OTA my phone prior to modding it so not sure what my baseband version was to begin with
Click to expand...
Click to collapse
maxwen said:
yes else wifi is still broken afaik
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, with 4.1 the wifi works , thanks
Is it just me or is OpenGL ES 3.0 not supported?
Btw, ROM runs smooth but Launcher crashes when opening the app drawer
Xtremelyevil said:
ROM runs smooth but Launcher crashes when opening the app drawer
Click to expand...
Click to collapse
no crashes here ...
rebuilding rom with a few cherry pick , changed my mind again . should upload before we reach Sept 6th (EST)
Running 24 hrs now, and this ROM is smooth. Having a complication with a BT headset, but it may not be ROM related.
Sent from my Find 5 using Tapatalk 2
link is up

[ROM][4.3.1]Unofficial SlimBean build I9295 20140316-2010

{
"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"
}
An unofficial SlimBean build for S4 Active (I9295)
build 20140316-2010
SlimRoms: http://slimroms.net/
device makefiles and kernel originally by LeJay, modified by me to work with Slim
sources unmodified from SlimRoms github
built by me
DISCLAIMER
UNOFFICIAL build, so complain to me, not SlimRom devs
I nor SlimRom devs are responsible if something unwanted happens
I am not actively developing this, fixes and updates might or might not come and will not come fast
Credits
SlimRoms: http://slimroms.net/
LeJay for kernel and device stuff
Bugs
Recording audio: second mic not working (how to test this? )
Camera might hang. Fix: reboot phone. Apparently this is a bug with Quallcom cameras... nothing i can do about it
Google Drive FC's
You tell me
How?
grab the rom: https://drive.google.com/folderview?id=0BzJzDM42pkRvZzZlOEJxV0ZNZzQ&usp=sharing
grab gapps: http://slimroms.net/ and Downloads -> Old releases -> Addons 4.3
factory reset recommended, might need /system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
SU: make sure to enable root in Settings->Developer options->Root access
Sources for kernel, device files and roomservice.xml
https://github.com/spegelius
First !! .... for mic and hdr issues could they be fixed by merginig some things from your aosp builds !
Thanks again for a great Rom.
I am positively surprised about the camera pic quality.
Using focal app. Top
Sent from my GT-I9295 using XDA Premium 4 mobile app
Seems to work fine. Thank you.
Any issues with root though?
I came from stock rooted. Formatted and installed and not sure how to get root back
Sent from my GT-I9295 using xda app-developers app
nasaprinsloo said:
Seems to work fine. Thank you.
Any issues with root though?
I came from stock rooted. Formatted and installed and not sure how to get root back
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Install the SuperSU.zip from CWM... That's it
Sent from my GT-I9295 using XDA Premium 4 mobile app
One question.
Its probably got to do with the lcd dpi(320), i canvt use the full screen of my home screen.
Attached screenshot. Full use,
delete
delete
mythi said:
First !! .... for mic and hdr issues could they be fixed by merginig some things from your aosp builds !
Click to expand...
Click to collapse
Possibly, i haven't confirmed this bug myself, it was posted on SlimRom forums. Actually didn't even know there was two mics . But the kernel sources are the same with CM and my AOSP build so either this bug is in those roms too or it's Slim specific bug.
nasaprinsloo said:
Seems to work fine. Thank you.
Any issues with root though?
I came from stock rooted. Formatted and installed and not sure how to get root back
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
As alirey ointed out, just install SuperSu. But when i had Slim installed it did have root, so i'm not sure why you didn't have it. Did you check the setting in Settings->Development-> root access (or something like that...)? It should be set to Apps or Apps&ADB
nasaprinsloo said:
One question.
Its probably got to do with the lcd dpi(320), i canvt use the full screen of my home screen.
Attached screenshot. Full use,
Click to expand...
Click to collapse
Hmm, haven't tried Full Screen. Maybe i'll install latest build with dualboot to check some things out.
As a daily. Works great for me.
Alright, installed latest build as dualbootable rom. Some testing with camera:
- first try with HDR result was hanged camera app and Cannot connect to camera when trying to start camera app. Logcat spits out some streaming errors as mm-camera-daemon tries to connect to camera, to no avail.
- reboot and second try. HDR works out of the box . Turning HDR on and off works, however Gallery FC's when taking a pic with HDR . Some outofbounds exception in logcat, related to decodeYUV422P. Hmm, haven't seen this with AOSP, but haven't actually tested camera in AOSP very thoroughly
All in all, there's stuff to do to get Active's camera working reliably.
Oh and the latest build is uploading, built yesterday
spegelius said:
Alright, installed latest build as dualbootable rom. Some testing with camera:
- first try with HDR result was hanged camera app and Cannot connect to camera when trying to start camera app. Logcat spits out some streaming errors as mm-camera-daemon tries to connect to camera, to no avail.
- reboot and second try. HDR works out of the box . Turning HDR on and off works, however Gallery FC's when taking a pic with HDR . Some outofbounds exception in logcat, related to decodeYUV422P. Hmm, haven't seen this with AOSP, but haven't actually tested camera in AOSP very thoroughly
All in all, there's stuff to do to get Active's camera working reliably.
Oh and the latest build is uploading, built yesterday
Click to expand...
Click to collapse
Just made a dirty flash. Everything seems fine. Thanks again... :thumbup:
Can you tell me for what GalaxyS3Settings.apk is?
I have deleted it but came back with the ROM.
Sent from my GT-I9295 using XDA Premium 4 mobile app
alirey said:
Just made a dirty flash. Everything seems fine. Thanks again... :thumbup:
Can you tell me for what GalaxyS3Settings.apk is?
I have deleted it but came back with the ROM.
Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It seems to be part of msm8960-common: https://github.com/CyanogenMod/android_device_samsung_msm8960-common.
Meaning it's part of SnapDragon device stuff. I don't know what it actually does, but apparently in Cyanogenmod it adds some additional options to settings perhaps? Propably with Slim also...
does not boot it stays in boot loop
spegelius said:
It seems to be part of msm8960-common: https://github.com/CyanogenMod/android_device_samsung_msm8960-common.
Meaning it's part of SnapDragon device stuff. I don't know what it actually does, but apparently in Cyanogenmod it adds some additional options to settings perhaps? Propably with Slim also...
Click to expand...
Click to collapse
it doesnt boot it just bootloops.i followed the directions..... i would like to run this ROM.... thanks
Have you done a format?
Using i9295. Not i537
Sent from my GT-I9295 using xda app-developers app
monac66 said:
it doesnt boot it just bootloops.i followed the directions..... i would like to run this ROM.... thanks
Click to expand...
Click to collapse
As nasaprinsloo pointed aout, did you do format? Factory reset might not be enough. To be sure, format /system, /data and /cache manually (maybe dalvik-cache also, and /preload).
Also, i assume you have CWM installed?
Personally, i've had no problems with installations. When coming from some other rom, facory reset and then flash. When flashing newer version, just dirty flash and it works.
Just fyi
With normal tw my useable home screen area was extremely small. As well as the apps list could hold prob 50 apps. I liked it very much (the small size)
Using Nova launcher, back to normal full screen usage. With standard size icons.
Nice one
I´m driving the build now and works like a charm...
Just got som issie with the gapps, tried you link but it has a user/password. Got another gapp but the play store just "chews" and don´t get anyware.... Any hint?
bnume said:
I´m driving the build now and works like a charm...
Just got som issie with the gapps, tried you link but it has a user/password. Got another gapp but the play store just "chews" and don´t get anyware.... Any hint?
Click to expand...
Click to collapse
Ah ok, can't link directly to the downloads... well, got to http://slimroms.net/ and from there Downloads and add-ons...
Goodie
got it now....i´m just a rookie at this...
The image really rocks... speedy and tiny...
Only problem so far is a errormessage that says "drive" stopped working ...a couple of times...

[KERNEL] Galaxy Tab Pro 10.1[SM-T520] Cybertronic v5

Cybertronic Kernel v5 - 4/23/2014
Sync-up Kernel to 3.4.82 (from 3.4.39)
Samsung clean-up and debug removal (They leave tons of factory-only, test-only debug code on)
Config optimization
Cache read-ahead optimized
More free RAM (1760MB Stock, now 1830MB)
Compiled with latest 4.8 Android toolchain (better ARM optimizations for Cortex-A15)
Caveats:
Secure storage is disabled
Only signed Samsung kernels can have this enabled. Keys/Wifi passwords, etc. Are still stored in the secure Android key-chain,
they are just not stored in TrustZone hardware. If this is critical for you, stick with the stock Samsung kernels.
In Progress...:
- ARM HMP (This will allow all 8 cores to be online at once) Porting it in will be a challenge, since it was introduced in the
3.11 kernel branch. I'm hoping the next release from Samsung bumps up the version, so it will be easier. I'll work on it in
in the meantime though.
- Merge-in ADF from Android mainline.
- Merge in anything neat from S5
Install TWRP Recovery first:
http://goo.im/devs/OpenRecovery/picassowifi
Download and install in TWRP Recovery, or use Flashify:
MOD EDIT: Link Removed as per no kernel source as per XDA Rules, and no reply from Author of said kernel.
[RESERVED]
Works well so far. Features list will be nice
Dont want to look at purely benchmarks but seems fluid.
{
"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"
}
Sent from my SM-T520 using Tapatalk
Nice! Is there a chance to get a kernel for T320 too?
Ill be more than happy to do testing on my SM-T520,
Cybertronicz said:
I've got a kernel I've been working on for the SM-T520.
Just looking for testers at the moment before releasing here publicly.
If interested in testing, PM me for link.
Click to expand...
Click to collapse
And what kind of kernel?
I think many of us would like more info before we risk bricking our device...
Since you give us NO information at all, We have NO clue what we are installing here,
how do we know what to expect, what the chances are,... ?
.:GraveD:. said:
And what kind of kernel?
I think many of us would like more info before we risk bricking our device...
Since you give us NO information at all, We have NO clue what we are installing here,
how do we know what to expect, what the chances are,... ?
Click to expand...
Click to collapse
You'll never brick your device from a kernel. It doesn't overwrite the bootloader or recovery. So you can always go back to stock, even if the kernel doesn't boot.
Anyhow.... I'm only looking for testers, who have experience. This isn't a public kernel yet, which is why the limited info. So please, calm down.
People have had good results testing so far, so I'll be releasing full details and the public file soon.
Thanks
Cybertronicz said:
You'll never brick your device from a kernel. It doesn't overwrite the bootloader or recovery. So you can always go back to stock, even if the kernel doesn't boot.
Anyhow.... I'm only looking for testers, who have experience. This isn't a public kernel yet, which is why the limited info. So please, calm down.
People have had good results testing so far, so I'll be releasing full details and the public file soon.
Thanks
Click to expand...
Click to collapse
No worries I'm not building up a rage or something like that
It was meant as a figure of speech since we now nothing
I just think it might attract more testers if we know more about what we are testing.
Is it optimized in general or is it meant for speed(oc'ing) or adds it extra functionalities to the kernel? something like that.
Anyway, I'm looking forward to your official release, and thank you for your time and effort you put into it for us Tab PRO users :good:
Does it mean we can also expect some roms for t520
i must say i have had quite the share of flashing, reflashing, and modifyting my however limited selection of android devices. Never bricked and item yet. I would love to test your kernel and give it my honest opinion.
Since its a testing thing, feel free to PM me deetails
Would love to try this, but how to get TWRP on SM-T520?
Found these recovery images for (I guess) our device, how to install these? Odin? http://goo.im/devs/OpenRecovery/picassowifi
Edit: I can confirm that flashing TWRP from rooted SM-T520 works with Flashify. Flashify finds and downloads correct TWRP2.7.0.1.
TheEvilVirus said:
Would love to try this, but how to get TWRP on SM-T520?
Found these recovery images for (I guess) our device, how to install these? Odin? http://goo.im/devs/OpenRecovery/picassowifi
Edit: I can confirm that flashing TWRP from rooted SM-T520 works with Flashify. Flashify finds and downloads correct TWRP2.7.0.1.
Click to expand...
Click to collapse
Thanks for that, I'll add a note in the OP about where to grab TWRP.
This should be moved to the development section. May get lost here.
Sent from my SM-T520 using Tapatalk
Annihlist said:
This should be moved to the development section. May get lost here.
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
I had it there originally...but a mod moved it here *shrug*
Cybertronicz said:
I had it there originally...but a mod moved it here *shrug*
Click to expand...
Click to collapse
But now you have a link with a kernel. Before you didn't hehe [emoji6]
Sent from my Nexus 5 using Tapatalk
Really considering flashing this, just a question though, where can I find the stock kernel to be able to go back if I wanted to?
Sent from my SM-T520 using Tapatalk
Cybertronicz said:
Thanks for that, I'll add a note in the OP about where to grab TWRP.
Click to expand...
Click to collapse
Better mention Flashify, just the img doesn't show how to flash.
salemsayed said:
Really considering flashing this, just a question though, where can I find the stock kernel to be able to go back if I wanted
Click to expand...
Click to collapse
You need TWRP first, with which you can make a backup of System to preserve the current kernel.
Running with the kernel now. Seems to be in order, but cannot tell of any advantages that are noticable.
Just flashed it, can't really notice much difference, but will give it some time and report back
Sent from my HTC One using Tapatalk
Since I've flashed the kernel (and then flashed stock again) and no thumbnails or pics are loading in most apps (namely Twitter, RedditSync) anyone faced that befot
Sent from my SM-T520 using Tapatalk
I've flashed the kernel. Now getting crash on launch camera (T520XXUAND1).

Categories

Resources