Related
I'd like to modify the stock browser, and was wondering if there is any source code available for it. A quick search returned nothing.
Is this something that is inside the ICS 4.0 source??
here is the official source of the browser https://github.com/android/platform_packages_apps_browser/tree/ics-mr1-release
andrew2511 said:
here is the official source of the browser https://github.com/android/platform_packages_apps_browser/tree/ics-mr1-release
Click to expand...
Click to collapse
You sir, are a gentleman and a scholar!
Many thanks!!!
ics-mr0/ics-mr1 don't have the latest stuff. Master does.
This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw
:/
ported from where? more details..
1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources
not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.
awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know
Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g
What works and what not?
jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.
Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990
After following this tutorial I compiled CM9 for my r800x and everything works fine but since I first compiled I have edited the SystemUI sources. The problem is when I compile it doesn't compile the new sources. Anyone know what I'm doing wrong? Sorry if this is a noob question.
Extra information (not sure if important but might help find the cause):
Using Xubuntu 12.10
Oracle Java 6
I edited /frameworks/base/packages/SystemUI
I compiled for zeusc instead of zeus
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
http://source.android.com/source/initializing.html said:
export OUT_DIR_COMMON_BASE=<path-to-your-out-directory>
Click to expand...
Click to collapse
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Trooper_Max said:
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Click to expand...
Click to collapse
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
bandoncontortion said:
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
Click to expand...
Click to collapse
Cj360 made a zeusc version and uploaded it to fxp cm10 page. I've tested it and it works great
Sent from my Xperia Play (r800x)
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
bandoncontortion said:
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
Click to expand...
Click to collapse
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Changing the timestamp didn't do anything. I'll try deleting the already compiled files and recompile everything over again tomorrow. Also CM10 is a lot better in my opinion too so I'll try it now so hopefully it'll work and fix the problems I'm having.
Trooper_Max said:
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Click to expand...
Click to collapse
CM10 works good on zeusc. Haven't found any bugs and I added the changes to it's SystemUI and it compiled it for me and works great. Thanks for the help!
Announcing PACE and PACE Plus for Find7.
PACE
This is pure AOSP plus with just enough CAF/CM enhancements to get it to run on a variety of hardware.
NOTE!!!
This is only for Find7a right now. I am working on adding support for Find7s. It should be ready in a few days.
Download:
pace44-find7-1.0.rc5.zip
md5=fa2984b63cdcbfab17b4118f397ddb66
Superuser (SuperSU):
superuser.zip
PACE Plus
This includes a few enhancements:
* Built-in SuperSU
* Gesture (swipey) keyboard
* Custom boot animation
* Density (DPI) changer
* Built-in adfree hosts
* Quick settings pulldown
* Torch
* Custom power menu
Planned enhancements:
* Theme support
* No-reboot installer
* ... Other suggestions?
Download:
paceplus44-find7-1.0.rc5.zip
md5=24d12e9aa482ea64d4ec0711af1e3c75
Known Issues:
* Location API (geolocation) used by apps like "Fences" does not work.
Changelog
v1.0rc5
* Initial build for Find7
Source:
github.com/pacerom
Hi, what is the differences between the branch v4.4 and v4.4plus with your source code on Github?
systop said:
Hi, what is the differences between the branch v4.4 and v4.4plus with your source code on Github?
Click to expand...
Click to collapse
The plus branch has the plus code with features listed in the OP.
tdm said:
The plus branch has the plus code with features listed in the OP.
Click to expand...
Click to collapse
I can get it, thank you for your so quick reply.
Then I wonder if I can roll back to 4.4.2? It is because I want to build a 4.4.2 pacerom using cm tree as a base rom to patch other roms like miui
Nice to see you here mate. Your rom on the OGP is excellent and I'm sure you will aim to please here as well
I did download and install an early *unannounced* build of this (before you had the thread up) and it was hard for me to pass the boot ani. I eventually booted in to safe mode and after that initial boot it worked great
*EDIT*
Flashed latest plus just now and it is flying. Would be awesome to have the device specific screen off gestures implemented. Only trouble so far is the AOSP keyboard force closes when swyping for me. Great work mate!
Hello, you can see some screenshots?
the rom is ready so how? does not need gapps? if so what is recommended MINI MODULAR PACKAGE ? thanks
Uanagana said:
Hello, you can see some screenshots?
the rom is ready so how? does not need gapps? if so what is recommended MINI MODULAR PACKAGE ? thanks
Click to expand...
Click to collapse
Im going to make this simple for you; ALWAYS flash gapps mini modular with every rom you ever use (unless you're flashing colorOS). I understand you are very new to XDA and perhaps a language barrier is the cause of some of the confusion (while corresponding with you in other threads)
@uppon2: The keyboard FC when using gestures should have been fixed. This is the fix commit:
https://github.com/pacerom/packages...mmit/9ddfe26215f035da036c620e69688c6721407811
That will depend on jni_unbundled_latinimegoogle existing, of course. It's provided in gapps.
If you have the "official" build with the md5 in the OP and you have gapps installed, I'll re-flash and re-test just to make sure something weird isn't going on.
I was on CM and Gummy for a couple months and I really got addicted to the tap2sleep/tap2wake stuff. I will definitely be trying to put those in soon. The other gesture stuff (circle for camera, vee for torch) may or may not make it in, depending on the amount of change required.
As for gapps, I have been using the CM recommended 20140606 package (linked here: http://wiki.cyanogenmod.org/w/Google_Apps) and it works well. Prior to last month I had been using the 20140105 package and it also worked well.
@Uanagana: Sorry no screen shots, just find a Nexus 5 screen shot and chop out the navbar.
tdm said:
@uppon2: The keyboard FC when using gestures should have been fixed. This is the fix commit:
https://github.com/pacerom/packages...mmit/9ddfe26215f035da036c620e69688c6721407811
That will depend on jni_unbundled_latinimegoogle existing, of course. It's provided in gapps.
If you have the "official" build with the md5 in the OP and you have gapps installed, I'll re-flash and re-test just to make sure something weird isn't going on.
I was on CM and Gummy for a couple months and I really got addicted to the tap2sleep/tap2wake stuff. I will definitely be trying to put those in soon. The other gesture stuff (circle for camera, vee for torch) may or may not make it in, depending on the amount of change required
Click to expand...
Click to collapse
I was reporting on the keyboard that is present in the rom. I had not flashed gapps at this stage so I'm assuming that will fix the problem.
I'm glad you're considering screen off gestures! Thank you
There are some duplicated ringtones in media and only difference is the letter case.
systop said:
There are some duplicated ringtones in media and only difference is the letter case.
Click to expand...
Click to collapse
I definitely see some weirdness with duplicated ring tones. Which ones do you see?
This may or may not be an aosp issue. I'll need to investigate.
tdm said:
I definitely see some weirdness with duplicated ring tones. Which ones do you see?
This may or may not be an aosp issue. I'll need to investigate.
Click to expand...
Click to collapse
Here is the list of duplicated ringtones:
arcturus.ogg vega.ogg Andromeda.ogg CanisMajor.ogg Perseus.ogg UrsaMinor.ogg hydra.ogg
Thanks for your rom, I have successfully patched a MIUI V5 4.4.4
Looks promising can't wait for find7 support thanks tdm
Here is my question, why do you remove the useful oppo custom setting from the CM tree?
systop said:
Here is my question, why do you remove the useful oppo custom setting from the CM tree?
Click to expand...
Click to collapse
I did not remove anything. I have my own tree and I am only adding things that are related to hardware support.
Which setting do you mean?
tdm said:
I did not remove anything. I have my own tree and I am only adding things that are related to hardware support.
Which setting do you mean?
Click to expand...
Click to collapse
You seems to remove the configpanel for common oppo phones which is included in cm tree
systop said:
You seems to remove the configpanel for common oppo phones which is included in cm tree
Click to expand...
Click to collapse
Ah yes the cmhw things. Is the anything in particular you want from that panel?
tdm said:
Ah yes the cmhw things. Is the anything in particular you want from that panel?
Click to expand...
Click to collapse
No, this config panel is not useful to me, and I only wonder if this panel is not compatible with the aosp?
systop said:
No, this config panel is not useful to me, and I only wonder if this panel is not compatible with the aosp?
Click to expand...
Click to collapse
I could add it if there is a need. But I have never wanted it myself.
Hi, I find that you add a kernel boot parameter: androidboot.selinux=permissive
I want to know why you add this? Is there any compatible issue with selinux between cm and pace?
Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!
ViperXvenom8888 said:
Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!
Click to expand...
Click to collapse
Just build it from source then you wont have this issue.
zelendel said:
Just build it from source then you wont have this issue.
Click to expand...
Click to collapse
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue
ViperXvenom8888 said:
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue
Click to expand...
Click to collapse
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.
zelendel said:
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.
Click to expand...
Click to collapse
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)
ViperXvenom8888 said:
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)
Click to expand...
Click to collapse
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.
zelendel said:
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.
Click to expand...
Click to collapse
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks
ViperXvenom8888 said:
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks
Click to expand...
Click to collapse
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.
zelendel said:
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.
Click to expand...
Click to collapse
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?
ViperXvenom8888 said:
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?
Click to expand...
Click to collapse
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.
zelendel said:
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.
Click to expand...
Click to collapse
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!
ViperXvenom8888 said:
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!
Click to expand...
Click to collapse
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.
zelendel said:
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.
Click to expand...
Click to collapse
Alright. Thanks a lot for all the information you have provided me!