Database Info

[INFO] I got Eclair running on hero! check it out!

OMG ROXORZ I DID IT I DID IT!!!
ok now that i have all the noobs attention please read, and stop posting stupid questions.....
(Mods, i know this is probably not what the forums need, especially as this is a repost of a sticky, but I (along with others) am tired of seeing inexperienced users post about system dumps/ROM/apps/stupid junk when all they need to do is use the search function!)
***Informative Threads***​Post your question / issue / success story / etc. in the appropriate threads instead of starting a new thread!
Do NOT post a new thread to ask a QUESTION!!!
If your post has a question mark in it, you most likely need to post your thread in the Q&A Section
​
[Build Indexes] - Don't ask which build is best -- choose for yourself based on the features you desire!
androidspin.com
SimonNWalker & a group of Android Community members are maintaining a site which showcases the feature sets of the latest and greatest android builds ("roms" if you prefer). Check here to see "which is best" and try them out for yourself. The site is also ripe with news about Android development and more. XDA Thread
androidrevisions.com
Sir Savant is maintaining another build database. This web app allows for sorting / filtering / etc - XDA Thread
Google Docs Build Spreadsheet - View and edit build info - Google Docs Build Spreadsheet
[Guides/Tutorials/Info]
HTC Dream overview and useful information - Wiki article
Highly recommended for beginners.
In the beginning... There was ROOT
Lots of good definitions, history, and an excellent overview of most things going on here.
SPLs for DREA100 & DREA110 (Orig, Eng, Hard)
Contains information and downloads for SPLs (Secondary Program Loader) for the Dream. A modded SPL is instrumental in restoring from backup, preventing a brick, applying builds designed for foreign markets, etc.
Nandroid v2.0 - Full NAND backup and restore tool
In-depth discussion of your best friend whilst modding your android device. A good Nandroid backup regimen will pay dividends to keep you up and running.
Basic adb/root commands for noobs
Using ADB and terminal commands for your Android phone.
Surviving a Data Wipe / Update (Reduces Force Closes, too!)
Save (most of) your data while switching between builds (wipes are not your enemy!!)
Cyanogen's recovery partition
Amon_Ra's Recovery Partition
Modded recovery and boot images
SDSPLIT repartition your SDcard on phone (w/o a PC) - NOW handles > 2G FAT!!!
An easy way to re-partition your SD card without a PC.
LucidREM's Latest JF mod scripts
The swiss army knife of build customization
Auto-lucid script by tehseano
Let's fix that SPL Pay attention too post 3
Report in here if your phone is unresponsive after applying the 1.33.2005 SPL released by Haykuro. If you can get into Recovery or the SPL bootloader screen (three skateboarding androids), this is not you.
ROM guide for HTC Dream
T-Mobile G1 User Guides/Manuals
HTC Dream Wiki
"Brick" Thread or Technical Think Tank for Bricked G1's
If your phone is stuck at your splash screen (most likely a big white "G1")...if you you think something is broken...if you otherwise think you have a brick, post here instead of starting a new thread and any online members will do everything they can to help you out. (Reading as much as possible of these threads before posting will give you lots of insight as well!!)
Benchmark your build (apps thread)
[HOW TO]
STOCK-2-CYANOGEN / Root, Recovery, Radio, Rom / Partition SD / FAQ
How To Partition SD Card With Ubuntu For Dummies
Partition sdcard w/parted,goto ext3/4 & install rom from adb. no liveCD req'd
UNROOT, get phone to STOCK firmware
Reverting back to stock firmware.
New and improved Apps to SD(more stable, more powerful, etc)
The latest tutorial on how to get apps to SD.
Convert and mount ext2 sd partition ( /system/sd ) to ext3
Tools and instructions to add journaling to your ext sd card partition (apps2sd, etc). trust me, journaling is a good thing!
Register the G1 without a sim or data plan
Increase Max Volume -- Automated, no reboot needed
ADB for Dummies Supported Operating Systems Drivers and SDK
Get Home Auto Rotate on JFv1.51
Unpack, Edit, and Repack Boot Images
Create and edit "recovery" and "boot" .img files -- this thread is not for splash images.
Custom SPLASH Image
Replace that G1 splash logo that displays when your device turns on.
Alternative way to creating a SPLASH image
View Man Pages in terminal / adb shell
Mount SD card in recovery via adb
Use ash as your login shell
[MOD]user configurable userinit.sh V0.1.4.1 for CM
config file for setting up compcache, tweaks, etc. at boot
[How to] mount SD card in recovery.
Ported Hero Programs:
HTC Camera
HTC Music
***Developer Links***
Developers - Instead of maintaining a list of builds, I've changed this list to include links to your publications (blog, twitter, main release thread, etc.) let me know when / if you want these modified or if any should be added -- I'm sure I've missed some of you!
​
JesusFreke's Blog
Haykuro's Blog
TheDudeOfLife's google code page
Cyanogen's Twitter
TwistedUmbrella's Twitter
justanothercrowd's twitter
Stericson's twitter
For links / info on particular builds, check out the AndroidSpin, Android Revisions, or the Google Docs Build Spreadsheet

