UNOFFICIAL CyanogenMod 11.0 BETA V0.3
by MisjugdedTwat a.k.a. BangL
WHAT IS THIS?
This is an UNOFFICIAL build of CM-11.0 ( CyanogenMod 11.0 ) for Huawei Mate (hwmt1_u06)
I am basically just continuing the work of others by merging and compiling, so credit goes to surdupetru, joestone, asyan4ik, mrAlmid and all coders who contributed to CyanogenMod.
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. Hard. A lot.
*/
REMEMBER
If you choose to use my unofficial build, pls don't post your issues and/or request in the official CyanogenMod forums. My builds contain unofficial code and MAY affect the official debugging process.
I do this in my free time, for free. Never forget that
Take care and do backups before flashing!
FIRST INSTALLATION (of THIS rom)
!!! BACKUP EVERYTHING !!!
Make sure your bootloader is unlocked, and install TWRP 2.8.1.0
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot into TWRP
Do a FULL WIPE (system, data, cache, dalvik) ! - you can try to keep data, but it will most likely fail booting.
Install the ROM, using TWRP
Install the Gapps, using TWRP (optional)
Reboot to system
UPDATE INSTALL (when you already have another version of this rom installed)
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot to recovery
Wipe system
Install the ROM, using TWRP
Wipe cache & dalvik
Install the Gapps, using TWRP (optional)
Reboot to system
LATEST CHANGES
V0.3
V0.2
CM SOURCES MERGED UP TO:
Change 110843 - manifest: Remove vendor/cyngn repo
http://review.cyanogenmod.org/#/c/110843/
INCLUDED KERNEL
whirlwind.kernel
KNOWN BUGS
a2dp is not running perfect, but it runs. - sometimes.
Nfc is probably not working at all, not sure.
GPS acts a little weird sometimes.
Video compression results in pure trash.
Clock might get desynced
DOWNLOADS
Please note this build is for bug-hunting purposes only, yet! (Plain CM is boring anyways)
I am just starting to build for this device and with this build am currently trying to get a stable basis for other roms.
My goal is having a fully working code-base for any AOKP-based 4.4 ROM.
So PLEASE join the testing phase, try every ****ing functionality on your phone and report the results here, so i know whats done and what needs to be done. Thanks!
Rom
https://www.dropbox.com/sh/gd42e500zsrl7e0/AACjh4We8ZjULayjWFL7Y1lla?dl=0
Gapps
Use any "ARM - 4.4" package from open gapps (i recommend the nano variant)
Bootloader/Recovery
If you are still on a locked bootloader, having an unrooted stock rom, or an old twrp installed, use this updated unlock/recovery suite for windows and linux:
TWRP 2.8.1.0
SOURCE CODE
https://github.com/hwmt1-u06/android
NOTICE:
I removed the asound codecs, which increases the sound volume dramatically. I wanna enjoy my music loud, when i'm sitting in the bus!
This kinda ****s up the speaker, since its too loud now, which causes clipping.
I use the Equalizier in CM's DSP Manager to reduce the speaker volume (by turning all levels around -6db)
Having loud volume, and the ability to decrase it, is better than having silence and no ability to increase it, right? Thats like going to the hair stylist and wanting longer hair.
Cool, thanks for your effort!
Will give it a try when I feel I have enough time
UPDATE V0.2
CHANGES
Fixed rebooting to recovery
Changed some default system props related to adb and root
Thats it, any bugs?
Otherwise i will now focus on porting more aokp roms, building twrp and a maybe a kernel.
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
sijben said:
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
Click to expand...
Click to collapse
Its probably both messed up as well in this ROM, i don't have the hardware to test those functions. Maybe you can tell me
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
SvenHee said:
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
Click to expand...
Click to collapse
its meant like this:
- first install the first installation of THIS rom
- update install is when you already have this rom installed (e.g. v0.1) and you wanna update to another version of this rom (e.g. v0.2), and keep your apps, data and settings.
and remember to backup first!
EDIT: Updated instructions in first post
Very good, thanks!
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Thanks for tests your reports, guys!
let's see..
SvenHee said:
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Click to expand...
Click to collapse
Wait.. what? Are you telling me a2dp is working perfectly fine? I did not expect that at all!
Yeah, i will port more ROMs, but first i had to have my own kernel (see below) :fingers-crossed:
blankulus said:
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
ive already patched in a tweak to help that problem atleast a little, i am not sure if theres more i can do.
as far as i know it's a well known jb/kk-problem on devices with very low ram... i had an LG O2x, which hab like 500MB ram or something... it was pretty much ununsable when someone called. i remember something like they started to remove the incallUI from the permanently-open list - if you know what i mean. and that's why it's causing this problem.
i don't really have this problem at all, to be honest. so maybe you can help it by removing some service-apps.. or maybe theres some app to force another app to stay loaded? i don't know, just an idea.
tauio111 said:
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
Click to expand...
Click to collapse
arg... P6? different kernel?
so your report doesnt really help me, since i dont even know what the exact differences between the MT1 and the P6 are, and most off the hardware related stuff is kernel related!
Good to see it's running well for you, though.
But thank you very much, srsly.
btw: you are having the wifi dropping too? thats weird, i was sure thats a kernel & /system/lib/modules thing.
...which is why i focused on kernel building for now. It seems like some people are smashing any modules they can find at their kernel until it works somehow. - this is a huge mistake. kernel modules in /system/lib/modules MUST be built against the exakt same kernel, they will be used on.
To be sure to have that clean, i felt like i need to get into that stuff as well. - and i actually just succeded like 30 minutes ago.
I will try out some things on this build, and when everything seems stable to me, i will even release my own kernel, which will always be shipped with the correct modules
But that will be HIGHLY experimental, and for the MT1 only!
Only had minor hiccups when browsing the internet at the same time.
Now testing the second session of music
Edit: A few more hiccups in one session, pretty good play a bit later. Very usable.
Installed and so far its very smooth
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
SvenHee said:
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
Click to expand...
Click to collapse
interesting.. is there any cm based rom, where you dont have that problem?
Carbon was the only 4.4.4 rom by Mr. Amid I got working, I know now (with your explanation) that I should have wiped data too when flashing a new rom.
I can not recall having the Maps problem with 4.2 roms.
UPDATE V0.3
CHANGES
Fixed /data/share paths in frameworks-base and system-core
System-props and init.rc script optimization
Using wpa_supplicant_8_ti instead of wpa_supplicant_8
Prebuilt B331 kernel and kernel-modules removed
Built whirlwind.kernel #2 from sources
Built wifi modules against whirlwind.kernel #2
Is a2dp, gps and wifi better with this build, or maybe even worse?
Will I be able to upload videos to instagram ?
Related
Scoot CyanogenMod 7.1.0 RLS3
This is a build I have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
Well, it still isn't quite as snappy as Froyo and the camera still doesn't work properly but it's probably about as fast as Gingerbread will get on our devices. I'm bound to have messed a few things up but i'll continue to work on it when I get time
All the usual things are working as far as i know, GPS works fine for me but the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, vilord, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
RLS2:
Built from the latest 7.0.2 source
Optimised EGL for our devices
Updated Market
LDPI and PNG optimisations to save space & increase speed
ADW Launcher updated
Loads of tweaks and status bar changes
Updated RIL lib
Loads of fixes and optimisations
**I recommend leaving the phone for 5 minutes after installing to sort itself out and cache apps etc...**
RLS3:
I can't really be bothered to list all of the changes, there are quite a few but I just compile the thing, the changes are in the CyanogenMod repository. I have included the updated RIL and all of the Google Apps are up to date. The camera is still ****e but that's a driver issue. This release hasn't been heavily tested as I don't use my Kaiser as a main phone anymore So i'm sure you will find issues in which case we can sort them out as and when. Enjoy!
LINKS:
RLS1:
English: http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages: http://www.mediafire.com/?amhd996w81xfldp
RLS2:
English: http://www.mediafire.com/?yhsc6jyl47wgpkv
All Languages: http://www.mediafire.com/?v3hhbh5tufoedfp
RLS3:
English: http://www.mediafire.com/?76vn9k0cx3debzd
All Languages: Coming soon!
Google Apps
28.04.11 : http://www.mediafire.com/?4yc9ubn2m513k3q
07.08.11 : http://www.mediafire.com/?c86rpae5kopdicc
I think that's it for now, have fun
OOOOOyyyyéééééé OOOOoyyyyyéééé !!!!
download'n !!!
thinx scooter & all android developers for our old kaiser
'll try your build this night & report any bugs...
keep working i realy apreciate your work sccooouut
xcuse my stupide bad english
cordialement esolks.
scooter1556 said:
Scoot CyanogenMod 7 alpha RLS1
This is a build i have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
This is an alpha and still needs a fair bit of work to get it running to it's full potential but you can get an idea of what it will be like. Feel free to report any bugs that you find, by this i mean application crashes and things that don't work or look correct. I already know the system can hang and it isn't as fast a froyo
I have had to make a LOT of modifications for this to work, some of which may affect battery life but i haven't tested it for long enough to know so let me know how it goes. I'm bound to have messed a few things up but i'll continue to work on it when i get time
All the usual things are working as far as i know, i have not tested GPS fully and the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
LINKS:
RLS1 :
English : http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages : Coming soon hopefully.....
I will try and get some screen shots posted for those that like pretty pictures
I think that's it for now, have fun
Click to expand...
Click to collapse
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?
-Arturo- said:
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?
Click to expand...
Click to collapse
It is indeed
scooter1556 said:
It is indeed
Click to expand...
Click to collapse
Excellent, thanks Scooter.
downloading now keep up the good work man
woot...gonna give it shot ... hoping for not getting same data/wifi reboots
woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance
Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
I have noticed that there have only been modules for '32 kernel included in the build. Should it work with '25 kernel with proper modules added?
I'll wait for All Languages version to test it with the new kernel.
1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...
chinomoreno said:
1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...
Click to expand...
Click to collapse
YES! you can
To view Battery percentage, you need to set that in Cyanogenmod Settings (correct me if I'm wrong here since its been ages when I used CM build)
Yes, you can do that it's actually very simple. Just remember to edit your .nbh before every install if you are changing versions (donut, froyo, eclair).
Cheers. Welcome to Android world
-Arturo- said:
Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
Click to expand...
Click to collapse
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry
scooter1556 said:
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry
Click to expand...
Click to collapse
Yes I have noticed that there have only been '32 modules included in the build.
I think I'm going to skip the '32 kernel as It was acting up on me in the past. I'll try nand install in the evening hopefully it will work. Thanks Scooter.
-Rif- said:
woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance
Click to expand...
Click to collapse
I recommend using the latest .32 kernel you can find, either one that L1q1d has compiled or one from Clemsyn's thread You can find the latest kernel here: http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD
Well have installed 6.1 and phone now works... =)
Will wait until a new version of this one to come out and then try again...
- Already found how to show percentage in bar status thanks dark_prince.
- Thanks for advice slimas, to edit .nbh do i need to reinstall kernel? and can i reinstall without mess up with previous android install or do i need to install again android?
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
I'm reading forum and these are some questions i couldn't find answer, for now i think that's all.. i'm enjoying android on kaiser think this is the time i will change forever...
thanks for fast feedback any good tips are welcome ;P
chinomoreno said:
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
Click to expand...
Click to collapse
The bar at the bottom of the scrren can disappear if you swipe down on the screen, it is a bit random but is a flaw in ADW launcher. To get it back you need to press the 'menu' button and go to 'settings' then go to 'ADW Settings, UI Settings and untick 'Dockbar'. Re-select 'Dockbar' and exit settings and it should be back I expect some freezing, it is still under heavy development and our devices are quite limited hardware wise so there won't be any miracles yet I overclock my Kaiser to 500Hz using ATools, a lot of people don't recommend it but it is what i have always done and i have never had any problems, it speeds the phone up a fair amount. Just tick the option when editing your NBH. The phone obviously needs to be connected to data or wifi for weather widget to get location information, i just tried it with wifi and it worked ok, there may be an issue with data though, i'll look into it Thanks for testing.
CAMERA
camera is not working properly but it looks awesome i will try to apply the update from previous cm to see if this will work
camera
after applying the update android can`t start so i am going reinstall it
*Copied from CM10 FAQ by RaphaelH1427.
ATTENTION: THESE BUILDS WITH KERNEL 3.0 ARE EXPERIMENTAL! QUARX IS NOT RESPONSIBLE FOR BRICKED PHONES, WORLD WAR, ALIEN INVASION, YOUR GIRLFRIEND CHEATING ON YOU OR ANYTHING!
Welcome to the support thread of Quarx's CM10.1!
[CM10.1] Android Jelly Bean 4.2 (By Quarx)
What is this thread for:
Here you can report all your problems of the Quarx's CM10.1 that you have and ask for help to see if it's solvable by others methods that doesn't include posting to the original rom thread.
This thread will be easier for him than look for all reports spreaded in the many pages of his thread, but remember, avoid flood!
Before adding your problem(s):
- Be sure to use the latest version of CM10.1! (Check here!)
- Be sure that your report is not already reported by someone, so use the search button.
Take a look here if you wanna know how to install the ROM, and few things like that: FAQ & FAQ 2 from CM10. :good:
BUG LIST:
Kernel 2.6: BT-Headset is a bit buggy, BT will not work if FM is enabled, some problems with 3G, video recording is not good.
Kernel 3.0: Low speed of USB mass-storage, display do not always wake after sleep, suspend not working correctly.
WHAT WORKS?
Kernel 2.6: Almost everything.
Kernel 3.0: SD-Card, Bluetooth, Torch, Leds, USB (all modes), HW Video decoding, Sensors, FM-Radio (only seek stations+RDS), Sound (only speaker).
WHAT DOESN'T WORKS?
Kernel 2.6: BT-Tethering, USB-Tethering
Kernel 3.0: Headset, BT-headset, FM-Radio sound, Phone, GPS, Camera, FM-TX, WiFi.
TIPS:
-Coming from CM7/CM9/CM10? Wipe Data!
-ALL BUILDS WITH KERNEL 3.0 UNTIL FURTHER NOTICE FROM QUARX ARE BUILDS FOR TESTING PURPOSES, SO IT'S NOT READY FOR DAILY USE!
-Need extra internal space? Use an Minimal Gapps! Download here. (Thanks to xinrag for the tip!)
Remember to not have a screenlock with more than 3x3 if u update from previous build , i had and couldnt put it in ...
Did a factory reset then , flashed 4.2 and gapps 4.2 , booted up first run.
Talk to speech crashes several times at first startup , baseband no good (im in Norway), very weak signal
zer0grav1ty said:
Remember to not have a screenlock with more than 3x3 if u update from previous build , i had and couldnt put it in ...
Did a factory reset then , flashed 4.2 and gapps 4.2 , booted up first run.
Talk to speech crashes several times at first startup , baseband no good (im in Norway), very weak signal
Click to expand...
Click to collapse
Quarx recommended on Facebook to wipe data before updating. And like he said, almost everything doesn't work properly. So, not ready for daily use.
update..
Cant find SD card +settings crashes when you try to access storage..
"Quarx recommended on Facebook to wipe data before updating. And like he said, almost everything doesn't work properly. So, not ready for daily use."
True , a bit early for daily use
zer0grav1ty said:
update..
Cant find SD card +settings crashes when you try to access storage..
"Quarx recommended on Facebook to wipe data before updating. And like he said, almost everything doesn't work properly. So, not ready for daily use."
True , a bit early for daily use
Click to expand...
Click to collapse
I also cannt find wifi,,,
Tjunkustc said:
I also cannt find wifi,,,
Click to expand...
Click to collapse
Searching does not work, but you can connect manually. works for me.
Are minimal GAPPS 4.2 out there yet?
@Gafanhotz Good idea to creat a new thread for 4.2 :good:
mitchum67 said:
Searching does not work, but you can connect manually. works for me.
Click to expand...
Click to collapse
For me too....
Sent from my MB526 using xda app-developers app
SD CARD can't be mount
zer0grav1ty said:
update..
Cant find SD card +settings crashes when you try to access storage..
"Quarx recommended on Facebook to wipe data before updating. And like he said, almost everything doesn't work properly. So, not ready for daily use."
True , a bit early for daily use
Click to expand...
Click to collapse
SD CARD can't be mount. me too . Defy MB525
yangvincent said:
SD CARD can't be mount. me too . Defy MB525
Click to expand...
Click to collapse
Quarx will solve that in the next build don't worry. It's not working for anyone. It's just a Demo rom so please wait until master quarx releases a daily usable rom.
Sent from my MB526 using xda premium
New unofficial version
After install some times in nany ways and settings I confirmed that new 4.2 version is good for defy hardware and custom kernel.
I still worry when Quarx2k implements the CM feautures if this is bug the rom.
But now...
1 - With or without gapps (4.2 or 4.1.2) the initial settings show erros.
2 - GSM signal is very weak, but phone tottaly functional.
3 - Widgets are not full sized on screen ( all go to left on screen).
4 - Phone with lot of memory and flows very good.
Where can I download gapps 4.2?
I hope the data dropouts i have in CM10 will be solved in CM10.1 but dont have my hopes up to high because they been there so long now that i dont even know when they started, might have been already on CM9 but im not sure.
Another thing that worries me a bit is that the system space is not big enough while internal storage atleast for me is on over 1GB, possible to make the system space bigger?
Cheers?
morteza-25 said:
Where can I download gapps 4.2?
Click to expand...
Click to collapse
Read the first post of CM10.1 of Quarx2k in Development Section
FlashTec80 said:
I hope the data dropouts i have in CM10 will be solved in CM10.1 but dont have my hopes up to high because they been there so long now that i dont even know when they started, might have been already on CM9 but im not sure.
Another thing that worries me a bit is that the system space is not big enough while internal storage atleast for me is on over 1GB, possible to make the system space bigger?
Cheers?
Click to expand...
Click to collapse
We can't resize system rom, because we have locked bootloader & i think 2ndboot will not help. Solution - unistall not need system apps, hint: unistall CMWallpapers - it will free about 10MB in SROM
Could this app solve the SD problem?
http://forum.xda-developers.com/showthread.php?t=1652079
Gafanhotz said:
Quarx recommended on Facebook to wipe data before updating. And like he said, almost everything doesn't work properly. So, not ready for daily use.
Click to expand...
Click to collapse
can you send me the facebook link? thanks!
sorry for off topic
Why quarx named cm 10.1 as unofficial build but cm 10 is also not official but he dint named it as unofficial builds.
mothy1025 said:
sorry for off topic
Why quarx named cm 10.1 as unofficial build but cm 10 is also not official but he dint named it as unofficial builds.
Click to expand...
Click to collapse
What's the point of this question??
You are in a stupid confusion!
Both are UNOFFICIAL ( Who cares though )
I don't want a tapatalk sig!
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
you can find more information here: http://forum.xda-developers.com/showthread.php?t=2541182
Gapps is included. You must install rom zip first, because it formats system partition.
Official gapps doesnt compatible with our phone, I think its better not installing.
hmm..
Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
I am using omni ROM . . somehow I find it less buggy than cm 11
Nevertheless I would wanna give my thanks and even though I am pointing out bugs . . I really do appreciate his work .. A lot
Omnirom is very very stable has all if not most of the theming features except for trebuchet launcher
//It is a bit more battery consuming but I like it cause I am able to run my processor at 1.4ghz which is sweeeet!!!
//It has issues with OK Google functionality the audio is lagged and irritating
//The Google experience launcher is not built for it
//It has issues with Google maps 7 but there is a fix to have 6th version to back you up when needed
//it has issues with Skype and the fix is work in progress I guess..
//GPs is a bit slow but works
//WiFi direct crashes for me
Once in a blue moon the phone might rebot itself cause of a crash..
Though considering WiFi tethering , 3g switching, link2sd ,memory swapping
Ksm everything is working really try it . . its an amazing experience from an amazing phone
Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?
Wi-fi direct is a type of communication between two devices, similar to Bluetooth, so you can send files. I never used this, even when transfering big files from one phone to another, it's better to use an USB OTG cable - the connection speed is lightning fast!
Don't know what you mean about wi-fi sharing. Maybe wi-fi tethering (hotspot) - it's when you share your phone 2G/3G internet connection via wi-fi. This thing is working fine. Wi-fi itself is working, of course.
As for keyboard light: when tested OmniROM, I used liblight solution, but the qwertyled using is simple too: just launch it and you're done. While the service is running, keyboard light will work.
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!
Makshow said:
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!
Click to expand...
Click to collapse
Can you use a cyanogen mod rom with clockworkmod recovery installed? i remember trying cyanogenmod with my phone and couldnt get it to work.
Just flash TWRP 2.6.3.1 from link above, it's superior to clockworkmod recovery (CWM) in all ways: touch interface, working backups with compression, charging support and it allows to install KitKat roms. With CWM you can install ROMs up to android 4.3, so, you still can install CM 10.1.3 or CM 10.2 with CWM, but not CM 11.
about wifi direct and sharing...
Pawprints1986 said:
Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?
Click to expand...
Click to collapse
Hey yeah the difference btw wifi direct and sharing is that in wifi direct you connect two devices directly to transfer files...
in wifi sharing you need to host a web adress to share your files
as a result in wifi sharing you host a list of your stuff on a web adress(local) which gets downloaded by other devices on your wifi connection
and a wifi sharing manager can either do this (host ur files using an ip) or my personal favorite is astro which can acess my pc's sharing folder over wifi which is preety awesome>..unlimited storage
also note that in a wifi sharing manager you cannot recieve files easily . . maybe airdroid but it can only run on a pc
wifi sharing apps are airdroid and other file managers like root browser
wifi direct requires specific drivers and libs... i guess.. hence not all devices can do it ..
anyway you should go for cm 11 or omni both are incredibly stable with an occasional hiccup.. which is occasional heh
also would suggest that if you do proceed to install please follow from the developer sources on xda rather than some blog etc
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk
cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.
Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!
SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...
Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.
Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Man, you are the best! And what about sensors?
And where did you find this solution?
hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.
How to make this logs? i know nothing in programming (
I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......
deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk
yea, link?
?????
Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk
uplodz complete.
Interesting :good:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!
Nice can we flash the Kernels that have been around here for a while on this rom?
patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.
deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $