This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent
ClockworkMod
ClockworkMod for A860 K/L/S
Flash using fastboot. Instructions are all over XDA so please search.
Thanks
thanks so much for your work...
another than CM10.1 , I also want to see customized kernel which can further enhance A860 , like power tweaks, disable logging, init.d or even add FauxAudio mod
Finally something about te Vega No6
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
Leechoonhwee said:
This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent
Click to expand...
Click to collapse
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!
magare said:
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!
Click to expand...
Click to collapse
Anyone can help in anyway they can! Please take a look at the following page about CM porting.
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Currently, I am trying to find a similiar device in terms of hardware and use their kernel github and try to build a test build
Device Tree
https://github.com/CyanogenMod/android_device_sony_yuga
Kernel
https://github.com/CyanogenMod/android_kernel_sony_apq8064
Let me know. Thanks!!!!
Sorry. Got busy at work and don't have time now.
Interesting
Sent from my IM-A860S using xda app-developers app
I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs
Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.
aget1 said:
I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs
Click to expand...
Click to collapse
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.
totalz said:
Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.
Click to expand...
Click to collapse
I remembered coming across a CWM mod that can allow you to choose which to backup. You can try ROM Toolbox.
Leechoonhwee said:
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.
Click to expand...
Click to collapse
As long as it boots, and it is a 3.4.0 kernel, i think it will work with cm10
anyway i am checking out cyanogenmod, but i dont find the a860 cwm recovery_ui.cpp source, only binary... i guess i need time to find the button mapping?
You could get answers from SDA.
Sent from my KM-S220 using xda app-developers app
There is a working CWM around in the 91dongji forum - works fine on my A860S with 1.30 software; now updating to 1.36 and see if the recovery sticks.
I'll post detailed instructions here once it is confirmed to work
i hope we can get some update on your efforts. though the crowd for this specific device is fewer than a handful for now, a lot of users are just waiting anxiously for any development....
Is there hope for this device to receive custom ROM?
there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.
tommyrumbler said:
there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.
Click to expand...
Click to collapse
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.
clockedtouch said:
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.
Click to expand...
Click to collapse
so why not set up your APN? that should be easy.
Also, using the ROM from vegaviet, i noticed the following observation :
-there was a considerable build-up of lag after three to four days of use, especially when doing a lot of web browsing
-the browser is unable to open some websites/webpages due to Ad-Block restriction
-the forced DNS settings most times slow-down my internet connection
-the keyboard still retains Korean functionality, with Korean characters sometimes getting in the way when typing
-kernel logging was enabled
much of the above were solved using the uninstall zip of crossbreeder - i just noticed our Vietnamese friends are fond of using cross-breeder on all their ROM mods.
the keyboard i uninstalled and deleted the IME file in system and just replaced it using Optimus G Pro's keyboard IME installer.
everything should be all good. don't ask me where i got those zips - a simple search should do wonders for you.
The rom doesn't allow for setting up your own APN. Those features are not available in JB. Thanks for the tips but I just went back to stock since I wasn't able to get the network going.
Sent from the brightest star in the sky using xda app-developers app
Related
I have picked up an old project I was working on, getting Eclair on our phones.
Now you might think, why Eclair, it is much older than Froyo and we already have Gingerbread!?
The answer is simple, just because we do not have Eclair roms for our phones
Some people here think newer is always better, but that is not always the case
Eclair is already booting, but I have some FC's and launcher does not work correctly. Neither any other things work.
I was trying to get a logcat, but could not connect using adb.
Perhaps someone else can give me a solution for enabling adb?
What did I use to get eclair booting up?
Froyo bootimage
Compiled Eclair using Froyo-libs and kernel.
If you want to take a look at it, here is a pre-pre-alpha where nothing works
It is not the latest, because I'm already solving some problems.
Reserved for future use
Why are you doing this?????
Raffy 97 said:
Why are you doing this?????
Click to expand...
Click to collapse
Damn ---^^^open your eyes wide n read d first post!
Sent from my LG-P500 using Tapatalk
First: Congrats
Second: Provide some logcat,maybe you have same problem as mine in OMFGB (missing resources in apks)
Third: Upload to your gitHub,I'll have a look
BTW: Could you check if you have any /build/core/kernel.mk? Really getting mad with that error on CM6.
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
_Arjen_ said:
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
Click to expand...
Click to collapse
Non-working RIL could be caused from three things:
You missed LG services into makefiles/.rc files (if you want I can PM you some strings to add to .rc files)
Wrong libs (easy to check)
Non-prelinked libraries (define TARGET_PRELINKER_MAP (or some like that) into device_thunderg.mk and modify prelink-linux-arm-msm7xx7 or some like that with names of unlinked libs. You can see what stuff isn't prelinked with a debugging-enabled linker you can find into Swift-sense Mur4iK GT540 post. For prelink address,use google because I don't know
Would this have any actual speed benefit?
Sent from my LG-P500 using Tapatalk
You will absolutely encounter speed differences with Gingerbread.
You will even have more space available, romsize is rather small
_Arjen_ said:
You will absolutely encounter speed differences with Gingerbread.
Click to expand...
Click to collapse
yes performance will be 2x(low) xD
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
ccdreadcc said:
yes performance will be 2x(low) xD
Click to expand...
Click to collapse
Reply to my private message
Sorry for offtopic
Sent from my LG-P500 using XDA Premium App
CAF Code right?
BTW,Did you build kernel together with the system? If so check your kernel.mk into /build/core. I'm getting mad at it.
Sent from my LG-P500 using XDA Premium App
No, this one is just AOSP with some LG crap
And booting using original LG Froyo kernel for now
Seems most compatible
Perhaps later a custom kernel will be used
Sorry for this off topic, but, good job and good luck ^_^ i hope you can successfully do this i loved the older builds of android an would love to go back to it, i wish i could help in some way and this is the best i can do :3 but good luck
What's up with RIL Arj?
_Arjen_ said:
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
Click to expand...
Click to collapse
whaa xD what now lmao,
good to see we can use eclair hope the look is as i remember D:
It is still as simple as Eclair is, it still uses the KISS principle
_Arjen_ said:
It is still as simple as Eclair is, it still uses the KISS principle
Click to expand...
Click to collapse
It didn't boot for me so i were not able to test
Sent from Mexico
The one posted here just boots to UI but launcher etc FC. (that is why it is called pre alpha)
Got one with working launcher now, but spent some time on OMFGB with Bytecode and CM9.
As soon as all is working I will release a beta.
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/system.img.gz md5sum: 29a6c707d25520c28528b502bb190c7e
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
jimbridgman said:
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
https://dl.dropbox.com/u/45576654/system.img
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
Click to expand...
Click to collapse
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
EDIT: i assume the gs3 is GSM correct?
lkrasner said:
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
Click to expand...
Click to collapse
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is in the system.img file I posted.... just mount it as an iso and you can pull out /system/app and grab the Svoice.apk from there.
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
jimbridgman said:
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Click to expand...
Click to collapse
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
lkrasner said:
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
Click to expand...
Click to collapse
Yeah I think that is a good start. Take a look at this link, the guys from team epic that do cyanogenmod ports have come up with a way to use kexec to test booting thier kernel and roms. You might PM one of them, I have not gotten to that point yet, plus these guys are working on the Sprint version, of the SGS3, but I am sure they can explain how they are doing this with kexec. These guys are on XDA, I have chatted with them on a couple issues I was having.
http://www.epiccm.org/
Oh, P.S.
Here is how to compile the "stock MB/ME865" kernel:
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make m2_att_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
Just make sure the toolkit is pointed to the install of the codesourcery toolkit I linked in the above post.
P.P.S
Your defconfig might be another pointer name, that you will have to find out for sure. You know the one above called m2_att_defconfig.
For the beginners don't try the rom,you might kill your phone!
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Glad to see you back around here, but lets not even give anything towards JB until we get ICS. if you are interested in helping with that, send me a PM, I have made some progress with cm9 (as in it boots fine, and i have some ideas for the radio).
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Yay! Cogeary's back! Good to see you around again...
Sent from my phone's mind
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
ICS to JB is going to be a much smaller kernel jump, but there will be a HUGE performance increase due to project butter which is now officially part of Jelly Bean.
The key to running something like this is to get a kernel compiled and running with kexec, even though it is just 1 proc, it is a good way to get started. Ports will be much easier if you do some merging of the changed code in newer kernels and do merged kernel. There are instructions for doing a kernel that is merged from 2 sources to get a complete kernel.
Now this will just work for testing and porting, and the actual ICS or JB install from at least a leak will be needed to actually run the port, but you can get ahead of the game by doing what I have mentioned.
Well going to give this a go in a few days doing some maintenance on my computer but will get back with something (hope not a bricked phone) .....
(off topic ranting)
Hate to say it at this rate what getting close to a year since Ics release Jb might just be a pipe dream..... Think I am growing grey hairs waiting for something to give here..... Without bootloader unlock I feel so useless (Yea I could make a recovery image with all the bells and whistles but I got bigger plans).....
Downloaded so I could tinker with some files. Thanks for sharing.
Sent from my SAMSUNG-SGH-I997 using xda premium
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
sure, no problem, give me a bit, my internet is slower than hell where I am right now.
EDIT: of course I didn't add it to dropbox originally, so now it is uploading to google drive. It just hit 1%
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
I uploaded it to my Drive right away after downloading - try this for SGSIII ICS: https://docs.google.com/open?id=0B-CZ8hXV8qOiVGtjOHZ3ZEg5eFU
P.S. - I also have a JB dump there, if anyone's interested: https://docs.google.com/open?id=0B-CZ8hXV8qOiSkc3QkE1Y0ZsRkU
EDIT: make that 2 jelly beans: https://docs.google.com/open?id=0B-CZ8hXV8qOiS2QtcG41QUh4R1k
...I was pretty active during the I/O hype last week...
jimbridgman said:
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
Click to expand...
Click to collapse
Why not try Filedropper or Mediafire?
MagicXB said:
Why not try Filedropper or Mediafire?
Click to expand...
Click to collapse
I am actually trying to get my recognized developer cert on here and get free premium access to xdafilehost, that all the recognized devs get access to.
We will see if I get it or not. If not I have other options, but things like filedropper will not do, I already looked into it
Perfect Android is a redistribution of the Android Open Source Project and Google software code that I have lightly modified to make as a daily driver for myself that I'm sharing with the community. This project doesn't have and won't focus on adding a ton of features and mods but instead focus on stability, and reliability so yes basically this is a stock like rom but not just stock my only efforts will be to make it run better, and be more polished, and complete.
GOOGLE APPS ARE INCLUDED
DOWNLOAD:
https://hotfile.com/dl/181925379/d84644d/perfect_grouper_ota_2012-12-01.zip.html
Mirrors:
If you have an error or something pops up I ask that before you post about it please make sure that you are running the ROM as provided. I cannot troubleshoot anything that is related to using other kernels, mods, or themes.
This ROM is basically like a stock rom of jelly bean so there is not a need for screen shots ........
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project my ROM is un-branded just give me some mention .......
WANT TO CUSTOMIZE THIS ROM READ THIS:
Like the ROM and want to add or remove anything or customize for yourself use this http://forum.xda-developers.com/showthread.php?t=633246 DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs
CREDITS:
CyanogenMod Team
Google - I used their apps
AOSP - of course
Probably gonna add a changelog here
AOSP 4.2 ROM so quickly? That will be interesting
Can you have some screenshots?
yep its uploaded
it looks just like stock I built it to be at least as good as what you get from google if everything is working correctly that is when I will begin modifying but for now it looks like the stock ROM so I didn't think screenshots would be needed
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Patroy said:
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Click to expand...
Click to collapse
Its solely up to you guys if you want to flash it as this is an expensive hobby for me I'm just sharing what I do with the community so is it worth it, for me yeah, for you I really don't care, I hope I'm not coming off as an ass but I have to draw a line somewhere. I not making any claims with this ROM I just sharing it if you use it fine if not fine, I don't get into the whole screenshots large claims huge changelog thing I just post and share I also maintain this ROM for the Sprint Galaxy Nexus which it has done just fine so if you want you can do a search here and see what and where I come from .......
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
I will happily try your rom to see how it compares to CleanRom, give my feedback tomorrow
Patroy said:
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Click to expand...
Click to collapse
I'm not getting angry with you in fact I agree however, regardless of how you feel about those roms someone still put that effort into them. Honestly for me the N7 is a new device and before I go making claims that my ROM can start your car and end world hunger I want to make sure that it at least meets stock standards. AOSP has done a lot of work to somewhat remove google entries in their code so it has taken me a few days to re-build AOSP code to work correctly with G-APPS and other Google code I do NOT claim to be an over the top developer I just do this as a pastime I have certain things that I do not like and thats why I have started making my own ROMs so that I always get what I want. Now I can tell you this and I know this as a fact THIS IS NOT A WINZIP KITCHEN ROM IT IS BUILT FROM SOURCE it took hella work to get it up to a win zip ROM and thats where we're at so far lol. When I learn all the changes to the 4.2 coding I will start to add small feature to my ROM.
SuperBoUDS said:
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
Click to expand...
Click to collapse
yes it works with TWRP and the information in the About screen is correct
There isn't developer section in setting menu. Is this normal?
SuperBoUDS said:
There isn't developer section in setting menu. Is this normal?
Click to expand...
Click to collapse
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
PAULO76 said:
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
SuperBoUDS said:
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
Click to expand...
Click to collapse
lol who knows I might depends on how things go with this
Installed thid yesterday and so far no problems, nice deep sleep of 96%. Nice work
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
SuperBoUDS said:
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
Click to expand...
Click to collapse
haven't checked for myself but is leankernel updated for 4.2
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.
Android 4.4
S3 builds are focused on being a simple, stable, and "stock-like" experience for your Android device.
View the source code at: http://github.com/jakdillard
----------
Developed by:
Jakdillard
----------
Devices currently supported:
Asus Nexus 7 (2013)
LG Nexus 5
S3 includes modifications to extend the basic functions of Android. With each update to Android, S3 features may change to work with the current version.
Feature list:
- Full Google Experience
- Clear Recents with VM Cache drop
- Reboot In Power menu
- Screenshot In Power menu (enable in developers settings)
- Advanced Reboot options (enable in developers settings)
- Swapped "on click" and "longpress" behavior for WIFI, Mobile network, and BlueTooth tiles
- Init.d support
- SuperSU root
Instructions:
First time flashing device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Fastboot oem unlock > fastboot flash recovery recovery.img.
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Known Issues:
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ and Picasa album viewing. Also I DO NOT USE FACE LOCK SO I DIDN'T INCLUDE IT SINCE I BELIEVE ITS A WASTE OF SPACE.
ROM: Link
G-Apps (INCLUDED)
Follow the above link for the complete source to make your own changes or to completely debug down to the core of the rom also follow my github for detailed changes.
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project.
WANT TO CUSTOMIZE THIS ROM READ THIS:
Want to add or remove anything or customize for yourself use DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs.
Hi. Just installed this and I like it. A few others have been having issues with chrome and location services causing soft reboots and really bad stability. This ROM does not have that problem. I tried first with the full PA gapps and had issues with Google search and the Google calendar FC. Wiped and clean installed and used the Banks gapps. All is good now.
Gonna go install the Elemental X kennel now.
Thanks for the ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app
going to try this and add some tweaks to it get more power of using aosp
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
ridobe said:
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
Click to expand...
Click to collapse
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
I have to look over those other roms sources to see what they are missing more the likely they don't have the location services pointing to the right adapter or still using the old way of making device trees causing make to not put the overlays together correctly.
Nice ROM Jak!
Syncing your Repo now!
Update 10-29-2013
http://d-h.st/RlW
10-29-2013
Added Google Play Edition Bootanimation
Added missing Flo props ( sound should be a little better )
Added missing proprietary DRM
De-Odexed ROM
Update 11-3-2013
Well there a beta quality build of KitKat in the op this will not be a daily driver until I have a complete source to work with and proper proprietary binaries but good luch and enjoy. Also consider this a nightly project as features will slowly be added.
Always under the radar for some reason, but your builds are always fantastic. Great job as always on 4.4. Loving the additional features.
Update 11-6-2013
http://d-h.st/bjj
New update but still no camera
jakdillard said:
http://d-h.st/bjj
New update but still no camera
Click to expand...
Click to collapse
Changes?
dictionary said:
Changes?
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 7 mit Tapatalk 4
dictionary said:
Changes?
Click to expand...
Click to collapse
I know he added a file manager and volume rocker wake. Those two weren't in the OP for the first build.
Sent from my Nexus 7 using Tapatalk 4
Unfortunately flash fails inTwrp 2.6.3.1.
Awesome. Best KitKat ROM of all I have tried so far. Smooth and no fc or other issues at all so far. Stable in tests that other ROMs have failed. Thank you!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Mindrocket said:
Unfortunately flash fails inTwrp 2.6.3.1.
Click to expand...
Click to collapse
I believe twrp has updated to 2.6.3.2
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
Every last person using any 4.4 with the new Google Experience Launcher.
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
I just double tap the home button. It's less annoying.
Love Jack's creations. Keep up the great work and thanks for sharing.