misleading topic title?

Pinesal said:
misleading topic title?
Click to expand...
Click to collapse
thats the point... maybe if people see something they are wanting, they will actually read the thread.

palosjr said:
thats the point... maybe if people see something they are wanting, they will actually read the thread.
Click to expand...
Click to collapse
haha. thanks for wasting 30secs of my life... anyway, what's Eclair?
[e] still props for compiling the list, i would correct the title (FAQ?) and make sure it gets sticky... i was really wondering why noone else did something like that. you can't complain about newcomers asking question if you don't have such a list

this thread is misleading bull****, should be locked

vihil said:
haha. thanks for wasting 30secs of my life... anyway, what's Eclair?
[e] still props for compiling the list, i would correct the title (FAQ?) and make sure it gets sticky... i was really wondering why noone else did something like that. you can't complain about newcomers asking question if you don't have such a list
Click to expand...
Click to collapse
this is exactly what i was pointing out ^^^^^^ nothing against you vihil, but you were the first to bite. all this information is in a sticky at the top of the Development Forum, but noone reads it anymore. I was just trying to get it out there in the "threads that are actually read" stream.

where are the sshots?
sshots or it didn't happen

rubbachicken said:
where are the sshots?
sshots or it didn't happen
Click to expand...
Click to collapse
lmao .. please tell me you're joking right? .. did you not read ANYTHING?

Ok....But how did you get 2.0 working on your Hero?
;]

xidominicanoix said:
lmao .. please tell me you're joking right? .. did you not read ANYTHING?
Click to expand...
Click to collapse
seriously... some of these ppl should not even be a part of this forum... i am half tempted to open a poll for the banning of members that post on this thread asking how i got it to work, ask for "sshots" or ask any other stupid question pertaining to eclair...

palosjr said:
seriously... some of these ppl should not even be a part of this forum... i am half tempted to open a poll for the banning of members that post on this thread asking how i got it to work, ask for "sshots" or ask any other stupid question pertaining to eclair...
Click to expand...
Click to collapse
HAHAHAHAHAHAHAA i love this. now for real n00bs to find this and read it...

This thread should be removed... you're only adding more useless content to the forum. Kinda hypocritical.

You got me good. I was actually excited for 0.5 seconds until I read the first sentence.

I thought this would be interesting....you realize legitimate power users would click on this and now we just have wasted time. I hope this thread vanishes.

dills84 said:
This thread should be removed... you're only adding more useless content to the forum. Kinda hypocritical.
Click to expand...
Click to collapse
no more useless than the previous 6 threads on eclair or an eclair port within the past 3 days.

even if they open it they wont even read it nonetheless, its almost impossible for these nubs

my point in this entire thread is an attempt to get noobs to read important info. case in point... in 15 minutes this thread already has almost 600 views...

This thread made me happy lol. I praise your efforts, but the n00bs are out of control and there is no helping them anymore. Its just "gimme, gimme, gimme". They want everything handed to them.....
At least the XDA Wrecking Crew made an appearance before the thread got locked.

