THIS IS NO LONGER BEING UPDATED
This was just about a direct copy of the ROM here I created due to the dev including opengapps in his builds: http://forum.xda-developers.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008
They are no longer doing that, so I am focusing on contributing to that. The v0.6 build there is equivalent and a bit better than the v0.6.1 build here. Just use their's. (Leaving the links here for now, but really don't use them. )
Full credit to @DevSwift1 for all his work on this thus far. (and the other contributors listed below). Seriously, the work they have done is a thing of beauty and I'm only doing this out of necessity of doing the right thing. (I'd rather not be, but I said I would and it may be fun.)
What works:
Audio
Brightness
GPU Acceleration
Bluetooth
Wifi
GPS
NFC
Location services
Camera and video recording
Video playback
MTP
Sensors
Bugs:
- very poor 1080p video recording quality
- Google seems to think you are using a 2012 N7. I pulled part of the fix for that since it was only part and broke the build. It should be worked out next build. (or, the next build)
You can dirty flash, but you may need to uninstall and re-install any Google Apps you installed from the Play Store.
Change Log
V0.6.1
- Uses kernel that is not vulnerable to CVE-2016-2059. (@zaclimon's with @DevSwift1's patches to compile it on GCC 4.9. The stock N7 kernel was never vulnerable to that CVE and neither was that one which isn't heavily modified from it.)
V0.6
- Updated to Android-7.0.0_r6, NRD90U, Sept 6, 2016 Security Patch. (I think r4 was actually the security patch. Not sure if there is more in r6.)
- Note that this is missing the fix for CVE-2016-2059 which was part of the Sept Security Update, but resides in the kernel which isn't part of the AOSP build. I'm fixing that and will have an updated ROM or flashable kernel soon. (Hopefully. Building the kernel is new to me)
V0.5.1
- Fork of DevSwift1's V0.5 with Gapps removed.
- Location Services works with wifi
Sources:
https://github.com/nbehary/manifest
Download:
v0.6.1
V0.6
Very Unsupported, experimental Download for Deb
This builds correctly from my fork of Devswift1's stuff which included Deb. I have no idea if it works.
v0.6.1 (Just the new Kernel for CVE-2016-2059)
V0.X (it should be about v0.6 if it works. Same sources except the parts that are different between the devices.)
Get Gapps from here: (The Micro Edition is the largest that will install due to size constraints on the System partition.)
http://opengapps.org/
contributors:
DevSwift1
zaclimon
parrotgeek1
nbehary said:
Get Gapps from here: (I recommend the nano package. It works. There are issues with them being too large.)
http://opengapps.org/
Click to expand...
Click to collapse
I was able to get micro Gapps installed with about 90m free space using the original ROM..(Will that cause issues ?? ) . Actually downloaded minigapps ,but created a gapps-config to install micro . I noticed that without Google search being a system app ,it gets killed quite quickly and takes time to load .That seems to have gone
Sent from my Lenovo X3a40 using Tapatalk
vkk178 said:
I was able to get micro Gapps installed with about 90m free space using the original ROM..(Will that cause issues ?? ) . Actually downloaded minigapps ,but created a gapps-config to install micro . I noticed that without Google search being a system app ,it gets killed quite quickly and takes time to load .That seems to have gone
Sent from my Lenovo X3a40 using Tapatalk
Click to expand...
Click to collapse
Doing that should be fine I'd think. The only issue is running out of space and as long as you aren't doing that there shouldn't be issues. (I only recommend nano since that is what I have been using and it worked for me so far.)
Unless the ROM itself gets 90mb bigger in future updates, micro should always fit. Technically, nothing should be writing to /system after install since it's usually locked anyways. Any free space in that partition just sits idle, unused.
Any custom kernels works on it? Because stock is garbage. I saw nexus 5 reports of 6.0 versions working on 7.0
- There are reports of location not working without a GPS lock, for good reason. Play Services wasn't listed as a location provider.....common thing. I think I fixed it maybe, but in a effort to release this quickly, I haven't tested much. Please let me know if you still have issues.
Click to expand...
Click to collapse
You can mark this as fixed @nbehary
Thanks to you and to @DevSwift1 this has been posible thanks to him and i encourage him to continue working on this port, it's amazing so far and there are many users out there that thank you for your hard work and for giving this rom to the community. Thanks!
Also thanks to the rest of developers.
Beautiful widgets now locates correctly, and so many other apps like Waze or Meteogalicia (local weather apps) Thank you.
{
"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 get this when flashing. Afterwards attempting to flash gapps indicates that I'm still on Android 6.0.1.
Never mind. Just had to boot into the system and flash gapps afterwards.
I've been following all of these 7.0 ROM threads since the beginning. It looks like enough fixes have been done to this rom (thanks to the work of ALL the devs involved) for me to finally install it. Great job everyone!
DISCLAIMER FOR THE REST OF THE POST: Not for noobs or the faint of heart
I just dirty flashed this right over the last official MM and full device encryption enabled. For the most part things went smoothly. The only thing (and it's quite a lot for me) I had to do was uninstall and re-install, through the Play Store, just about everything from Google. The only app that didn't crash was Play Games - almost anything else with a Google account crashed, including MightyText (I originally suspected this was because I used nano GApps, which removed most GApps from /system - but YouTube Creator Studio and MightyText debunk that theory). After doing this everything seems to be running smoothly, but I'll continue to monitor battery usage. AOSP Calendar and Contacts have been disabled, in favor of the Google versions.
The biggest reason I wanted N was so I could use Night Mode and get rid of Twilight. The option is still baked into AOSP even though it won't appear in the Quick Settings shade. Download Night Mode Enabler from Play Store and the option returns.
Clean flashed 0.5.1, immediately rebooted back into recovery and flashed OpenGapps Pico and SuperSU 2.78 while wiping Dalvik and Cache between each step.
Everything works perfectly including the restoring of my Titanium app backups.
Thanks for supporting this device!
binglejellsx2 said:
The biggest reason I wanted N was so I could use Night Mode and get rid of Twilight.
Click to expand...
Click to collapse
Sorry for being off-topic, but Twilight is really bad compared to Chainfire's CF.lumen. Twilight adds a kind of overlay, while CF.lumen does it with root and a driver, which makes the screen not look washed out or blurry like Twilight. It's free, too. Otherwise there's the live display one in every CyanogenMod based rom.
FingerMove said:
Sorry for being off-topic, but Twilight is really bad compared to Chainfire's CF.lumen. Twilight adds a kind of overlay, while CF.lumen does it with root and a driver, which makes the screen not look washed out or blurry like Twilight. It's free, too. Otherwise there's the live display one in every CyanogenMod based rom.
Click to expand...
Click to collapse
Thanks, but now that Im on Nougat, I have a native solution available. The reason I used Twilight is because I don't root anymore. I'm aware of other solutions, but these days I'm looking for the simple stuff.
This ROM is exactly what I was looking for.
Can I skip tracks with volume keys?
Any get system ui tuner working?
Sent from my Nexus 7 using Tapatalk
dadymon53 said:
Any get system ui tuner working?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes. Just help the settings wheel down for a few seconds, nothing too crazy. Just use it to display battery percentage
V0.6 is up on the main page. It just merges in the Sept Security Update.
Extreemator said:
Any custom kernels works on it? Because stock is garbage. I saw nexus 5 reports of 6.0 versions working on 7.0
Click to expand...
Click to collapse
Going to say likely not. I just tried ElementalX, with all default settings, and it boots to recovery. There may be ones that will (in theory there can be, this uses the stock 6.0 kernel far as I can tell).
It really is in the kernel dev's wheelhouse to fix things for a new Android release. I totally don't want to get into that world. Did enough messing around in the Linux Kernel in the 90's.
That said, if there are things on the AOSP side I can do to help things work, I can look into that.
nbehary said:
Going to say likely not. I just tried ElementalX, with all default settings, and it boots to recovery. There may be ones that will (in theory there can be, this uses the stock 6.0 kernel far as I can tell).
It really is in the kernel dev's wheelhouse to fix things for a new Android release. I totally don't want to get into that world. Did enough messing around in the Linux Kernel in the 90's.
That said, if there are things on the AOSP side I can do to help things work, I can look into that.
Click to expand...
Click to collapse
So it boots to OS with elementalX? Or boots only to recovery?
Glitch kernel has a version that is compatible, but I have not used it yet
Extreemator said:
So it boots to OS with elementalX? Or boots only to recovery?
Click to expand...
Click to collapse
It boots to recovery. I think it got as far as showing the logo for a split second before rebooting into recovery. (I also was wrong about this being stock maybe. It was compiled too recently, and not by Google. Not sure where it came from, since it is just a Binary in the repos. Could still be a very slightly modified, if at all, 6.0.1 stock.)
Related
This is ice cream sandwich for the Dream/Sapphire. Yes, you read that right. Android 4.0, Ice Cream Sandwich. We currently have cm9 and AOKP mostly working. AOSP is next
What works:
It boots
Touchscreen
Wifi
Mobile data
Audio
sdcard
Bluetooth (maybe. It turns on. I don't have devices to test with)
What doesn't:
Camera
Hardware acceleration
probably everything else, tell us
info:
Android 4.0.4
latest cm9 source as of 09 Aug 2013
Latest aokp code as of 6 of June 2012
Downloads:
Cm9:
Alpha3 - https://dl.dropboxusercontent.com/u/19978192/cm-9-20130802-UNOFFICIAL-dream_sapphire.zip
Alpha2.2 - http://dl.dropbox.com/u/19978192/android/update-cm-9.0.0-RC0-dream_sapphire-alpha2.2.zip
Alpha2 - http://db.tt/ejZqOHDX
alpha1.1 - http://uniteddev.com/wordpress/file...0-RC0-dream_sapphire-UNOFFICIAL- alpha1.1.zip
alpha1 - http://uniteddev.com/wordpress/file....0.0-RC0-dream_sapphire-UNOFFICIAL-alpha1.zip
alpha0 - http://uniteddev.com/wordpress/files/update-cm-9.0.0-RC0-dream_sapphire-UNOFFICIAL-signed.zip
Aokp:
Alpha2 - http://db.tt/p2lQtue2
Alpha1 - skipped
Alpha0 - http://db.tt/jErGK56g
kernel -
ezterry's kernel + ics patches and some performance tweaks (enabled 710mhz overclock and other things) http://www.mediafire.com/?py8asp6ab109dyl
ezterry's ezgb 1.5.2 http://sandbox.devnull.name/android/ezgb-kernel/ezgb-2636-v1.5.2_S.zip
cmtd files
http://www.mediafire.com/?amh4qn763gi339r
http://www.mediafire.com/?vw51n1ctl8j1p4t
http://uniteddev.com/wordpress/files/roms/cm9/mtdpartmap.txt
Note: the rom zips are not signed. Flash with clockworkmod, or sign yourself. Once this becomes more usable, I will start signing them.
very slim gapps http://www.mediafire.com/?o94hh30vh0q1oy7 (there are here for testing purposes. contains copyrighted google code that I am not really allowed to distribute. use at your own risk!)
possible fix for camera:
http://www.mediafire.com/?smfhlv2xon1e45z
flashing instructions:
you need to use custom mtd. I used 140 for /system and 20 for /cache (rom currently requires a /cache partitoin. will be fixed in a later update)
1. download all needed files and place them on your sdcard. mtdpartmap.txt needs to be at the root of it
2. flash recovery patch.
3. wipe system, data, and cache
4. reboot into recovery.
5. flash rom and kernel
6. Flash gapps if desired
7. flash boot patch
8. reboot into rom
9. wait.
10. enjoy the awesome
To use data, you need to put in your apn settings. Google to find these.
Thanks to:
Google - android
CyanogenMod team - the awesome rom
Aokp team - aokp
Ezterry and AndDiSa - kernel for ics
Infinimint and the united dev team - hosting and support
My girlfriend - for loving me even though I worked almost all day on this.
Pictures (screenshots later)
{
"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"
}
Sorry for the blurry pics. Used my other phone running cm9 with a partially working cam
Roadmap:
Slim down (in progress)
Mess with hw acceleration and camera (maybe never) - this will be alpha3/beta1 if it happens
Port AOSP
Changelog:
Alpha2.2: update to latest code. good cm9 release.
Alpha2.1: not released
Alpha2: fixed audio
Alpha1.1: small fixes (keyboard, other stuff) cm9 only bugfix release
Alpha1: fixed wifi, sdcard, and home button (skiped in aokp)
Alpha0: initial public release.
If you want to build yourself (please do, we need more people fixing stuff), the repo init command will look like this:
Code:
$ repo init -u https://github.com/UnitedDev/android.git -b ics
Note: rules on using this rom for other projects
Most of android is under the apache2 license. just don't violate that and we're good.
more specific rules: source is on my github, do whatever you want within the terms of the licences. make your own rom, use it to port other devices, release a rom that is exactly the same with a new name and a shiny theme, I don't care as long as you are building from source.
If you use prebuilt anything from releases of this rom, please be nice and send me a pm asking for permission. this is supposed to be an open community, but i hate seeing 20+ cm7 roms with nothing different except name and bundled apps. If you don't ask, and you havent made something different enough from this rom to be worth having its own thread, it may or may not get reported.
First
cm9 ! i will use now !
thanks !
Wow....speechless...
Sent from my HTC Dream using Tapatalk
OK my mind is officially blown for the day. I am completely amazed. Im gonna try this ASAP.
forgot to post kernel in the op. fixed
tvall said:
forgot to post kernel in the op. fixed
Click to expand...
Click to collapse
OK good stuff. this is probably why it wouldnt boot for me (no kernel). Downloading and testing now
Don't forget to use CustomMTD with an mtdpartmap.txt containing:
Code:
mtd 140 40
CM9 on MT3G:
Mind = Blown
Posted pictures in post 2. Enjoy
If you look at them carefully, you can see the box thos was built on. And you can see my girlfriend's leg
Tvall....amazing ---- cm9 on the dream! Don't care if this isn't fully working I'm super impressed to see another ics rom for the g1. Who would have thought! Keep it up! Will download when I get to a computer
Sent from my HTC Vision using xda premium
Can anyone confirm the status of wifi and data? I'd test wifi, but I can't find my girlfriend's phone and she is asleep...
I don't want to put water into the wine, but ... The status of the ROM is more or less in the same state as I had my ICS some month ago. (@Tvall: you should have a look at my repo, if you didn't do that already.) Wifi / Bluetooth should work without problems, at least at that time I had it working. The biggest problem (and the most important reason why I suspended the wok on it): to low memory on the G1. Startup of services from time to time failed even without any additionals apps installed.
Probably on the MyTouch it will run better, but I do not expect, that it will run decently on the G1, but I might be wrong ...
AndDiSa said:
I don't want to put water into the wine, but ... The status of the ROM is more or less in the same state as I had my ICS some month ago. (@Tvall: you should have a look at my repo, if you didn't do that already.) Wifi / Bluetooth should work without problems, at least at that time I had it working. The biggest problem (and the most important reason why I suspended the wok on it): to low memory on the G1. Startup of services from time to time failed even without any additionals apps installed.
Probably on the MyTouch it will run better, but I do not expect, that it will run decently on the G1, but I might be wrong ...
Click to expand...
Click to collapse
It runs decently (apps dont close much) on my mytouch, which is why I'm working on it. My plan is to get cm9 stable enough, then work on an aosp rom. That should be a little lighter.
Has anybody gotten this to run on a g1 yet. I managed to install, but it went crazy. I started doing a force close loop. By that i mean that it booted started then said trebuche has stopped working. I press ok then com.android.phone stopped working. i press ok then trebuche has stopped ... and so on. I followed the install to the letter a few times but i couldn't get it to run.
Nice work! Have you tried the EGL files from here: http://forum.xda-developers.com/showthread.php?t=1526920 ? Hero has same gpu (adreno 130) as dream/sapphire so it *should* work Not sure about kernel however
e334 said:
Nice work! Have you tried the EGL files from here: http://forum.xda-developers.com/showthread.php?t=1526920 ? Hero has same gpu (adreno 130) as dream/sapphire so it *should* work Not sure about kernel however
Click to expand...
Click to collapse
Not yet, thanks for the link! If that works, I'll release another alpha as soon as I fix the home button..
alex_camacho said:
Has anybody gotten this to run on a g1 yet. I managed to install, but it went crazy. I started doing a force close loop. By that i mean that it booted started then said trebuche has stopped working. I press ok then com.android.phone stopped working. i press ok then trebuche has stopped ... and so on. I followed the install to the letter a few times but i couldn't get it to run.
Click to expand...
Click to collapse
I have a mytouch 3g 1.2. It has more ram. So... if it works for me it might or might not work on a regular 32b device
Oh my...now this is impressive. I'm really interested how this turns out. Best of luck!
I told you not to get me in that picture...
I can't wait to do more testing. (My boyfriend is amazing! He's currently working on getting the wifi to work)
Sent from my Dream/Sapphire using Tapatalk 2
As a usual disclaimer : THIS CAN KILL YOUR PHONE AND PERHAPS EVEN YOURSELF AND THE ENTIRE UNIVERSE
{
"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"
}
P A C ALL IN 1
DESCRIPTION
The struggle to find the rom you need is over. Some people like CyanogenMod 10, Some prefer AOKP, Some like the advantages of Paranoid Android
To cure your rom hunt we have come up with the P A C man Rom.
PACman is a unique rom.
We have picked the best features from CM10, Aokp and PA and combined them in a single rom so you get the experience you deserve
To enjoy the features of every available project without the hassle of flashing regularly.
The Rom is rock stable for an average user but keep in mind the Rom is in WIP stage so expect some minor hickups but we are trying our best to resolve these issues
DOWNLOAD
(updated on 09/27/2013)
Download beta 4.2.2 version modded by carlos (use approriate 10.1 gapps from h1n1
Add-On :
To add Paranoid settings, please flash this zip
see post #3 for explanations
CHANGELOG
[*]27/09/2013 - update with h1n1's work
[*]09/01/2013 - Battery stats works (need feedback on accuracy) - New bootanimation
[*]08/01/2013 - New build including governors and HW rendering (thanks Razielwolfy)
the release includes a kernel with new governors and has been supercharged (v6)
[*]07/01/2013 - Initial release (in OT-995 thread)
YOUR ATTENTION
You will not send Private Message for noobish questions
You will READ before asking
Feedbacks (positive or negative) must include the version you are using
NEVER ASK FOR ETA (especially by PM)
Donations are accepted and would be used to buy a dedicated phone for dev
STATUS - not sure if it's up-to-date
[+]
Boots
Wifi
bluetooth transfer
photo/camera
HW encoding and decoding
Paranoid android settings
charging
USB Mount (desinstall all alcatel drivers and one touch craps)
FM Radio (with spirit free app)
battery stats
[-]
amount of data used is not available in the settings
bluetooth audio (sound goes out the headset but is awful)
compass/magnetometer
hdmi (image goes out but is distorded)
[not tested]
tethering
profiles
SOURCES
http://forum.xda-developers.com/showthread.php?t=1731574
https://github.com/ius/android_device_alcatel_cocktail
https://bitbucket.org/bagyusz/android_device_alcatel_cocktail
https://github.com/ius/alcatel_cocktail_kernel
https://code.google.com/p/ot995-cyanogenmod/wiki/Installation
Click to expand...
Click to collapse
THANKS TO
szl.kiev for sources of PAC rom
bagyusz
Cyanogenmod Team
Paranoid team
AOKP team
iuss
Razielwolfy
TioCareca
fonix232
all testers
Click to expand...
Click to collapse
INSTALL
Use h1n1 CM10's recovery, check their thread
wipe all
install the zip on sdcard : this rom, then install gapps (see my recommendations below)
wipe again (in case of ..)
power off
reboot
Click to expand...
Click to collapse
NOTES
- Gapps
Google let the source code available, but the google apps (google play, gmail, etc) must not be included in the rom. In order to really use your device, you must add them by flashing them.
Three possibility :
1) Multipack v3, allows to add 4.1 apps, but also to specify your gps region, change the launcher, the font etc.. flash it in the recovery, and use the touch menu from AROMA
2) 4.1.2 gapps : the complete and official gapps (85 Mo)
3) Minimal 4.1.2 gapps : the minimal version (11Mo)
4) use h1n1's gapps for CM10
- Paranoid add-on :
It adds the paranoid settings, with the possibility to specify plenty of settings per app, like the type of display (tablet/phone) the dpi etc.. It is really a great addition.
It is not included by default in the rom as molesarecoming and D4rKn3sSyS, the PA devs have asked not to implement their work in other ROM.
I would have continue to develop only PA if it was still maintained, but the Paranoid team split, with a new branch created AOSPA, which is not available and only developed on nexus. The old branch with CM stuff is not updated.
If the zip does not add, you can unzip it, take the apk and put it in /system/app, and chmod it 644.
That's why i took the decision to put the add-on, in order to benefit from these functions. But the members that deserves your gratitude are molesarecoming and D4rKn3sSyS.
- Backup and restore in recovery :
To make a working backup, please select the tar format in the backup menu of CWM 6.x.x. recovery. This one works well.
Really nice work. :good:
Nice Work BEN
And m tested latest miui rom and
battery stats are available on miui u must look maybe help u
and here s some ss mayybe take them thread http://forum.xda-developers.com/showpost.php?p=36220508&postcount=3218
HoScHaKaL said:
Nice Work BEN
And m tested latest miui rom and
battery stats are available on miui u must look maybe help u
Click to expand...
Click to collapse
strange, Razielwolfy told me that it was not working ..
this rom is very great but it seem to be lagging in front of CM10
with the same app installed i have 59 mb free ram with PAC and i have around of 100mb free with cm10
i've added some tweaks by hand on the last build, and they might not be so great, in addiiton of V6-supercharger
otherwise, just go back to the previous build, with the mods
BENETNATH said:
strange, Razielwolfy told me that it was not working ..
Click to expand...
Click to collapse
i ll give u ss next time it s working on me ı ve s50 devices and ı got update vio otu TR ICS 4.0.4
moomoon03 said:
this rom is very great but it seem to be lagging in front of CM10
with the same app installed i have 59 mb free ram with PAC and i have around of 100mb free with cm10
Click to expand...
Click to collapse
Do remember that the free amount of ram you still have has nothing to do with how fast your phone is this is a common mistake people make!
The apps that stay in your RAM are staying there until you need RAM for another app and your device will automatically clear some idle apps to make space for the other app..
Then what is so great about this?
Well if you launch a app again which was still in the RAM memory it starts a lot faster. So basicly its pretty health for a device to be completely out of RAM :highfive:
For people who are interested in more read this article
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
(note that Android is based on linux for those who didn't know)
i know that but in the reality this rom is less reactive!
i have tried the previous version and it was the same problem
less reactive than what ? previous version with or without mods.. be constructive please
it is less reactuve than cm10 but it is the same as the previous build
i am sad because i prefer the look of pac like in menu or web browser
i can notice also strange scrolling in all JB roms
moomoon03 said:
it is less reactuve than cm10 but it is the same as the previous build
i am sad because i prefer the look of pac like in menu or web browser
i can notice also strange scrolling in all JB roms
Click to expand...
Click to collapse
Hmmm.... I'm about to flash the latest PAC build, but I'm using the first one now. I have to say that it's very smooth and fast and responsive on my phone. Matter of fact that's one thing that been a fact since the very first rom build Ben put out. Since just about all that have tried this rom don't have the same experience as you, maybe something happening during the flashing process or maybe even something running in the background is causing your glitches. Just a thought.
Sent from my OT-995 using xda premium
tumaini418 said:
Hmmm.... I'm about to flash the latest PAC build, but I'm using the first one now. I have to say that it's very smooth and fast and responsive on my phone. Matter of fact that's one thing that been a fact since the very first rom build Ben put out. Since just about all that have tried this rom don't have the same experience as you, maybe something happening during the flashing process or maybe even something running in the background is causing your glitches. Just a thought.
Sent from my OT-995 using xda premium
Click to expand...
Click to collapse
i t s not the first time i flashed rom but i noticed on pac rom the running process parameter takes 40mb of ram
Weird I had the opposite feeling with those roms.
CM10 felt very sluggish for me and looked like it had trouble running on my phone
PAC rom however runs smooth like a ICS rom would run its the best and fastest JB rom I have seen till now (although I haven't tried MIUI yet)
here s antutu score
and ı cant make setting ui to 200 dpi m changed it to phone ui but ı cant set dpi bigger i want 200 dpi on pa setting its possible but on pac ıt s not possible :/
look here
moomoon03 said:
i t s not the first time i flashed rom but i noticed on pac rom the running process parameter takes 40mb of ram
Click to expand...
Click to collapse
Well all I can say is I'm using the Jan 8th release now. Smooth as glass. Extremely responsive. No lag,no stutter, no nothing to hinder navigating the rom. I have missed a few pages, so I'll ask if anyone else is reporting this issue.
Sent from my OT-995 using xda premium
i use the first release of pac rom for ot995, so far no problems. i do experience some lag, but it might be of apps installed (like viber, facebook and other apps that stay active even if screen is locked). i downloaded the today release, and i'm about to try it (saw v6 supercharge in changelog )
ı ll take paranoid prefences apk and take system now m changing setting dpi hehe
With a few requests from tab-plus owners, I started building ROMs for tab-plus. I don't want to ignor anyone so built for all models.
I can't reply all post because I don't have the tab to test. However, I tried to answer all PMs as detail as possible. Once a while in these few months, I received a few hostile PMs, calling me names, etc. I might have asked too many questions. I don't have the ability to guess what model or which ROM if they are not mentioned. I don't know why asking for a screen shot, a video or details would be too much for someone.
Anyway, I over estimated myself to support a device I don't have. I have spent too much resource and I don't think I can do this any more. Bye.
*** Lollipop is out so my development for Kitkat is done. As a closure, I included all tab-plus models in this final build***
for some unknown reason, download provider is missing in the final build
Patch didn't work and I need to rebuild. Hoping this is really the final.
{
"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 another aftermarket ROM having its unique features. I have been playing with Carbon for sometime. It has some unique features like CarbonFibers and ActiveDisplay. Another cool ROM worth trying. Cheers!
goo.im is up again!
Release Note:
2014/8/2
Just finished the GPU performance settings. In case some tabs might have lower tolerance, I lowered the GPU default min. and max. freq.
I also enable the Carbon performance tool. You can flash kernel and recovery from there. zRAM can only be enabled by TricksterMod. Old methods doesn't work on Kitkat. This build included all Carbon features. Enjoy!
2014/7/2
With help from @zombiezoom, the Carbon 4.4.4 build proved working on Tab plus. I do a sync before building for 7.7. It was a bad move. Carbon has an incomplete commit which cause me 12 hrs. to make the build pass.
On request from the local friends, link for Alipay is added in Donation.
2014/4/19
There are a few bugs in CarbonRom for our tab since day one. SystemUI crash, Some pages in CarbonFibers crash...etc. I finally fixed them this weekend! So it's time for me to share. It include all the fixes in my Kitkat roms.
Change log: :victory:
Code:
Official Carbon [URL="https://carbon-rom.com/changes/"]Change log[/URL]
[COLOR="Blue"]2014/8/2[/COLOR]
- Latest CarbonROM source
- Android 4.4.4r2 KTU84Q
- kernel update for GPU O/C and zRAM
- add GPU settings in performance
- include performance tools
- zRAM support
- major Bluetooth update from Bluez
[COLOR="Blue"]2014/7/2[/COLOR]
- Latest CarbonROM source
- Android 4.4.4r1 KTU84P
[COLOR="Blue"]2014/4/19[/COLOR]
- Latest CarbonROM source
- Android 4.4.2r2 KVT49L
- Fix crash in SystemUI
- Fix crash in CarbonAbout
- Fix crash in CarbonFibers
- Fix in QuickSettings (mess up after change QSTile position)
Know issues:
Only minor issues:
1. Lock screen stay at landscape with Rotaion Lock is ON
2. A few apks (eg. Browser) with distort screen after rotation. (Can be recovered by selecting from recent menu again)
Downloads: :highfive:
goo.im: http://goo.im/devs/daniel_hk/rom/carbon
AFH: http://www.androidfilehost.com/?w=files&flid=13972
mirror: http://pan.baidu.com/s/1GjnUQ#dir/path=/carbon
Recovery requirement
** CWM6, TWRP 2.3.1 or above is OK.
Most of the 4.4 Roms require the latest reovery with file_contexts and set_metadata support.I have patch the update-binary to work with old recoveries.
** See my thread to patch any gapps or ROMs with set_metadata fail **
Source:
kernel & device trees will update the new kernel soon after testing
github: https://github.com/danielhk?tab=repositories
Credits: :good:
** The CarbonROM team!
** All those who donate to me. Giving me the resources to upgrade my PC and accessories!
** All those who help our cool tab's developments!
Donations:
I just cannot believe it man! You are unstoppable and I REALLY LOVE YOU
Thank you so much for this ROM..downloading it right now and I think it's gonna be better than OmniROM in terms of features :good:
Thanks daniel, how to access the old internal storage, cause the path changes to "storage/emulated" (whatever i forgot)
I cannot see my data, cause the old internal storage in "mnt/shell/sdcard"
so I must manually move all data to new path internal storage ?
ravhi1044 said:
Thanks daniel, how to access the old internal storage, cause the path changes to "storage/emulated" (whatever i forgot)
I cannot see my data, cause the old internal storage in "mnt/shell/sdcard"
so I must manually move all data to new path internal storage ?
Click to expand...
Click to collapse
Of course not. I don't have a Tab Plus to test but there are links to /sdcard, /storage/sdcard0, etc.
I don't know why you say you can't access. Apks will find the data themselves. You have to be more specific. Which apks, what do you want to do, etc.
At least you have to tell which model you have in order to get helps from others.
Good luck!
Sent from my Nexus 7 using Tapatalk
Oops, system UI crashed and I can't access anything other than settings via quick menu.
I have a p6200 WiFi+3G and now I am back to the latest build of OMNIRom
I already did 3 wipes but same problem exists
zombiezoom said:
Oops, system UI crashed and I can't access anything other than settings via quick menu.
I have a p6200 WiFi+3G and now I am back to the latest build of OMNIRom
I already did 3 wipes but same problem exists
Click to expand...
Click to collapse
Can you or anyone provide a logcat?
Thanks.
Sent from my Nexus 4 using Tapatalk
daniel_hk said:
Can you or anyone provide a logcat?
Thanks.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Done.
Messed my tab
This ROM did a really big mess on my tab. Been flashing roms since gingerbread, but this rom is a big mess.now my p6200 have a really screwed file system. i don't recommend using this.
phangs23 said:
This ROM did a really big mess on my tab. Been flashing roms since gingerbread, but this rom is a big mess.now my p6200 have a really screwed file system. i don't recommend using this.
Click to expand...
Click to collapse
I don't know what you meant by messing your file system?
I think you meant the content of the internal sdcard was moved to the folder 0. This is the way android handle multi user since 4.2. Your experience might only upto 4.1.2. There were similar misunderstandings early last year when 4.2 launched.
Flashing might corrupt the /data and/or /system partition. If it is interrupted during flash, partition info might be corrupted. Internal sdcard is inside /data and the content will be gone. But that would be a very rare situation. I would say one in a thousand.
Although there are over a thousand downloads all together, I haven't received a single success. I don't have a Tab-Plus to test so I decided to drop this build for Tab-Plus.
daniel_hk said:
I don't know what you meant by messing your file system?
I think you meant the content of the internal sdcard was moved to the folder 0. This is the way android handle multi user since 4.2. Your experience might only upto 4.1.2. There were similar misunderstandings early last year when 4.2 launched.
Flashing might corrupt the /data and/or /system partition. If it is interrupted during flash, partition info might be corrupted. Internal sdcard is inside /data and the content will be gone. But that would be a very rare situation. I would say one in a thousand.
Although there are over a thousand downloads all together, I haven't received a single success. I don't have a Tab-Plus to test so I decided to drop this build for Tab-Plus.
Click to expand...
Click to collapse
NO NO NO! PLEASE MAN! You can test anything with mine, just tell me what you want. I already provided a logcat.
This is the best rom yet, it has amazing features.
zombiezoom said:
NO NO NO! PLEASE MAN! You can test anything with mine, just tell me what you want. I already provided a logcat.
This is the best rom yet, it has amazing features.
Click to expand...
Click to collapse
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
daniel_hk said:
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, the logcat I provided was done from my Linux laptop. Now, I only saw SystemUI crash warning once but everytime I boot the device I see a black screen no home! just the toolbar and softkeys.
So, if you need another one, I'll make another.
daniel_hk said:
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Screenshots after a clean flash uploaded and you can see that I cannot access Home or Apps drawer
I also attached a ZIP of 3 logcat files.
Thank you so much for taking time to build for our tab
Downloading now!
Edit: the AFH link leads to the galaxy 7.7 downloads!
Edit: Fixed.
Thank you Daniel, everything is working as it should. But sometimes when restarting the tablet, it gets stuck on the CarbonRom logo. That's the only problem I encountered so far. I will update this post if I found any other problems.
EDIT: seems like it was fixed by flashing Minimal GApps ^^
Which Kernel to use?
I have tried all of the kernels available on the download link on the first post, but none work with my P6210. They all fail with a getprop error.
Is there a newer kernel somewhere? I am trying to use CM-11 unofficial or carbonrom.
Thanks!
Can folks please post experiences on the p6200, I've been using the 7.7 version which is fantastic, the most usable daily rom but if this is good enough on the plus, I'd really like to suggest this rom to a friend who is still stuck with 4.1 jb
xaadilhx said:
Can folks please post experiences on the p6200, I've been using the 7.7 version which is fantastic, the most usable daily rom but if this is good enough on the plus, I'd really like to suggest this rom to a friend who is still stuck with 4.1 jb
Click to expand...
Click to collapse
I am currently using the latest version and it's so amazing, ROCK stable. I have no problems with it. It's the best for Tab Plus so far.
EDIT: BTW a lot of people here -and I don't know why- don't appreciate the massive work that Daniel has made for Tab Plus. You could see a lot of downloads being counted but only a few people who would comment with reviews or even a thank you!
I'm extremely great full for daniel_hk's work but i think it would be great is somebody would test all P6200 roms and test them on common every day app and games and give feed back and benchmark scores as i have no idea what rom to try first ??? just look at the choices just from daniel_hk
this one is on my list to be tested just saying keep up the great work
Can we have some screenshots ram usage and benchmarks scores from somebody that uses it already? might cause more downloads and more replies
Thanks for your feedback on the plus zombiezoom, great to hear.
I've been trailing mainly P6800 (7.7) rom mods for about a year now. Its fantastic to be able to get access to these roms and everyone's hard work particularly Daniel, I must say he has so many roms posted and its great to trial them. I've been looking for a stable alternative to stock now for a while and I think I've found it.
I think people who use the roms are likely following guides from other sites, they just download, trial and don't comment here. To get everything working efficiently we do need to focus comments here to help the developers/ and ultimately ourselves by getting a nice working rom.
@ this point to have wifi, bluetooth, mobile function and other major functions to be working reliably is great. I'm sure those who make the switch from stock and remain would likely consider donations. I said on the 7.7 topic, that I rather less fancy functions and features and more stability. This way we can all leave the stock rom behind just like samsung left us there and turn to our rom of choice. Once we do that we then can support our developers who can in turn keep our devices stable and alive.
Thanks
{
"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"
}
SlimROM is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam works together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and Gerrit.
DISCLAIMER:
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
BUGS/NOT WORKING:
Some glitches (see screenshots (navbar))
You tell me
HOW TO INSTALL:
Full wipe.
Flash the ROM and GApps.
SUPERSU INSTALLATION
Wipe cache & dalvik cache.
Reboot System.
CREDITS:
SlimROMs Team
@monster1612@Hashcode @transi1
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.72+
Slim6 version: 1.12 STABLE
Build Status: Beta (MOB31K)
Based On: SLIMROM
NAVBAR: Go to Settings-Navigation-Navigation bar-Button style-button glow color and change button glow color to black (see screenshot #3)
TWRP BUILDS
Created 2016-09-02
Last Updated 2016-11-25
Don't be too excited folks. I used CM source for tate to bring this build (AOSP source isn't working yet). Plus, I had to tweak Slim source a little bit. When AOSP source will be done, I'll bring new build which should perform better. Some glitches occur, but the ROM does the job. And of course, if you found some bug, post about it here.
I will give this a try tomorrow! Thanks!
vasolini said:
I will give this a try tomorrow! Thanks!
Click to expand...
Click to collapse
Thank you as well.
There might be some Bluetooth issues.
Droid187 said:
There might be some Bluetooth issues.
Click to expand...
Click to collapse
If you found Bluetooth issues, please, confirm it. If you didn't flash the ROM, confirm it as well. THERE IS NO PLACE FOR "MIGHT BE". Don't forget, that's a test build. AOSP base is needed to make it work 100% properly.
alexander_32 said:
Thank you as well.
Click to expand...
Click to collapse
I'm not sure if it is just me, but I was unable to set up the rom. Everything flashed without an error, but when it got to the setup, all I could see was a small portion of the screen about an inch high x 2" wide right in the center. The text inside the window looked like it was the correct size, but I was unable to move it or enter any information for setup. Do I need to change any settings before flashing?
vasolini said:
I'm not sure if it is just me, but I was unable to set up the rom. Everything flashed without an error, but when it got to the setup, all I could see was a small portion of the screen about an inch high x 2" wide right in the center. The text inside the window looked like it was the correct size, but I was unable to move it or enter any information for setup. Do I need to change any settings before flashing?
Click to expand...
Click to collapse
Try to press on power button then press on power button again. Or tap on this small portion of the screen. I've seen it before. Again, that's a test build, but I'm sure it can do the job even with these little glitches.
alexander_32 said:
Try to press on power button then press on power button again. Or tap on this small portion of the screen. I've seen it before. Again, that's a test build, but I'm sure it can do the job even with these little glitches.
Click to expand...
Click to collapse
The second time's a charm! I have it up and running. Still in setup right now, so I'll try to give some feedback in a day or two. :good:
So far so good! I like how it uses less RAM than others, and it's pretty smooth and responsive. I had to get used to the navigation buttons looking like they were showing that they'd been touched all the time , highlighted I guess would be another way of describing it, but everything's working fine so far. I haven't tested Bluetooth yet. Since I don't use Bluetooth or the camera on my Kindle, that's not a priority. Overall this is a pretty smooth build!! I will be running it for a while. ?
vasolini said:
So far so good! I like how it uses less RAM than others, and it's pretty smooth and responsive. I had to get used to the navigation buttons looking like they were showing that they'd been touched all the time , highlighted I guess would be another way of describing it, but everything's working fine so far. I haven't tested Bluetooth yet. Since I don't use Bluetooth or the camera on my Kindle, that's not a priority. Overall this is a pretty smooth build!! I will be running it for a while. ��
Click to expand...
Click to collapse
Thank you for your feedback. In the future, it will be even better. Bluetooth should work too. It was just a suggestion by some user, who can't even confirm it. Camera works, I've seen it personally. I found the main problem with AOSP building, probably it's easy to solve it, we'll see. And, honestly, I'm surprised it's a pretty smooth build. Perhaps, I didn't wipe internal storage and some odds occurred.
If somebody can help me bring updated version of Slim6 without glitches, please contact me. You just need to download the source, my branches, change a couple of makefiles, nothing extraordinary. My building machine (laptop) is slow, I'm working on bringing other ROMs, so any compiling help deeply appreciates.
IMPORTANT UPDATE
1. Big thanks to @r3t3ch for unloading my laptop
2. The previous build was removed due to there is no point to let it live.
3. New build still has navbar glitches, but now it's definitely less glitchy. (Must be some specific Slim overlay stuff, will be fixed later)
4. 3.0.101+ kernel replaces 3.0.72+ kernel
5. Bootanimation is fixed
https://www.androidfilehost.com/?fid=24728673521238242
Installation: Full wipe/Flash ROM + Open GApps
Alex32,
Tried dirty flashing this over your latest 6.01 beanstalk,
which I have been using for a while and like a lot.
Wiped only caches, reinstalled gapps, android system
kept crashing upon reboot. Maybe the newer kernel
requires full wipe?(I know instructions say full wipe), but
I have been dirty flashing different mm builds of yours.
Wondering if I can just flash the new kernel from the rom in twrp
or do you think I will run into the same problem with crashing?
Just can't help myself I'm a flashaholic and wanted to try. Thanks
skalnas said:
Tried dirty flashing this over your latest 6.01 beanstalk
Click to expand...
Click to collapse
Slimrom isn't based on cm, so of course it's broken if you do that. Even flashing between cm variants without wiping system isn't a great idea.
r3t3ch said:
Slimrom isn't based on cm, so of course it's broken if you do that. Even flashing between cm variants without wiping system isn't a great idea.
Click to expand...
Click to collapse
Understood, I do realize that's a risk I take by flashing. That's why I have a fastboot cable and backups. I have had a lot of success switching between cm13 variants by dirty flashing without issue.
Didnt realize slim wasnt based on cm. Suppose I could try wiping system this time. Thanks
skalnas said:
Understood, I do realize that's a risk I take by flashing. That's why I have a fastboot cable and backups. I have had a lot of success switching between cm13 variants by dirty flashing without issue.
Didnt realize slim wasnt based on cm. Suppose I could try wiping system this time. Thanks
Click to expand...
Click to collapse
I'm not even sure it will work cleanly without a data wipe as well, though I understand the inconvenience. I usually use tibu to restore just user apps but if you have a lot of apps that can be time consuming as well.
Also to note, with all builds posted by alexander_32, the bootloader has enabled holding volume down to fastboot (vol up still recovery) so it can make entering fastboot mode a little more convenient.
skalnas said:
Understood, I do realize that's a risk I take by flashing. That's why I have a fastboot cable and backups. I have had a lot of success switching between cm13 variants by dirty flashing without issue.
Didnt realize slim wasnt based on cm. Suppose I could try wiping system this time. Thanks
Click to expand...
Click to collapse
You really should read instructions, descriptions, and follow them
Curious though I was able to upgrade your most recent beanstalk to your final beanstalk with the new kernel. Dirty flashed.
Sent from my Amazon Tate using XDA Premium 4 mobile app
skalnas said:
Curious though I was able to upgrade your most recent beanstalk to your final beanstalk with the new kernel. Dirty flashed.
Sent from my Amazon Tate using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No offense, but you better help me to make a test build for Slim6, than post stuff like this. And I'll make a test build for Omni today.
AOKP (Android Open Kang Project)
7.? Nougat for All Motorola "Quark" Devices (XT1225 | XT1250 | XT1254)
With Substratum/OMS Themes
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR PHONE!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
This is for the AOKP fans out there that are using the Motorola Quark, which includes: DROID Turbo, Moto MAXX and Turbo Maxx. It's stable, I use it daily, however it's still under development, see post #2 ("Extra Info") for additional information.
Screen Shots
{
"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"
}
Installation
Clean Install Recommend:
Use TWRP for a Full Backup
Wipe/Factory Reset
Flash ROM.zip + GApps
Clear Cache/Dalvik
Reboot
Upgrading
Use TWRP to Backup Data Only
Wipe/Factory Reset
Flash ROM.zip + GApps
Clear Cache/Dalvik
Reboot
Setup Phone
Reboot Recovery
Restore Data Backup
Download
Current Release
Open GApps 7.? (I used Pico)
Credits
Development:
@bhb27
ROM Testers:
@eddiemc12
@hpbrasil
@kitcostantino
@Nitefire77
@Shiftydogit
And, I've recently added more (PM me if you want your name here)
Sources
Source Code: AOKP
Device Tree: Motorola Quark
Kernel: BHB27 Stock Kernel
Extra Info
Most "bugs" have been fixed. IF you find one, feel free to share on this thread :good:
PLEASE, PLEASE:
Do a "clean install" before reporting issues, you may also want to clean your modem first using this:
Download Zip
(Flash using TWRP)
Kang 2
Great.
Is it using bhb27 kernel or you modified something in it?
Very nice, thanks @NepoRood
Debuffer said:
Great.
Is it using bhb27 kernel or you modified something in it?
Click to expand...
Click to collapse
Using bhb's stock CM14 kernel, it's running great. I'll be adding more information to the first 3 posts as time goes on :good:
NepoRood said:
Using bhb's stock CM14 kernel, it's running great. I'll be adding more information to the first 3 posts as time goes on :good:
Click to expand...
Click to collapse
But is it using Bhb kernel 1.0?
Or you changed something and it's your 1.0 version?
ROM was running great. Been running it a couple days without hassle
Nitefire77 said:
ROM was running great. Been running it a couple days without hassle
Click to expand...
Click to collapse
same here ,smooth and fast with no reboots.
For those who has problems installing because of com.android.phone has stopped
First fresh install
Reboot
It'll problem
Reboot in recovery
Dirty install the rom again (without any configuration done in the first boot)
Reboot
Worked for me.
@NepoRood can you please add caffeine tile in next update? And maybe zzmoove gov? I know its just the first build, but this additions would be really loved. Thank you for such a good job.
Link to kernel not working. Could you please confirm
janine13 said:
Link to kernel not working. Could you please confirm
Click to expand...
Click to collapse
It's a typo, my bad. You know that is the source code, right?
@Debuffer, personally, I have no use for all the "extra" functionality of a custom kernel. After the holidays, I'll look into providing a custom kernel along with the stock one (like bhb does with RR). Just out of curiosity, did you install the Kernel Auditor app?
NepoRood said:
@Debuffer, personally, I have no use for all the "extra" functionality of a custom kernel. After the holidays, I'll look into providing a custom kernel along with the stock one (like bhb does with RR). Just out of curiosity, did you install the Kernel Auditor app?
Click to expand...
Click to collapse
Yeah. I use Bhb kernel since 5.1.
Thank you for this.
NepoRood said:
It's a typo, my bad. You know that is the source code, right?
Click to expand...
Click to collapse
Yeah, I got that part after I went to the site. I was looking for the kernel in a bid to try using it with the ROM. I have been using the ROM for the past 3 hours now and all seems smooth and stable so far. I will keep running it and see, if it stays this way I just may have a new daily driver
Great rom, it runs very well. Only issue with it, is that the torch using gestures is very inconsistent. Similar to what happened when 6.0 roms first came out. It either takes 30 seconds to activate, or never works at all.
Also, the setting to control media volume by default doesn't work. This is the same on cm14.1, so imagine it's not something you can easily change in the rom.
Users with GPS problem only make the flash of this file that will be solved.
https://www.androidfilehost.com/?fid=24531035584725320
Please add publication. @NepoRood
Very good rom.stable and smoot.but there is little laggy for camera conect in many apk.more of it happens for front camera
Sent from my DROID Turbo using Tapatalk
great rom, liked it alot, clean installed it without any phone stop errors, bhb27's auditor n govtuner works perfectly aswell
only one issue i have was when i take photos im not able to share them online for some reason (example via watsapp or facebook) it always shows "sharing failed please try again" msg. dont know what happened there i tried re-installing watsapp and also a different camera app but still get the same error.
reverted back to 6.1 for now as i really need photo share as my work is depended on it, although i did notice the pictures i took on 7.1 now in the gallery were corrupt n un-viewable aswell ? was there something i did wrong? should i try flashing again?
Pakman300 said:
great rom, liked it alot, clean installed it without any phone stop errors, bhb27's auditor n govtuner works perfectly aswell
only one issue i have was when i take photos im not able to share them online for some reason (example via watsapp or facebook) it always shows "sharing failed please try again" msg. dont know what happened there i tried re-installing watsapp and also a different camera app but still get the same error.
reverted back to 6.1 for now as i really need photo share as my work is depended on it, although i did notice the pictures i took on 7.1 now in the gallery were corrupt n un-viewable aswell ? was there something i did wrong? should i try flashing again?
Click to expand...
Click to collapse
There are 2 folders where pictures are stored: DCIM and Pictures
Using the built in file explorer (or a PC), rename each of these. I did DCIM2 and Pictures2, then use your phone to take a picture. Both folders will be recreated. Then, drag and drop everything from the #2 folder into the corresponding "New" folder.
Hassle? Just a bit, but we did just change branches on our android phones :laugh: