{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warning:
I am not responsible for anything you do to your phone
THIS GUIDE IS VERY OUTDATED AND NOT PROPER. I'M VERY BUSY AND DON'T EVEN BUILD MY OWN ROMS ANYMORE. I'LL UPDATE WITH A NEW METHOD WHEN I HAVE TIME TO RESEARCH ONE.
This is all infromation i recieved from atc3030 so please stop by his profile and hit that beautiful thanks button. I am posting this after numerous requests from people on how to compile ROMs with the Linaro toolchain
What you'll need
Basic knowledge of how to compile a ROM
Common Sense
Fingers to stop by atc3030 profile to thank him.
Read Through instructions once before executing, there short so don't complain.
Lets Get Started!
Navigate To Root Of Your Source In Terminal
Run: "cd prebuilts/gcc/linux-x86/arm/"
Run:
ICS "wget http://releases.linaro.org/12.07/components/android/toolchain/4.7/android-toolchain-eabi-linaro-4.7-2012.07-3-2012-06-19_14-52-07-linux-x86.tar.bz2"
JB "wget http://releases.linaro.org/12.11/components/android/toolchain/4.7/android-toolchain-eabi-linaro-4.7-2012.11-1-2012-11-16_21-55-58-linux-x86.tar.bz2"
Run: "bunzip2 *.tar.bz2"
Run: "tar -xvf *.tar"
In Your File Browser Navigate To Root Folder Of Your Source
Navigate To ~/build
Open envsetup.sh In Your Favorite Text Editor
Modify The Arm Toolchain Line To Reflect Your Linaro Folder (Check Picture)
Now: Enjoy :]
I will try to keep toolchain links updated. If one is released without me updating the post then PM me.
Was just looking for this. Will let you know how it goes.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
You are awesome!!! Thanks for this Post!!!
Sent from my Galaxy Nexus using xda app-developers app
i dont think it is necesary to
run
rm arm-l
dont think it makes a difference
plus
just tried it to double check....
says its not even found....the file anyway
when you add the linaro toolchain files into the folder. the arm-linux file need to be deleted (tahts the old toolchain).
I installed the toolchain system-wide. Build it from src/create a pkg for your package manager, install. Point build system to it.
Thanks for the time spent creating this thread, but this is a rather hackish way of doing it.
Sent from my i9250
bk201doesntexist said:
I installed the toolchain system-wide. Build it from src/create a pkg for your package manager, install. Point build system to it.
Thanks for the time spent creating this thread, but this is a rather hackish way of doing it.
Sent from my i9250
Click to expand...
Click to collapse
if you have a better way PM me, ill add things in and edit things (with your name by it ofcourse lol)
Awesome, been looking for such ressource for a while now :good:
Thanks a lot
updated with lastest toolchain. thanks androidguide for the heads up
Thanks was waiting for this!
Sent from my GT-I9000 using xda premium
Dri94 said:
when you add the linaro toolchain files into the folder. the arm-linux file need to be deleted (tahts the old toolchain).
Click to expand...
Click to collapse
Where would that file be? Have been building for a while, but never messed with the toolchain before.
There are some in ndk/toolchains and more in external/valgrind/main/exp-bbv/tests
apascual89 said:
Where would that file be? Have been building for a while, but never messed with the toolchain before.
There are some in ndk/toolchains and more in external/valgrind/main/exp-bbv/tests
Click to expand...
Click to collapse
Prebuilts toolchain. Sane place you d download the file to
____________________________________________________________
"A foot is the ultimate stocking stuffer."
Ok so i was informed that 4.2 changes everything, if you know enough then simply putting the files in the new toolhain folder (prebuilts,gcc,arm) is enough though dirtier and more hacksih then this method. I will be updating the OP once i find a cleaner method
Is it just a matter of replacing /prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 with the android-toolchain-eabi directory from the Linaro archive (renaming it to arm-eabi-4.6)? Or is there more to it than that?
How would we go back if we dont like the results?
KaosMcRage said:
Is it just a matter of replacing /prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 with the android-toolchain-eabi directory from the Linaro archive (renaming it to arm-eabi-4.6)? Or is there more to it than that?
Click to expand...
Click to collapse
Yes you can do that. I was trying to get it to point to the 4.7 since that is Lindsay. I think is just modifying the envsetup
KBizzle said:
How would we go back if we dont like the results?
Click to expand...
Click to collapse
What's there not to like? I guess you could Google the default toolchain
edit: if you followed instructions you can just rename the .old file back to regular, and delete the linaro
____________________________________________________________
"A foot is the ultimate stocking stuffer."
Dri94 said:
Yes you can do that. I was trying to get it to point to the 4.7 since that is Lindsay. I think is just modifying the envsetup
What's there not to like? I guess you could Google the default toolchain
edit: if you followed instructions you can just rename the .old file back to regular, and delete the linaro
____________________________________________________________
"A foot is the ultimate stocking stuffer."
Click to expand...
Click to collapse
I did read it. Just lost track of the steps and wanted to make sure.
Sent from my SCH-I605 using Tapatalk 2
Dri94 said:
Yes you can do that. I was trying to get it to point to the 4.7 since that is Lindsay. I think is just modifying the envsetup
Click to expand...
Click to collapse
I tried replacing the arm-eabi-4.6 directory like I mentioned above, but I'm not convinced it actually used it. No way to tell, I suppose? Maybe I'll just wait til you have the cleaner method. Thanks for your efforts in this thread, by the way.
Dri94 said:
What's there not to like? I guess you could Google the default toolchain
edit: if you followed instructions you can just rename the .old file back to regular, and delete the linaro
Click to expand...
Click to collapse
Also, a 'repo sync' should wipe it out and revert to the default toolchain in whatever you're building.
KaosMcRage said:
I tried replacing the arm-eabi-4.6 directory like I mentioned above, but I'm not convinced it actually used it. No way to tell, I suppose? Maybe I'll just wait til you have the cleaner method. Thanks for your efforts in this thread, by the way.
Also, a 'repo sync' should wipe it out and revert to the default toolchain in whatever you're building.
Click to expand...
Click to collapse
It used it if you did it right. There is no other toolchain for it to use lol. It looks in a location to find the toolchain. Add .bak to the end of the folder and it won't be able to locate the toolchain.... Repo sync doesn't effect it. Although it might in the future based on some open commits I saw
____________________________________________________________
"A foot is the ultimate stocking stuffer."
Dri94 said:
It used it if you did it right.
Click to expand...
Click to collapse
Depends on what "did it right" means, I guess. In /prebuilts/gcc/linux-x86/arm, I replaced the arm-eabi-4.6 directory with the renamed android-toolchain-eabi directory from the linaro archive.
Dri94 said:
There is no other toolchain for it to use lol. It looks in a location to find the toolchain. Add .bak to the end of the folder and it won't be able to locate the toolchain....
Click to expand...
Click to collapse
I'm not so sure that's true, at least in the case of the folder I mentioned earlier (/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6). I just blew that directory away completely (arm-eabi-4.6) and compiled. It built just fine. So, maybe that isn't the folder it's looking at in 4.2?
Dri94 said:
Repo sync doesn't effect it. Although it might in the future based on some open commits I saw
Click to expand...
Click to collapse
Maybe that varies based on which ROM you're building, but in AOKP a 'repo sync' will overwrite some files in that directory and repopulate missing ones. Again though, we might be looking at the wrong directory for 4.2.
Related
Updated for CM9 Alpha 5-pre1
flashable zip this time
https://dl.dropbox.com/u/8566596/CM9-PreAlpha5-NavBar.zip *note for alpha5-pre1 only*
[notes for simple disable]
Edit a quick way to disable this mod without reflashing rom is to edit your build prop
Add this line to your /system/build.prop: qemu.hw.mainkeys=1 and reboot
I use Rom Toolbox for this, make the changes, save and reboot. Rom Toolbox will save your original build.prop as build.prop.bak and you can restore it to turn it back on.
What can we use because I really need this... Can you gave me a file to enable it and disable it?
Thanks
deedscreen said:
What can we use because I really need this... Can you gave me a file to enable it and disable it?
Thanks
Click to expand...
Click to collapse
I agree, my hard keys go haywire from time to time, I'd like to turn them off and still be able to use theme chooser..
Sent from my SPH-D710 using Tapatalk 2
drleo1 said:
I agree, my hard keys go haywire from time to time, I'd like to turn them off and still be able to use theme chooser..
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
That should actually work but it's from alpha 3 build and I have not had the time to do it again on alpha 4.
update here you go updated, now sleep time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://dl.dropbox.com/u/8566596/framework-res.zip
Code:
extract the zip get framework-res.apk
push to phone
adb root
adb remount
adb push framework-res.apk /system/framework
adb reboot to restart phone *note my phone jumped to bootanimation screen right after framework-res.apk is pushed, didn't go past it, but adb reboot or pretty sure hard reboot gets you back in*
Other ways to install this is to replace this file into the rom zip and reflash or I'm sure you can edit gapps.zip to flash this also.
I had done this on my current framework-res.apk and it worked fine, then I redid it again from framework-res.apk from cm9 alpha 4 which I pulled from the zip. I have not tested but it should work.
As always make a backup first.
hey man where can I get the nightlies for CM9? havent been able to locate them anywhere?! even tried the IRC with no luck
This worked beautifully, thanks again
im0rtalz said:
update here you go updated, now sleep time
https://dl.dropbox.com/u/8566596/framework-res.zip
Code:
extract the zip get framework-res.apk
push to phone
adb root
adb remount
adb push framework-res.apk /system/framework
adb reboot to restart phone *note my phone jumped to bootanimation screen right after framework-res.apk is pushed, didn't go past it, but adb reboot or pretty sure hard reboot gets you back in*
Other ways to install this is to replace this file into the rom zip and reflash or I'm sure you can edit gapps.zip to flash this also.
I had done this on my current framework-res.apk and it worked fine, then I redid it again from framework-res.apk from cm9 alpha 4 which I pulled from the zip. I have not tested but it should work.
As always make a backup first.
Click to expand...
Click to collapse
This is off-topic but what icons are those in your screenshot? They look hawt
iniz94 said:
This is off-topic but what icons are those in your screenshot? They look hawt
Click to expand...
Click to collapse
http://marcarnal.deviantart.com/art/SAMARA-Icons-296032324
I pulled it out from the mtz file. Just rename mtz to zip and you should be able to extract the icons.
TeamERA said he will begin making this mod again for the newest build of CM9a4 soon. Since its always better to make the mod for the current buold just incase something changes.
Sent from a phone running a custom ROM with kNOw CiQ...
MrTimz said:
TeamERA said he will begin making this mod again for the newest build of CM9a4 soon. Since its always better to make the mod for the current buold just incase something changes.
Sent from a phone running a custom ROM with kNOw CiQ...
Click to expand...
Click to collapse
my second link is made with cm9a4
Been wanting to get this on cm9 sweet.
Sent from my SPH-D710 using Tapatalk
What changes to the framework-res.apk to enable this mod. Seems like it would be easier to just make a flashable zip that changes the necessary files and allows it to be compatible with all future builds.
Decompile framework-res/ res/values/bools.xml
config_showNavigationBar = true
And you can change the dimensions if you like in values/dimesions.xml. You may need to change the images if you make it to small.
Sent from a phone running a custom ROM with kNOw CiQ...
MrTimz said:
Decompile framework-res/ res/values/bools.xml
config_showNavigationBar = true
And you can change the dimensions if you like in values/dimesions.xml. You may need to change the images if you make it to small.
Sent from a phone running a custom ROM with kNOw CiQ...
Click to expand...
Click to collapse
Just found it, thanks. What height would you suggest changing it to?
brooksyx said:
What changes to the framework-res.apk to enable this mod. Seems like it would be easier to just make a flashable zip that changes the necessary files and allows it to be compatible with all future builds.
Click to expand...
Click to collapse
I just prefer pushing the files but I made an update.zip for now. No way to make it work on all future builds due to framework changes in CM9.
brooksyx said:
Just found it, thanks. What height would you suggest changing it to?
Click to expand...
Click to collapse
If you make it too small you have to update the images in systemUI also I believe, I seen most do either 37 or 34
im0rtalz said:
If you make it too small you have to update the images in systemUI also I believe, I seen most do either 37 or 34
Click to expand...
Click to collapse
I just did a build with 38, ill see how that turns out.
iniz94 said:
This is off-topic but what icons are those in your screenshot? They look hawt
Click to expand...
Click to collapse
This is off topic but how do u get those icons! And how do u put them on cm9!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As The Name Suggest This To0l Will Create An OTA Update Package For You,
It Doesn't Work Like The Actually OTA Packages Due To The Nature Of Custom ROM And Their Customization Ability,
Making patching near to impossible,however this will scan to folder and compare them,
picking the differences, creating a new OTA Folder, which you just zip and broadcast.
The Advantage Of Using This Tool Are SimpleSmaller Update Packages,
Faster Upload From The Dev,
Faster Download For the User,
It's Also Allows user to update without having to reflash stock kernel, as the modules (if they're the same) wouldn't be included,
It's Also Allow You To See The Actual Difference between each updates
Updates:Initial Release V1.0: Simple OTA Maker
Update V1.2:
Bug Fix
Update V1.1:
Logger Will Show An Error Should One Occurs
Exceptions (These Will Not Be Compared But Will Be Copied)
Upcoming Updates:
SuggestionsAll Suggestion are welcome
Notice:
1) For Aroma Users I highly Recommend that after using the tool to copy and paste that folder yourself,
usually Aroma options don't change and thus ignored by this app
2) The Same Apply To the update binary
3) If You Use This App, Please Credit, There is no need to tell me but i'd like to know
4) Some ROM format the /system partition before installing the ROM, if so make sure to comment out that line
5) I'd Highly Recommend You test the OTA package before publishing it
DOWNLOAD HERE
Look @ The 2nd Post For A Quick How To.
How To Use1) Extract The Old ROM (v1) Into A Folder And Place The Folder Into The "ROM" Folder
2) Extract The Updated ROM (v2) Into A Folder And Place The Folder Into The "ROM" Folder
3) Run The Tool & Click Refresh
4) Choose The Old ROM 1st & Then The 2nd ROM
5) Select A Name For Your OTA Folder
6) Click Process & Wait For The Magic To Happen
7) Now A Folder Will Be Created With The Name You Specified & Placed In The OTA Folder
8) Now You "Probably" Need To Edit The Binary Script To Make Sure It Works Correctly,
^^ You Won't/Shouldn't Remove/Edit Symlink/Chmod Or Extract Unless They Specify A Specific File
Awesome gonna use them for my roms....
Real Steel
razer1224 said:
Awesome gonna use them for my roms....
Real Steel
Click to expand...
Click to collapse
Great,
Let me know if you run into any problems.
thunder07 said:
Great,
Let me know if you run into any problems.
Click to expand...
Click to collapse
SURE!
Real Steel
what a great idea OP, my congratulations I'll try it asap, thx a lot:good:
Awesome idea. Nice one. Would be useful if the devs that use this have a script to remove any .dex incase the ota receiver has reodexed their rom. But that's another matter.
Thanks, that is amazing!
You do love making it easy for everyone
Sent from my HTC One X using xda premium
joewong1991 said:
You do love making it easy for everyone
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm cool like that
Sent from my HTC One X
backfromthestorm said:
Awesome idea. Nice one. Would be useful if the devs that use this have a script to remove any .dex incase the ota receiver has reodexed their rom. But that's another matter.
Click to expand...
Click to collapse
thats a different story,
though i'm not yet 100% yet sure if odex apk/jar are interchangable, but let say they are,
this would work the same way,
and i doubt a dev would release 2 roms an odex and deodexed, but thats a the cooks problem not mine
Update V1.1
Update V1.1:
Logger Will Show An Error Should One Occurs
Exceptions (These Will Not Be Compared But Will Be Copied)
Update Is In The 1st Post
This looks awesome! Will try it out when I mess with ROM development again!
You made it on the News Portal btw
http://www.xda-developers.com/android/cut-rom-transfer-time-with-ota-creator/
hasoon2000 said:
This looks awesome! Will try it out when I mess with ROM development again!
You made it on the News Portal btw
http://www.xda-developers.com/android/cut-rom-transfer-time-with-ota-creator/
Click to expand...
Click to collapse
haha sweet thanks for let me know
cant get the roms to show up in the app
ayysir said:
cant get the roms to show up in the app
Click to expand...
Click to collapse
you must extract the rom into a folder inside the "ROM" folder
Failed To Copy
Process Took 1 Minutes And 7 Seconds
window 7 ( run as administrator )
cm10 nightly updaet
li9ht said:
Failed To Copy
Process Took 1 Minutes And 7 Seconds
window 7 ( run as administrator )
cm10 nightly updaet
Click to expand...
Click to collapse
an empty exception list broke the whole app....
Fixed And Uploaded
would be great that this app also automatically creates a flashable zip and signs it
yeah great app.
but how does it compare?? on filesize, date or how?
I just tried to compare rom 1.0 with rom 1.1 and it gave me update on almost all system apks but they are the same date and size??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For general discussions, bug reports and FAQ, write HERE!
This topic aims to be a tools collection to be used for roms MMB, as expansions and plugins.
Downloads:
MoltenMotherBoard | GoogleCode
----- NOT-ACCORDING-WITH-ANDROID-VERSIONS:
EXT4 Formatter [D]
INIT.D support Activator [D]
----- Android 2.3
Gapps [D]
----- Android 4.0
----- Android 4.1 / 4.2
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, p4c0_00, ItachiSama
mackief said:
Here are a lot of BUILD.PROP tweaks for GIO users, made by me during this year.
Lot of them are not tested. Needed someone that can do it!
This evening I'll modify this post adding a guide to how add it on your phone.
Click to expand...
Click to collapse
i can test .. shall i use the cm7 from marcin oh android i dont have much time now porting P.A
hi i am battery spammer
I am glad to be causing this issue
ha ha ha ha
m.ali.ozkaya said:
hi i am battery spammer
I am glad to be causing this issue
ha ha ha ha
Click to expand...
Click to collapse
HAHAHAHAHAHA :3 okay sry :')
Check out this http://forum.xda-developers.com/showpost.php?p=31952053&postcount=45
marcin1147 said:
Check out this http://forum.xda-developers.com/showpost.php?p=31952053&postcount=45
Click to expand...
Click to collapse
Ty dude. Check out other tweaks to add and remove.
Thanks for your help!
Also ro.media.panorama is useless for Gio
Dont think 5 fingers fit my screen really, and isnt supportive neither...
Good list though, should have a look at ace thread except camera tweaks, and maybe add flashable zips from multiple roms (cm7/9/10 and some stock 2.3.6) to make it easier?!
Sent from my GT-S5660 using xda app-developers app
voetbalremco said:
Dont think 5 fingers fit my screen really, and isnt supportive neither...
Good list though, should have a look at ace thread except camera tweaks, and maybe add flashable zips from multiple roms (cm7/9/10 and some stock 2.3.6) to make it easier?!
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
I thought about it, but in build.prop there are important lines for the rom info.
How can I only add few lines in that file, without deleting anything?
mackief said:
I thought about it, but in build.prop there are important lines for the rom info.
How can I only add few lines in that file, without deleting anything?
Click to expand...
Click to collapse
Use build.prop from every rom and just add the lines, a file in updateracript will always overwrite so you need much versions. ...
But I think you can experiment a bit and try to implent them all into 1 flashable zip with aroma installer to choose the right build.prop for the right rom..
Sent from my GT-S5660 using xda app-developers app
voetbalremco said:
Use build.prop from every rom and just add the lines, a file in updateracript will always overwrite so you need much versions. ...
But I think you can experiment a bit and try to implent them all into 1 flashable zip with aroma installer to choose the right build.prop for the right rom..
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
In this way I should make thousand packages, one for all GIO's roms... I've to find another way...
For the INIT.D tweaks there's no problem, but for build.prop tweaks is different...
voetbalremco said:
Use build.prop from every rom and just add the lines, a file in updateracript will always overwrite so you need much versions. ...
But I think you can experiment a bit and try to implent them all into 1 flashable zip with aroma installer to choose the right build.prop for the right rom..
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
In this way I should make thousand packages, one for all GIO's roms... I've to find another way...
For the INIT.D tweaks there's no problem, but for build.prop tweaks is different...
mackief said:
In this way I should make thousand packages, one for all GIO's roms... I've to find another way...
For the INIT.D tweaks there's no problem, but for build.prop tweaks is different...
Click to expand...
Click to collapse
not completely true
you can use all latest stock 2.3.6 as almost all of them are based on 2.3.6 wich are about 5, 6 or something , and latest cm7, phiexz, marcins, cm9/10.
its quite some work though, but copy paste method is also not optimal...
voetbalremco said:
not completely true
you can use all latest stock 2.3.6 as almost all of them are based on 2.3.6 wich are about 5, 6 or something , and latest cm7, phiexz, marcins, cm9/10.
its quite some work though, but copy paste method is also not optimal...
Click to expand...
Click to collapse
The only problem is that in this way all roms lose their specific info: developer, rom, date, fingerprint, etc...
Sent from my GIO running DebianDroid LENNY
How and where can I use these commands??(init.d)
m.ali.ozkaya said:
How and where can I use these commands??(init.d)
Click to expand...
Click to collapse
Two ways:
- Typing them in Terminal Emulator app;
- Using ADB shell.
Sent from my GIO running DebianDroid LENNY
mackief said:
The only problem is that in this way all roms lose their specific info: developer, rom, date, fingerprint, etc...
Sent from my GIO running DebianDroid LENNY
Click to expand...
Click to collapse
well thats true, but I think they"ll know wich rom they are using, hmm?
I think you need the different build.props for stock roms ecause of fingerprint, you can change build number, thats just a name. but fingerprint is different in another stock rom, so is buildnummer, but in custom roms it is changed so that wont affect the booting process, but fingerprint will....
I dont think theres a method in flashing to "add" these lines so the easiest way is just to keep it for copy-paste usage...
voetbalremco said:
well thats true, but I think they"ll know wich rom they are using, hmm?
I think you need the different build.props for stock roms ecause of fingerprint, you can change build number, thats just a name. but fingerprint is different in another stock rom, so is buildnummer, but in custom roms it is changed so that wont affect the booting process, but fingerprint will....
I dont think theres a method in flashing to "add" these lines so the easiest way is just to keep it for copy-paste usage...
Click to expand...
Click to collapse
Mmmh. So the easiest way is to make one package for each rom"s fingerprints? Well, I could do it.
I'll add new tweaks and then I'll try to apply them by flashing!
Sent from my GIO running DebianDroid LENNY
$ export PATH=/data/local/bin:$PATH
$echo ....any code..
"Cannor create ...... permision denied"
$
m.ali.ozkaya said:
$ export PATH=/data/local/bin:$PATH
$echo ....any code..
"Cannor create ...... permision denied"
$
Click to expand...
Click to collapse
You have done su first in terminal?
Sent from my GT-S5660 using xda premium
No responsibility taken for any bricked device. Use it at your own risk
Updated with How to.
Hi,
there is a new driver for Android JB on the Qualcomm website.
It is running fine on my Optimus LTE (Nitro HD equivalent by NTT) with CM10.1.
I wont upload the files cause they are copyrighted.
You have only to create an account and wait 2 minutes to download the drivers for yourself.
I do not know what was fixed. But I have encoutered the blue flickering bug with this driver too...
https://developer.qualcomm.com/download/Adreno200-AU_LINUX_ANDROID_JB_VANILLA_04.02.02.060.053.zip
There was an another driver released earlier (4.april). I have not tested it though. Could be incompatible like the last one.
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
There is a CWM ZIP attached, You have to copy all folders inside system from the qualcomm driver zip to the folder system inside the CWM ZIP. I recommend to use the latest Winrar, to minimize the risk of your ZIP getting corrupted.
Now flash and wipe cache/dalvik.
How To with Winrar:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It will ask you about the parameters of the new zip. Do not change anything and press ok.
Thanks for sharing, and good job making a nice cwm zip template. Very helpful!
+thanks
Sent from my LG-P930 using Tapatalk 2
Dumb question with some repititon but this means we should:
unzip both files
Copy contents of download
Paste into template
Zip template
Copy to /sdcard
Boot into recovery
Flash
Wipe cache/dalvik
???????????????
This did not work for me.
[NOTE] I am using TWRP 2.5
lbomber7 said:
Dumb question with some repititon but this means we should:
unzip both files
Copy contents of download
Paste into template
Zip template
Copy to /sdcard
Boot into recovery
Flash
Wipe cache/dalvik
???????????????
This did not work for me.
[NOTE] I am using TWRP 2.5
Click to expand...
Click to collapse
Assuming you are running Windows, it is easiest if you use 7zip to merge the files into the template zip.
Extract the driver zip file
Browse into the extracted folder to the 'system' directory
Go open the template adreno.zip with 7zip in another window
Drag the contents of the extracted 'system' folder into the system folder in the 7zip window.
Exit 7zip, and you're done.
http://www.7-zip.org/download.html
Thanks. I was using 7zip but ya, the drag drop thing works a lot easier and better than un and rezipping.
mpsantiago said:
Assuming you are running Windows, it is easiest if you use 7zip to merge the files into the template zip.
Extract the driver zip file
Browse into the extracted folder to the 'system' directory
Go open the template adreno.zip with 7zip in another window
Drag the contents of the extracted 'system' folder into the system folder in the 7zip window.
Exit 7zip, and you're done.
http://www.7-zip.org/download.html
Click to expand...
Click to collapse
You can also just use xplore available on the play store for free and just copy the files into adreno.zip and install. Easy as pie no computer needed.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You can also just use xplore available on the play store for free and just copy the files into adreno.zip and install. Easy as pie no computer needed.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Thats what i use too. Works amazing.
Sent from my LG-P930 using Tapatalk 2
NFleck said:
Thats what i use too. Works amazing.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Could you create the zip for su640 please
If you flash this and then go into build.prop and change debug.composition.type to c2d it seems to make the UI smoother.
Can somebody else also try it and confirm whether it is just placebo or not?
I also set windowsmgr.max_events_per_sec to 60
mpsantiago said:
If you flash this and then go into build.prop and change debug.composition.type to c2d it seems to make the UI smoother.
Can somebody else also try it and confirm whether it is just placebo or not?
I also set windowsmgr.max_events_per_sec to 60
Click to expand...
Click to collapse
Made no difference for me. Before Adrino, after Adrino, and after moding the build.prop file. All very fluid.
Sent from my LG-P930 using xda app-developers app
mpsantiago said:
If you flash this and then go into build.prop and change debug.composition.type to c2d it seems to make the UI smoother.
Click to expand...
Click to collapse
Ok, I just discovered a real, repeatable (I think) improvement from doing the above.
On a fresh flash of the latest PAC (and CM10.1 also I believe) open the YouTube app and start playing a video, preferably in full screen. While it is playing, attempt to use one of the on-screen youtube menus (share, etc). You'll notice the options in the menu are distorted.
Now, flash the new Adreno driver and change debug.composition.type to c2d (from dyn). Do the same youtube test again- menu options are clear.
I bet this not only fixes the issue in YouTube, but in other apps that use overlays on video or other complex backgrounds.
mpsantiago said:
Ok, I just discovered a real, repeatable (I think) improvement from doing the above.
On a fresh flash of the latest PAC (and CM10.1 also I believe) open the YouTube app and start playing a video, preferably in full screen. While it is playing, attempt to use one of the on-screen youtube menus (share, etc). You'll notice the options in the menu are distorted.
Now, flash the new Adreno driver and change debug.composition.type to c2d (from dyn). Do the same youtube test again- menu options are clear.
I bet this not only fixes the issue in YouTube, but in other apps that use overlays on video or other complex backgrounds.
Click to expand...
Click to collapse
Thanks:good:
It's better now. Will see if anymore glitches+BSODs.
This problem is really annoying.
It happens after some msm: rotator kernel changes (Apr 24, 2013).
I had tried to revert the changes, but doesn't work. I dunno what CM did with the ROM.
mpsantiago said:
Ok, I just discovered a real, repeatable (I think) improvement from doing the above.
On a fresh flash of the latest PAC (and CM10.1 also I believe) open the YouTube app and start playing a video, preferably in full screen. While it is playing, attempt to use one of the on-screen youtube menus (share, etc). You'll notice the options in the menu are distorted.
Now, flash the new Adreno driver and change debug.composition.type to c2d (from dyn). Do the same youtube test again- menu options are clear.
I bet this not only fixes the issue in YouTube, but in other apps that use overlays on video or other complex backgrounds.
Click to expand...
Click to collapse
When I open YouTube, open a video on HQ, then rotate to landscape/full screen, all the menus work great except share is kinda bright but I can still clearly see the menu. In what way is it distorted?
Cm10.1 rc1 + wind 2.01
Sent from my LG-P930 using Tapatalk 2
NFleck said:
When I open YouTube, open a video on HQ, then rotate to landscape/full screen, all the menus work great except share is kinda bright but I can still clearly see the menu. In what way is it distorted?
Cm10.1 rc1 + wind 2.01
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Mine would sometimes become blotches of random color. Sometimes I would get a lockup as well.
mpsantiago said:
Mine would sometimes become blotches of random color. Sometimes I would get a lockup as well.
Click to expand...
Click to collapse
I keep getting these random reboots with this driver. Anyone else?
Sent from my LG-P930 using xda app-developers app
installing new driver means?
---------- Post added at 11:20 PM ---------- Previous post was at 11:15 PM ----------
And does this work with MIUI V5 3.5.24 Official (from original chinese MIUI)? It's JB.
Swetnes said:
I keep getting these random reboots with this driver. Anyone else?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I've actually been starting to get random reboots even without this.. You running cm nightlys with wind?
Sent from my LG-P930 using Tapatalk 2
Initially i was getting high frecuencies, about 1512 MHz, but it lasted just like 7min, now its ok, seems promising.
Thanks.
ultimate_neet said:
Initially i was getting high frecuencies, about 1512 MHz, but it lasted just like 7min, now its ok, seems promising.
Thanks.
Click to expand...
Click to collapse
Not sure what you mean... The kernel sets the processor to clock up when needed in one way or another with most performance settings. Nothing wrong with that.
If you're referring to something else opp lease explain..
emperorisuka said:
installing new driver means?
---------- Post added at 11:20 PM ---------- Previous post was at 11:15 PM ----------
And does this work with MIUI V5 3.5.24 Official (from original chinese MIUI)? It's JB.
Click to expand...
Click to collapse
I think any rom based on cm10.1 (iirc: all jb ROMs for p930) would work, however, some may contain custom changes to settings (miroslav_mm's ROM for example) to which this may overwrite; effectively negating many features of that ROM. Best to check with the specific author, or at least the list of changes to see whether or not it contains adreno drivers and/or changes that this may overwrite.
Sent from my LG-P930 using Tapatalk 2
Hey guys, here's the source for my new application launcher. This launcher looks and feels like it belongs in Glass. The feedback I've received so far has been awesome, and I'd love to hear what you guys think.
http://github.com/justindriggers/Glass-Launcher
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Props to Michael DiGiovanni and launchy for figuring things out long before the GDK release.
Apk
Tried compiling the apk from your source but it failed once sideloaded onto glass. Any chance you could provide the .apk?
please post apk for testing
Yeah, source isn't compiling correctly. Please post complete source, or provide the app.
GSLEON3 said:
Yeah, source isn't compiling correctly. Please post complete source, or provide the app.
Click to expand...
Click to collapse
It compiled fine for me, though I had to do some tweaking in Eclipse.
I was getting the following:
[2013-12-16 22:21:03 - Dex Loader] Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
[2013-12-16 22:21:03 - GlassLauncher] Conversion to Dalvik format failed: Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
In order to fix it, I had to do two things (assuming that you've already installed the GDK sneak peak via the Android SDK)....
1. Right click on the project >> go to Android Tools >> click on "Add Support Library"
2. At the top of Eclipse, click on Project >> Clean >> selected my project and cleaned it.
Once that was done I was able to run it and have it sideload onto my Glass that I had plugged into the laptop.
Hope that helps.
mybrotherischad said:
It compiled fine for me, though I had to do some tweaking in Eclipse.
I was getting the following:
[2013-12-16 22:21:03 - Dex Loader] Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
[2013-12-16 22:21:03 - GlassLauncher] Conversion to Dalvik format failed: Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
In order to fix it, I had to do two things (assuming that you've already installed the GDK sneak peak via the Android SDK)....
1. Right click on the project >> go to Android Tools >> click on "Add Support Library"
2. At the top of Eclipse, click on Project >> Clean >> selected my project and cleaned it.
Once that was done I was able to run it and have it sideload onto my Glass that I had plugged into the laptop.
Hope that helps.
Click to expand...
Click to collapse
@mybrotherischad , Thanks! That did it. I had the GDK & I can't figure out why, but cleaning seemed to make the difference. Maybe something was hung up.
can either of you pls post or send a pm to the .apk for a non-programmer explorer?
Not working on EX12
Loved this launcher amazing work. No longer works on EX12 for me.
Edit:
Works now with patch from post #11
The best sideloaded app launcher on glass!
Now working on EX12
GSLEON3 said:
@mybrotherischad , Thanks! That did it. I had the GDK & I can't figure out why, but cleaning seemed to make the difference. Maybe something was hung up.
Click to expand...
Click to collapse
The issue was tracked on my GitHub as well, apparently downgrading the Android Build Tools to 18.1.1 was a workaround, but 19.0.1 is out now and it seems to have fixed the problem altogether.
JohnShaft69 said:
can either of you pls post or send a pm to the .apk for a non-programmer explorer?
Click to expand...
Click to collapse
Unfortunately, Google's GDK developer policies state that, "You may not publish or distribute Glassware outside of the official Google-hosted Google Mirror API Client and GDK application distribution channel, unless otherwise approved in writing by Google."
I don't want to risk anything this early on, but I'm sure someone out there would be happy to compile it for you.
thet1nman said:
Loved this launcher amazing work. No longer works on EX12 for me.
Click to expand...
Click to collapse
Fixed in the latest commit.
JohnShaft69 said:
can either of you pls post or send a pm to the .apk for a non-programmer explorer?
Click to expand...
Click to collapse
If I have some free time tonight I'll try to compile it for u (although iv never done it b4 so now I'll learn so that I Dont have an issue if I need to compile my own code soon)
Sent from my SPH-D710 using Tapatalk
JohnShaft69 said:
can either of you pls post or send a pm to the .apk for a non-programmer explorer?
Click to expand...
Click to collapse
thet1nman said:
Loved this launcher amazing work. No longer works on EX12 for me.
Click to expand...
Click to collapse
<link pulled, see next post> (i forgot to sign it )
Works with XE12 via djwhitlow's patch
invisiblek said:
http://invisiblek.org/glass/GlassLauncher-12192013-signed.apk
Works with XE12 via djwhitlow's patch
Click to expand...
Click to collapse
Looks like the apk isn't signed.
EDIT: Might have been an error on my side. Got it signed and installed. Working great. I have attached the .apk.
Invisiblek: if you want me to take this down, I will do so.
banq81991 said:
Looks like the apk isn't signed.
EDIT: Might have been an error on my side. Got it signed and installed. Working great. I have attached the .apk.
Invisiblek: if you want me to take this down, I will do so.
Click to expand...
Click to collapse
Heh, whoops. No, by all means, keep it there for the others :laugh:
Can someone compile the apk and pm it to me too please?
Sent from my Galaxy Nexus using xda app-developers app
mightybryan said:
Can someone compile the apk and pm it to me too please?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This thread is two pages long. You couldn't even read two pages to find it? WTF.
invisiblek said:
This thread is two pages long. You couldn't even read two pages to find it? WTF.
Click to expand...
Click to collapse
The one above fails to install...
Sent from my Galaxy Nexus using xda app-developers app
Worked for me!
Install, but FC.
Screens, features, some describtion would be usefull ...?
Sent from my GT-S7562 using xda app-developers app
Screens, features, and description in the OP.
After adb installing the file, you have to run the main activity from adb the first time.