LOL
+1
/10char

I am getting rather tired of answering questions answered 10...000 times

[Dev] Output to CWM recovery via shell script (with sample) [Thanks Chainfire]

This is for developers, rom packers, etc.
When Rodderik was working on his sdboot partitioning script, I was told about a way to get a shell script run from recovery to output to the user using the ui_print command.
Since then, I have been curious if it is possible to report progress to CWM from a script as well.
I finally got around to doing some research and figured out how to get reporting progress working.
I used the sources found here to figure it out.
Then, while asking around where the ui_print stuff came from (so I can give credit) I was pointed to this post by Chainfire:
[TRICK/CWM3/EDIFY] Output to recovery UI from shell script
So it seems it had already been done (figures), but oh well, it's still good stuff!
I'm posting here so more people will see it and I've also attached a sample zip as a working example.
The example has been tested and is working in both Grape-Ape and Bonsai recovery.
Credits:
Chainfire for figuring this out to begin with.
chris41g for sharing it with Rodderik (and indirectly me) and for digging up the link to Chainfire's thread.
Rodderik for sharing it with me and creating a nice little sample for me (which exposed why my initial attempt wasn't working).
Note that, apparently, to get a nice full progress bar, the full value should be about "1.335".
Also my scripts are a little different than Chainfire's, but the basics are the same.
(Check the sources link if you want detailed descriptions of the commands.)
Enjoy.
=]

So much easier to skip the edify scripts and do everything from Sh scripts...

indeed much more flexibility doing it that way...i've been thinking about doing it this way myself from now on

Hi ive big problem.
I would try to convert the update-script to an shell script.
Its possible?
please help.
I use cwm 4.0.0.9 lg optimus speed.

[PROJECT][WiP] CMbins v0.3.1

Originally this was going to be something I would do for Kyorarom v0.2.0, but I will also let the general public in on my works.
I am currently going through every single file in CM6.2 and seeing if it will work on Froyo with little to no effort. Why? Well think of it as a poor mans alternative to a fully functioning CM6.2. I respect marcellusbes work 100% but there are so many people who are being impatient about the non-existant ETA of CM6.2 and CM7 (BECAUSE IT SAYS THERE IS NO ETA AND THERE SHOULD NOT NEED TO BE AN ETA), I decided to give the people half of what the want: the performance and open sourceness of CM6.2 while still retaining 100% functionality of the Samsung firmware.
Current Status
99% of the bins are working
A few CM apps are working
Some of the libs are working (but they are more just sitting in there)
--- CONSIDER THIS VERY MUCH IN BETA - THIS WILL HAVE A FEW BUGS HERE AND THERE SO PLEASE REPORT ALL OF THEM SO I CAN FIX THEM ---
Now remember, this is by no means an alternative to CM6.2, it is more of a stopgap for people who really want our phone to have CM6.2 on it.
I have been working on this all day today and haven't been able to actually test it properly, but it appears to be stable with the files I have added, and it also appears to be quicker. Not by much, but it feels a little smoother.
Why would I need this?
As I said, it's a poor mans CM6.2. It will give you 90% of the performance of CM6.2 while still giving you 100% functionality (provided I haven't broken anything) from Samsung firmware. Programs run quicker, the system responds faster, and the system just feels smoother in general. It's not like FuguTweaks or V6 Supercharger which gives you a tiny change, the goal of this is to give you a HUGE change.
What is noticably quicker?
Well I need people to tell me that, but what I have noticed is quicker is:
Screen rotate happens quicker
Scrolling through menus
Swiping around websites
System boot time
What do I need to use this?
Well I have only tested this on Kyorarom v0.2.0 alpha (unreleased), so I don't know how your results may go, but it SHOULD work on all JPS based SAMSUNG ROMS.
THIS IS NOT A PATCH FOR CM6.2! THIS IS A PATCH FOR SAMSUNG!
You will also need CWM with update.zip signing disabled. This is provided as an update.zip as there are SO MANY permissions that need to be set in the bins/xbins/libs that it would be ridiculous to tell people to run an ugly script which will probably not work on 99% of peoples computers, so an update.zip without signing is how I will do this. Why no signing? Because every guide I have followed to tell me how to sign a zip or an APK has done nothing useful. SOMEONE TELL ME HOW PLEASE!
How do I install this?
Just put this on your SD Card, go into CWM and tell it to update from an update.zip. Pretty simple. I highly recommend doing a system.img backup first though to be on the safe side in case something goes terribly wrong. Format your /system before restoring the system.img.
What should I do if I get a bug such as a force close or a random reboot
Get your phone right to just before the crash happens
Plug your phone into ADB
Go into ADB SHELL
Type logcat > /sdcard/crashlog.txt
Reproduce the crash
Wait until it has rebooted/force closed
Press Ctrl-C on ADB SHELL
Get the crashlog.txt off your SDcard and paste the last about 20-30 lines in a code box here telling me what you did to cause the crash.
Links
Patch 0.3.1 (requires Samsung firmware, recommended to be on JPS)
CMapps 0.3.0 (should work on Samsung firmware without CMbins)
CMbins Remover (will only replace the bins with the original Samsung bins)
Patch v0.2.0 (requires Samsung firmware, recommended to be on JPS)
Busybox Fix (for in case you installed any of the patches v0.0.3 and below - NOT AN UPDATE.ZIP: THIS IS A BUNCH OF FILES WITH A README)
Please note that this may play up with some custom themes, especially large ones such as MIUI as this replaces a lot of files which these themes may be using or rely upon.
Credits
marcellusbe for his incredibly hard work on CM6.2 and CM7 which sadly seems to not be appreciated as much as it should by some of this community. Please go over to both the CM6.2 and CM7 threads and thank him for his hard work, even if you have already done so.
Change Log
v0.3.1
Removed more pointless stuff such as the etc and libs as they won't provide a performance boost. They were more decoratio.
Fixed install script which removed TW apps but didn't replace them from v0.3.0.
v0.3.0
Removed pointless bins which don't provide any performance boost, such as ping and stuff.
Fixed force close lag bug.
v0.2.0
Added the last few bins that were missing. Only bins missing are the ones that cause the system to break.
Added a few more things from etc from CM. They shouldn't cause any difference.
v0.1.1
Fixed dalvik-cache building.
v0.1.0
Removed xbin. It was causing too many problems
Added a few libs (ones that aren't in Samsung)
Added a few items from etc
Replaced a few stock Samsung apps in order to clean the system up before I remove twframework.
v0.0.3
Fixed the missing meta-inf folder in the update.zip. Sorry guys!
v0.0.2
Fixed the busybox issue. the patch removed the old busybox and replaced it with a broken one. If this doesn't fix it then 'mount -o rw,remount /dev/block/stl6 /system' and 'chmod 755 /system/xbin/*'

I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!

cdesai said:
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
Click to expand...
Click to collapse
If you wish to help me then by all means I'll be grateful. I am nowhere near finished as there are a few files in /system/bin that still need checked to see if they cause issues. I just went through the alphabet and if a file such as 'dexopt' caused problems then I left out all of D. However that's just an example. Dexopt is left out, but I left in the rest of D as I found it causing problems later down the track. I know I am missing Q and S. I'm gonna go through them all tomorrow.
EDIT: Not to mention I want to go through frameworks and libs and the etc folder too.

I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.

Sergiales said:
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Click to expand...
Click to collapse
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.

@hillbeast
you also plan to port the framework of cm6?

ale_bot said:
@hillbeast
you also plan to port the framework of cm6?
Click to expand...
Click to collapse
I hope I can. The plan is to get everything that will work from CM6.2 in Samsung firmwares to work.

New version uploaded. See first post for details.
I fixed the busybox issue. I thought I fixed it earlier but aparently not. It was CM6.2s Busybox being in there that killed it. I put the Samsung one into v0.0.2 so it'll fix the grief it caused with version 0.0.1.
If it still causes issues then go into adb shell (or Terminal Emulator) and run this code:
Code:
mount -o rw,remount /dev/block/stl6 /system
chmod 755 /system/xbin/*

Donate and get rewarded
Good work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
You (just caught you user reading this), could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones (dharamg3, marcelubes.. and some of all the other great programmers) donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!

(•.•) said:
Gut work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
Yes You, could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
Click to expand...
Click to collapse
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.

hillbeast said:
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
Click to expand...
Click to collapse
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.

(•.•) said:
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
Click to expand...
Click to collapse
Yeah that is the entire point of the XDA: developers helping developers to make our phones incredible and help them reach their true potential.
People bash the Galaxy 3 but undreneith it's actually a really good phone with really good hardware. It's no dual-core Cortex-A9 with 1GB of DDR2 RAM or anything, but it's certainly a very good mid-range phone. It was just held back by Samsung not programming it right.

Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!

niteshtak said:
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
Click to expand...
Click to collapse
Yes however I also need to find what is compatible with the rest of Samsungs firmware.

hillbeast said:
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
Click to expand...
Click to collapse
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.

Guys I totally forgot the meta-inf folder in v0.0.2. You can just use the one from v0.0.1 as there is no signing or anything. I'll see if I can get the link on my phone for v1
Sent from my GT-I5800 using XDA App

But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !

Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
Well its just a try to get the CM6.2 speed and smoothness on the samsung ROM..without having the bugs of CM6.2 which arent solved yet...

Sergiales said:
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Click to expand...
Click to collapse
Same problem in 0.2 with busybox installer, even trying to fix it with adb.

Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
As I stated in the OP, Cyanogenmod is incomplete and is buggy. The camera doesn't work, the FM radio doesn't work, no Bluetooth, and some things are buggy. By working in the opposite direction of moving to Cyanogenmod with small steps by using the working components from it, we get a balance.of speed and functionality which is what a lot of people have been moaning about all this time since CM went alpha.
Again, huge respect to marcell for getting it this far. This is a huge achievement from him.
Also here is the mediafire link for v1 so people can grab meta-inf and insert it into the v2. I will fix this in v3 later today.
Sent from my hybrid Kyorarom + Cyanogenmod Galaxy 3

The Theory of Everything (Building MTK from saucery) asop cm miui ubuntu

Welcome​
I have started this thread for the THEORETICAL development of the mt6732/mt6752 from source if such a thing happened to exist which of course it does not.
While compiling from source is pretty well documented :good: compiling MTK is not so well documented especially the mt6732/6752.
I have tried to keep this thread as ambiguous as possible and hopefully we will be left in peace to iron out any difficulties.
DO's:
I am a Total Noob myself to compiling from source but experienced enough to use the xda search box, Google and Youtube first before asking any questions. If your still confused after using the above then by all means ask here.
DON'T s:
If your a noob who should happen upon this thread then by all means read and learn but please respect the dev's by not asking random question without searching first :fingers-crossed:
SHARING:
Please only share things of a sensitive nature with recognised members who you know and via the PM. :good:
Lets just see how far we can push this Kernel
Recommended Reading:
[GUIDE]Building a Kernel from source{Mediatek}
Build Kernel MT6577 - Can't boot after build
How To Port CyanogenMod Android To Your Own Device
XDA:DevDB Information
k01q_e k01q_h, Kernel for all devices (see above for details)
Contributors
bigrammy
Kernel Special Features: Remains to be seen
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-02-25

I am here, reporting for duty. If anyone wants an extra "potato" because he has too much "ketchup" for use feel free to ask me

Just to be clear
I am new to compiling from source in any shape or form
I believe the kernel to be not a problem and I know dev's are working on getting our phone on cm and maybe others :fingers-crossed:
But me being me I am very curious and would like to understand how we would go about doing what @varun.chitre15 managed to do for the mt6582 Here
I have the PC all setup for building now thanks to @carliv great guide Here and the cm and android tut's I also found this useful guide on youtube by Dave Bennet Here
Our device is not on the cm or google repo so how do we add it locally.
Do we need any special commands for mediatek
Could we use the mt6582 repo and substitute or mod the files
As you can see I have more questions than answers as normal :laugh:
I dont want to tread on any toes here or take over current developing but just want to learn as said in the OP there is a lack of mtk guides regarding this.
If I missed a clear mtk guide then please post the link to it. :good:

In short your looking at manifests. http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
carliv (I think) posted the device config on github - link in your SPFlash thread somewhere.
Found it: https://github.com/carliv/device_elephone_p6000?files=1
Vendor files

I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.

xenonism said:
I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.
Click to expand...
Click to collapse
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.

HypoTurtle said:
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.
Click to expand...
Click to collapse
The config file is attached to the post, it's too big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
About the notification issues (which bothers me the most), I haven't had much time do to more experiments, but I was thinking this (which probably also led to my confusion*): there's a chance the functionality is not removed or shut down, at least in the intentions of the maker. After all, in V8.4 (and in the new ROM), when the phone is connected the light stays on, while notifications make it breath. While not a desirable behaviour (at least IMO), I wouldn't call it... a non-behaviour, so to say. So perhaps the functionality itself is intact but something is altering the way it works, for whatever reason. I also did some unpacking and grepping a few days ago, but I couldn't find anything useful.
* At some point I thought the issue was fixed because the light was breathing while connected to my PC, but it was probably because I had a notification to read.

xenonism said:
The config file is attached to the post, it's to big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
Click to expand...
Click to collapse
Lets not speculate too much - but perhaps there was a minor board change between the first and second preorders, notification could be a problem with granting notification access (in settings) - could this be a selinux issue? It would explain why things like Light manager work - as you grant them notification access.
For lost Imei - can you compare the custom partition to the one in the ota?

If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.

BachMinuetInG said:
If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.
Click to expand...
Click to collapse
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:

bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
I'm actually a noob too, and honestly I've only ever successfully built a fakeflash (temporary recovery) that didn't even work.

bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?

Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
I think you can use the scripts in the root of the source code to build the kernel? make<something>.sh.
Make sure you're on Linux (Ubuntu preferred) and that you have all dependencies installed correctly. To execute the script, simply go to the Terminal, cd to the location, then type . make<something>.sh

Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Have a look at the README.
Does make menuconfig work here?

These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.

xenonism said:
These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.
Click to expand...
Click to collapse
Yea wasn't sure about menuconfig as mtk uses projectconfig rather than def_configs.
In the custom partition there are files like /custom/etc/firmware/modem.img etc. When messing with a Flyme port it was these files (and possible conflicts in /system) that caused an IMEI:nul.
FYI I opened the custom partitions on windows using an ext viewer after running the imgs through sgs2toext4.

Kernel building Mediatek
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Not sure if you guys have seen or read this but it's a pretty comprehensive guide to building the mediatek kernel by @MasterAwesome and should really be compulsary for all kernel related things thread here http://forum.xda-developers.com/showthread.php?t=2754513
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Maybe we will have to repartition the emmc to a standard config and alter the kernel (if the links are set via the kernel that is) for cm and other ports to work smoothly as I am unsure just how everything is linked up.
I have not had much experience with custom partitions so someone one know's of a good info source please link it. :good:
Hopefully Master @Santhosh M can figure out what's going on with the custom partition :fingers-crossed:

bigrammy said:
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Click to expand...
Click to collapse
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).

HypoTurtle said:
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).
Click to expand...
Click to collapse
Haha thanks that explains a lot of weird things perfectly. :good:

What's the problem or what is the issue here.
Mediatek compiling guide ( by masterawesome ) that you have linked to is not actually practically this mtk kernel is done and is just way too complicatedly explained.
There is no defconfig stuff or pulling config.gz from phone in mtk. In this new source its just simple. Set up your toolchain path. Execute the makeMtk followed by the project no u want. Get zImage and patch it for mtk header and merge it with stock ramdisk. For this newer mtk chipsets repack has an extra stuff where u have to be careful of kernel command line parameters.
That's it the kernel stuff in mtk

**Development Stopped**

Development Stopped!
I think my project is useless so i will stop it
When i have my new Phone I will Try myself on Safestrap and Cyanogenmod on stock Kernel
Cause My Fire is then only around and i can brick it​

Development Stopped!

What exactly is the upside to this "customized" stock ROM ? Details pls!
Unless you recompile something, it's not clear what this accomplishes. The trend is actually the other way, to keep things as stock as possible.

bibikalka said:
What exactly is the upside to this "customized" stock ROM ? Details pls!
Unless you recompile something, it's not clear what this accomplishes. The trend is actually the other way, to keep things as stock as possible.
Click to expand...
Click to collapse
I Make this cause no One did This for this Devices!

bibikalka said:
What exactly is the upside to this "customized" stock ROM ? Details pls!
Unless you recompile something, it's not clear what this accomplishes. The trend is actually the other way, to keep things as stock as possible.
Click to expand...
Click to collapse
I assume the OP just took out some system apps, then rezipped it with some CM extras.

Remolten said:
I assume the OP just took out some system apps, then rezipped it with some CM extras.
Click to expand...
Click to collapse
Given that the FireOS 5.x update comes with a huge file that is kind of dd'ed into /system partition, would it not make more sense to create a flashable zip which would do a few post-install modifications such as :
1) remove apps you don't want
2) install CM apps you do want
This would be a lot more transparent, and easier to use with the newer FireOS updates when they come out.

bibikalka said:
Given that the FireOS 5.x update comes with a huge file that is kind of dd'ed into /system partition, would it not make more sense to create a flashable zip which would do a few post-install modifications such as :
1) remove apps you don't want
2) install CM apps you do want
This would be a lot more transparent, and easier to use with the newer FireOS updates when they come out.
Click to expand...
Click to collapse
Sounds like a great idea! Probably fairly easy to do as well. You could also append it to a gapps script as well.

I can't believe we don't have any real roms yet

Remolten said:
Sounds like a great idea! Probably fairly easy to do as well. You could also append it to a gapps script as well.
Click to expand...
Click to collapse
See my little clean up script "make_space_v01.zip" in :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
For now I just removed moffice and weather, but if needed, one can delete a whole bunch of stuff (it's a script in this zip file called "rmstuff.sh", just add more removals, and re-zip )
Code:
#!/sbin/sh
rm -rf /system/priv-app/moffice*
rm -rf /system/priv-app/com.amazon.weather

bibikalka said:
See my little clean up script "make_space_v01.zip" in :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
For now I just removed moffice and weather, but if needed, one can delete a whole bunch of stuff (it's a script in this zip file called "rmstuff.sh", just add more removals, and re-zip )
Code:
#!/sbin/sh
rm -rf /system/priv-app/moffice*
rm -rf /system/priv-app/com.amazon.weather
Click to expand...
Click to collapse
This is a great start! Releasing some heavily customized stock roms could definitely be useful for some people.

Sorry for the people who liked it but the development is stopped now!

JUSTINMARMER said:
I can't believe we don't have any real roms yet
Click to expand...
Click to collapse
Funny 'cause, I have absolutely NO PROBLEMS believing this. this is what happens when you use cheapo Chinese junk.
Caveat The Hardware, in-and-of-itself is fine. The support of such Manufacture's to actually release a useful SDK / Sourcecode however? Can be forgotten. Fact is if anyone BUT Amazon were selling this Device. We probably wouldn't even have the Kernel Source. Much less the rest of what would be needed to build a new Custom ROM.

Ichijoe said:
Funny 'cause, I have absolutely NO PROBLEMS believing this. this is what happens when you use cheapo Chinese junk.
Caveat The Hardware, in-and-of-itself is fine. The support of such Manufacture's to actually release a useful SDK / Sourcecode however? Can be forgotten. Fact is if anyone BUT Amazon were selling this Device. We probably wouldn't even have the Kernel Source. Much less the rest of what would be needed to build a new Custom ROM.
Click to expand...
Click to collapse
We have full kernel source for the Fire 7 (9th gen) ?
Where ?
Edit:
I just found it here:
https://www.amazon.com/gp/help/customer/display.html?nodeId=200203720