Related
EDIT:
Magister2k7 said:
Please update first post of a thread, as Mer should run X with a latest kernel from git.
You just need to disable FB_MSM_DOUBLE_BUFFER ("Enable MSM Framebuffer double buffering") and enable framebuffer refresh thread.
Click to expand...
Click to collapse
Yeah, I kinda doomed myself from the start with how I structured this post. I'll restructure it later to be more able to show you good information.
Old start:
Mer is a more community-led version of the Maemo phone and internet tablet operating system. See http://wiki.maemo.org/Mer/ .
I was in contact with a member of that project (Stskeeps on freenode#mer), who gave me some information about porting this to phones such as the kaiser. He and I thought it would be a great way to benefit both communities (we get a good, not google-owned linux-based os for our phones, they get developers helping them make mer better). We also agreed that it would take a bit of effort.
First of all, Mer is completely designed for landscape-only, 800x480 phones at this point. It has been run well at 640x480, but that's still 4 times our native resolution, and 2 times what we can fake without crashes. The resolution problem is easily fixed by skilled theme-makers. The landscape/portrait problem should be fixed soon, given that the upcoming n900 will be a portrait/landscape phone. He said wait for the maemo conference for more on that.
The other problems we might hit basically are just the standard problems of molding the userspace around the kernel (get a phone app working, get the modem to work, etc.).
If you are serious about helping, please come to #mer and/or #htc-linux on freenode. At this point, the mer folks are probably more help to what we need to do.
INSTRUCTIONS:
At this point, quite literally nothing works, but it all almost works. Here's what I did to get that far:
1. Partition your sd card into two partitions, and make the second one ext2.
2. Unpack (with the -p option of tar) the rootfs (http://wiki.maemo.org/Mer/Releases/0.16testing , pick the q5 rootfs) to the ext2 partition. Make sure that it's not in any subfolders, but as the root of the drive.
3. Grab a zImage (or build your own) using the instructions we had in place from android. Put it on the fat side.
4. Set up HaRET on the fat side - Use a default.txt from android, get rid of the initrd, get rid of your ppp stuff (for now), and add "root=/dev/mmcblk0p2 rootwait" to the kernel cmdline.
5. mknod /dev/fb0 c 29 0 (this was my number, check using the terminal in android, cat /proc/devices for the major, and /proc/fb for the minor). Also make sure that it's within the root, not on your disk .
That should boot, giving you a ton of messages about an "incorrect resolution png" or something - that's the splash screen unable to load. Simply rename /lib/init/splash-* (two files) to something else. Once you get a terminal later, there's an actual package to remove, but this lets it go a bit further.
You also need to keep X from starting at this point - all it does is hang. I have not yet done this myself, but it should be an initscript that you just un-link.
EDIT: It wasn't X that caused the issues. It was the combination of failed splashes and consolefont. Comment out the lines with "splash" in them in /etc/init.d/check{fs,root}.sh, and re-run.
I do not know if X actually fails - doing that test now.
EDIT: hitting framebuffer issues... no X yet.
So, if you're adventurous, and preferably a dev at this point (this is completely useless to users), please try this out and make it better!
Okay, just a note: the password is "rootme".
First reply!
this is relevant to my interests. I'll take a look. I remember seeing that Maemo was made on top of Gnome. Do you know if there's a chance to get Debian apps on here? That's the big thing for me to get me working on it-- some type of desktop compatibility. Having an X-server is perfect. Looks like you're saying the resolution issue is purely theme based? How open are the devs for it for suggestions and feedback?
2nd reply
This does sound cool
already made some read about this in the new nokia n900..
its cool.. it free.. but i dont like the ui :\
lets see where this goes.. but.. for now.. for me... android (L)
Ok, just saw it's Jaunty based which is what I've been looking for in a phone.
Is there a list of features/bugs/issues and what's been developed so far? Seems like if the kernel brought to us in part by dzo will work maybe it won't be so hard to get wifi and other features working. A list is good.
I'll admit I haven't put much effort into it, but at this point X won't work, for one thing - probably have to change the resolution in a config somewhere.
Indeed, most of the hardware should be fine - I imagine, for example, once we are able to load the firmware, wifi should be good. Some code will have to change (a few things are built android-specific in the kernel), and some of the RIL stuff especially (phone, data, etc.) will have to be ported by someone who has that code and some time.
Indeed, Mer is Ubuntu-based, and so, according to their site, 95% of ubuntu apps should work perfectly. This is really nice for getting software on (aren't just limited to any applications in an app store or market.).
At this point, all we need to do is everything .
I'm going to try now to disable X and see if I can't get a few more things working.
EDIT: in response to your question about how open the mer-folk are to suggestions? The idea that I got from talking to them was that they are more than happy to get this extra help, and since they are trying to bring this to more devices, they are willing to put up with our requirements, to make this more readily available in general.
Alright, as I edited, I got some more success.
By removing the splash calls and the X starting, I can get a terminal. I edited the /etc/shadow file to have a password that I knew for root. Now, I can log in as root on the console (/dev/tty1).
I tried to start X, and I'm getting some strange framebuffer errors.
I'll keep you posted.
Wow, if we could get this working, it'd be sick! Thanks for posting, formatting now.
with all the hard work already done for the Android port, seeing devs being interested in Mer is REALLY PROMISING! Waiting for Google to open up Android even more, is frustrating...
Porting Mer and thus having a REAL linux (kernel+software stack) is what we need to leverage the dev capacity of the great XDA community. At least, this is what I feel like .
Owning both a Kaiser and 2 N800s, I'll probably try out the stuff posted here... I was keeping an eye on Mer for my N800s anyway, but using it on the Kaiser is more triggering
so devs, have courage and good luck!
Frame Buffer and X server
Unfortunately I've been quite busy lately and haven't been following the Android development as closely as I would like. (I don't think I've updated my git repo for months)
If I remember correctly, the frame buffer code in the kernel wasn't finished. That would prevent X from running. Can anyone say whether that was completed? I just wanted to mention this in order to avoid people wasting their time if it is in fact the problem.
It would be great to *eventually* see X running with hardware acceleration, can anyone point me to info about how DZO got that working? Was it reverse engineered, or did he figure out how to make some binary blob happy?
It will be nice to have some choice of Linux based distros the Kaiser and Vogue. Keep up the good work everybody, I appreciate it!
-Mysteryvortex
I've been looking at the n900 for quite some time just waiting for its release to the US next month. I know nothing about developing but I am very excited about this one, and I hope that there is a quick start to the apps that are put out for it. I was curious myself as well at how this would port to the kaiser so I could get a good hands on before I went and bought one. I would be more than happy to be a tester. I bought an iphone cause cause the little green guy is really starting to piss me off and my tilt's about to give up the ghost. I quickly gave it to my wife as the signal strength and battery life just sucks so I hope this maemo can give me what I want
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
Click to expand...
Click to collapse
The build has a kernel and stuff, but don't use it. Use the regular stuff from android (or build yourself from htc-vogue).
mdrobnak from irc got mer up on his raph - thanks to the vga screen, with a quick kernel patch and some xorg.conf modification, he got X working great.
Within the next few days, I'll do some tests of the data connection and such.
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
Click to expand...
Click to collapse
Yes, that's correct. Android doesn't use X. Many, many months ago, it was mentioned that the framebuffer in the Vouge/Kaiser kernel (which X will use) was broken. Nobody was planning to fix it since Android doesn't need it. I was just trying to point people who have time to work on supporting our phones in the right direction.
poly_poly-man: Looks like the Raphael kernel is being developed on another branch, but it sounds like the FB patch helps us?
-Mysteryvortex
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Borkata81 said:
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Click to expand...
Click to collapse
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Borkata81 said:
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Click to expand...
Click to collapse
It seems that even set to the right resolution, our fb does not work with X. Needs more patching than just the patches I got from the other branch. We may need to move up to the other branch, I'm not sure.
the /dev/fb0 should be replaced with /path/to/sdcard/root/dev/fb0, of course. And it's better to just get rid of all the splash references - that way, you don't get the blank screen issue.
toasty_ said:
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Click to expand...
Click to collapse
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
Oh yes, you're right. I should first read the full post before answering questions that havn't been asked
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
http://people.openezx.org/tmzt/
the msmts and vres patch. Didn't work, because there are more problems in our older kernel.
I'm interested in finding out why we aren't on 2.6.27 already...
Hello,
I was wondering if there was an Android app like Activator on the iPhone? I have searched to the best of my abilities regarding this question but have not found a clear answer. The closest I have come to finding this answer was the app "LaunchKey." However, it does not seem to fit what I am looking for.
Reason for this search is due to my brief episode with the iPhone 3g and yes I know...(after finding out, android system is definitely better in terms of customizing and freedom) Thus during that time I came upon this app called "Activator", which is basically amazing. Now that I am back using the android system I realized the only I miss about the iPhone was that app.
So if anyone can help that would be great! Thanks!
BTW:
Background information on the iPhone jailbreak app "Activator." Basically you can launch any apps and system actions via gestures or hardware buttons. (such as long-press, short-press, double tap,etc...)
http://forum.xda-developers.com/showthread.php?t=850464
and for gestures Im not entirely sure where I saw it or or what it was called but it does exist.
Reply
Thanks for the reply, however, I did stumble upon that app but it does not really support long press, short press, double tap and other various hardware buttons. As for gestures, I guess it does not matter as much as the hardware button configuration. Basically can a button have more functions than just one ie: home button-going to home. Thanks
I'm hoping that this app exists, as its one of the first apps I discovered years ago that was auto installed after jail breaking my previous iPhone. The app basically allows you customize a very large range of settings as shortcuts.
http://m.lifehacker.com/5899492/mak...hen-you-connect-or-disconnect-your-headphones
not strongly related but here's an app which I found very useful:
https://play.google.com/store/apps/details?id=tora.mamma.swipestart
Thanks!
Thanks for your input I however have found the app "SwipePad" to be extremely useful, albeit not the original application I was looking for but it does the job Thank you again!
really!!! Android is amazing, I think is like a pocket pc, but sometimes I miss my old iPhone when I remember cydia tweeks like Activator. :silly:
mnunez2 said:
really!!! Android is amazing, I think is like a pocket pc, but sometimes I miss my old iPhone when I remember cydia tweeks like Activator. :silly:
Click to expand...
Click to collapse
LOL, yeah same here man this post is old Most of the updates in 4.2 resolved my need for Activator...though not as much options it serves well nevertheless
clikonco said:
LOL, yeah same here man this post is old Most of the updates in 4.2 resolved my need for Activator...though not as much options it serves well nevertheless
Click to expand...
Click to collapse
OMG This is what I want to say my Android Friends Iphone tweaks are more easy way to go, im wondering How can I get Activator !!! >> since 4 years im iphone user and recently bought Note 2 (still I have Iphone) this entire conversation is what im looking for Please help to get a tweaks like that even I looked Cydia substrate for Android mm no use as of know....
Widgets are great but you still have to unlock the phone and look at the screen and press it. With activator you can, for example, press the power button of the phone twice and that will initiate the flash light... this is much better when you are in need of the flash light quickly...I wish android had something like that...
Help Help .... Droid help
webvamsi555 said:
OMG This is what I want to say my Android Friends Iphone tweaks are more easy way to go, im wondering How can I get Activator !!! >> since 4 years im iphone user and recently bought Note 2 (still I have Iphone) this entire conversation is what im looking for Please help to get a tweaks like that even I looked Cydia substrate for Android mm no use as of know....
Widgets are great but you still have to unlock the phone and look at the screen and press it. With activator you can, for example, press the power button of the phone twice and that will initiate the flash light... this is much better when you are in need of the flash light quickly...I wish android had something like that...
Help Help .... Droid help
Click to expand...
Click to collapse
I believe since the time I have posted this question to the present, there have been alternatives as well as actual implementations to the hardware tweaks. Currently, there are baked in hardware tweaks in custom ROM such as CM10.1 (lock screen long press buttons do variety of different things) or software programs such as swipepad, or Trigger app (Both of which I use a lot)
My current ROM CM10.1 has the capability of accessing the flashlight from the longpress of home button while in lockscreen. Or even changing music volume and music track by volume press/longpress. This I consider the equivilent of what you were referring to.
clikonco said:
I believe since the time I have posted this question to the present, there have been alternatives as well as actual implementations to the hardware tweaks. Currently, there are baked in hardware tweaks in custom ROM such as CM10.1 (lock screen long press buttons do variety of different things) or software programs such as swipepad, or Trigger app (Both of which I use a lot)
My current ROM CM10.1 has the capability of accessing the flashlight from the longpress of home button while in lockscreen. Or even changing music volume and music track by volume press/longpress. This I consider the equivilent of what you were referring to.
Click to expand...
Click to collapse
Hi Clikonco,
Thanks for the Update, awesome response, I'm new to Android and have few questions
1) if I do Custom Rom CM10.1 can I get is back to normal Stock ROM to get warranty back ?
2) If so what would be the best procedure to install CM10.1 ?
I already root my Stock Rom with Rooting using Odin by Beginners Guide
3) So would I be able to install CM10.1 after rooting my custom Rom
4) If possible also please point me(url) to unroot custom Rom to Stock Operating system please (for future need).
5) And also I heard a lot about cm10, cm10 nightly, cm10 aopk which one is better or all these same ? I have international Note 2 with
GT- N7100 > 4.1.2 > Baseband : N7100DDDMG1 > Build no : JZ054K.N7100XXDMG1 > Kernel V: 3.0.31-1071214
confused !!!!
Please help .. Thanks a lot lot lot :good:
webvamsi555 said:
Hi Clikonco,
Thanks for the Update, awesome response, I'm new to Android and have few questions
1) if I do Custom Rom CM10.1 can I get is back to normal Stock ROM to get warranty back ?
2) If so what would be the best procedure to install CM10.1 ?
I already root my Stock Rom with Rooting using Odin by Beginners Guide
3) So would I be able to install CM10.1 after rooting my custom Rom
4) If possible also please point me(url) to unroot custom Rom to Stock Operating system please (for future need).
5) And also I heard a lot about cm10, cm10 nightly, cm10 aopk which one is better or all these same ? I have international Note 2 with
GT- N7100 > 4.1.2 > Baseband : N7100DDDMG1 > Build no : JZ054K.N7100XXDMG1 > Kernel V: 3.0.31-1071214
confused !!!!
Please help .. Thanks a lot lot lot :good:
Click to expand...
Click to collapse
**ATTENTION: any of the information I have provided are based on my own experience/knowledge/research. IT IS IMPERATIVE(important) that you do your own research to double check my information and advice. If ever in DOUBT, ask/research around. (or dont follow through is usually the safest option) YOU are ultimately responsible for what you do with YOUR device, if you don't believe this, please do not continue dabbling in this area.
You should be able to do that, to "unroot" your phone, but it depends on the device as well as the instructions that other developers/rooters have given. (meaning not 100% probable, you need to do more research)
*JUST NOTICED YOU SAID YOU ARE ROOTED
-To get Stock ROM, just download the appropriate ROM zip files and then flash it.
-if you want to get warranty back, you will have to follow instructions for your device on how to unroot. (if even possible)
Follow the instructions given on the cyanogenmod website, usually involves flashing and wiping. (sounds like you have a samsung phone )
Based on question 3 statement, I believe you have to do MORE research. (as this is an extremely basic idea of rooting, unless of course I misread or the question was mistyped) Here is where you can start:CM about
Again, you have to do MORE research yourself, google is your friend for that. There is no one size fits all unrooting method.
Cyanogenmod (also known as CM) has an software release life cycle. (not counting the M snapshot nor experiments) You have Stable>Nightly> Release Candidates(RC).
Taken from this Forum
bassmadrigal:
Stable is after all the features desired by the CM devs have been put in and the code has been tested. Snapshots (M builds) are builds done roughly once a month that has had some testing to make sure things are mostly working and released to the public. These are the first builds that allow official bug reports on the project manager site, https://jira.cyanogenmod.org. Nightlies are automated builds that are built, well, every night. There is no human interaction with these and they are largely there just to see if the code added throughout the day will compile. As far as the devs are concerned, there are no bad builds with the nightlies, because if it doesn't build, that is news to let them know that something is screwed up in the code. They don't accept any bug reports on these builds.
Generally, the nightly builds, while extremely experimental and considered bleeding-edge, tend to be relatively stable and mostly bug-free. Many people use the nightlies as their so-called daily-driver, meaning that any bugs that they may have aren't so severe that they want to switch to a different version. For my Nexus 4, as soon as I got it I switched to a nightly build and haven't had any bugs pop up.
Also, all builds are full builds, so if you switch to a nightly, you aren't required to flash every single nightly. You can do it as you see fit. I've been known sometimes to flash a build every day, but then I've gone a month in between updating. Just grab the latest version you want to flash and flash that one.
Click to expand...
Click to collapse
Similar answer regarding AOPK (Android Open Kang Project:What Is AOKP ROM? How Is It Different From CM9? All You Ever Wanted To Know About
Hope these answered/helped you. I intentionally did not include some information such as unrooting because you will have find them yourself Alright, already spent too much time on this post, im out for now.
BTW: if you or anyone finds incorrect information in this post, please feel free to correct me. Thank you!
clikonco said:
Hello,
I was wondering if there was an Android app like Activator on the iPhone? I have searched to the best of my abilities regarding this question but have not found a clear answer. The closest I have come to finding this answer was the app "LaunchKey." However, it does not seem to fit what I am looking for.
Reason for this search is due to my brief episode with the iPhone 3g and yes I know...(after finding out, android system is definitely better in terms of customizing and freedom) Thus during that time I came upon this app called "Activator", which is basically amazing. Now that I am back using the android system I realized the only I miss about the iPhone was that app.
So if anyone can help that would be great! Thanks!
BTW:
Background information on the iPhone jailbreak app "Activator." Basically you can launch any apps and system actions via gestures or hardware buttons. (such as long-press, short-press, double tap,etc...)
Click to expand...
Click to collapse
Use xposed addition in xposed
Hello,
the device /dev/graphics/fb0 is word read- and writeable on my device (Samsung Galaxy S2 with CM 9.1.0). I suspect it is the same way on many other devices.
Every app can read the whole framebuffer and make screenshots. If the app would do that it could also monitor the softkeyboard. The results wouldn't need to be saved because it could extract the pressed key on the fly.
I have tested a short loop in the Terminal and it worked. I was able to get screenshots from an app with the FLAG_SECURE set. Which should disallow the ability to make a shot. ( I wasn't root. ) I was able to get the fb dumps with the keyboard and the keys pressed.
You can manualy set the Permissions to 660, then only root and graphics users can use it.
Can someone please confirm this configuration on other devices?
I don't think it is intendet that every app can play keylogger.
And before you ask I havn't posted/informed anyone. Because if you look at the /dev/exynos-mem hole you want to check every other file in /dev for similar errors. So that is what I did and i can't be the only one. So I figure the blackhats are two steps ahead.
blulantern said:
Hello,
the device /dev/graphics/fb0 is word read- and writeable on my device (Samsung Galaxy S2 with CM 9.1.0). I suspect it is the same way on many other devices.
Every app can read the whole framebuffer and make screenshots. If the app would do that it could also monitor the softkeyboard. The results wouldn't need to be saved because it could extract the pressed key on the fly.
I have tested a short loop in the Terminal and it worked. I was able to get screenshots from an app with the FLAG_SECURE set. Which should disallow the ability to make a shot. ( I wasn't root. ) I was able to get the fb dumps with the keyboard and the keys pressed.
You can manualy set the Permissions to 660, then only root and graphics users can use it.
Can someone please confirm this configuration on other devices?
I don't think it is intendet that every app can play keylogger.
And before you ask I havn't posted/informed anyone. Because if you look at the /dev/exynos-mem hole you want to check every other file in /dev for similar errors. So that is what I did and i can't be the only one. So I figure the blackhats are two steps ahead.
Click to expand...
Click to collapse
I'm 90% certain this file was copypastaed from a Samsung initramfs - so some Samsung releases most likely have this setup too. I'll ask codeworkx which one.
I'm in the process of cleaning up ueventd, unfortunately this mess happened just as I was getting ready to leave for the holidays.
Entropy512 said:
I'm 90% certain this file was copypastaed from a Samsung initramfs - so some Samsung releases most likely have this setup too. I'll ask codeworkx which one.
I'm in the process of cleaning up ueventd, unfortunately this mess happened just as I was getting ready to leave for the holidays.
Click to expand...
Click to collapse
I was unable to locate the same issue in stock devices, maybe CM is using copypasta from old firmware ramdisks.
jcase said:
I was unable to locate the same issue in stock devices, maybe CM is using copypasta from old firmware ramdisks.
Click to expand...
Click to collapse
Yeah, there's a good chance it predates XWLPM. We swapped kernel sources but not ramdisks with Update7.
What builds have you looked at? I'm going to try and see if codeworkx remembers which build he pulled those from.
I'm going to attempt to do a ueventd cleanup before I leave for the holidays. It may be an "axe everything and let the rest of the team figure out what broke and needs repair" approach...
I think this may have been in a samsung leak that never got removed, it dates back to the very first commit of this file in ICS, but isn't in one of my initramfs dumps from one of the first ICS official releases.
http://review.cyanogenmod.org/#/c/28759/
If no observed regressions it will be backported to CM10/CM9 time permitting, but could take some time as I'm unavailable from tomorrow onwards until the new year.
Hi,
I did a little code search on github, this issue seems more widespread than I thought.
I can't post external links here, because I'm new
If you search on Github in Code for:
/dev/graphics/fb repo:CyanogenMod/*
You will find
CyanogenMod/android_device_htc_click » init.bahamas.rc (Rust)
CyanogenMod/android_device_geeksphone_zero » init.zero.rc (Rust)
If you don't restrict the search on a repo you will get many results for different devices, the once i checked had the permission set to 666 or 777 (in the latest revision). But I didn't find the result with the galaxys2 so i figure my results are far from complete.
Is there a mechanism to let the owners know without searching through every projekt and opening an issue there?
Thanks.
Entropy512 said:
Yeah, there's a good chance it predates XWLPM. We swapped kernel sources but not ramdisks with Update7.
What builds have you looked at? I'm going to try and see if codeworkx remembers which build he pulled those from.
I'm going to attempt to do a ueventd cleanup before I leave for the holidays. It may be an "axe everything and let the rest of the team figure out what broke and needs repair" approach...
Click to expand...
Click to collapse
Recent builds (im lazy and in bed so ill look later)
Sent from my SGH-I317M using xda premium
Entropy512 said:
I think this may have been in a samsung leak that never got removed, it dates back to the very first commit of this file in ICS, but isn't in one of my initramfs dumps from one of the first ICS official releases.
http://review.cyanogenmod.org/#/c/28759/
If no observed regressions it will be backported to CM10/CM9 time permitting, but could take some time as I'm unavailable from tomorrow onwards until the new year.
Click to expand...
Click to collapse
Makes sense since leaks often have more relaxed permissions due to debugging.
Sent from my SGH-I317M using xda premium
Anyone willing to make builds on a weekly base ?
robuser007 said:
Anyone willing to make builds on a weekly base ?
Click to expand...
Click to collapse
I think I may be willing. I'm quite a newbie, getting this as my first smartphone - really first cell phone, for Christmas. I got it partly for utility, mostly as a learning vehicle, and one of the first things I did was flash CM10.2 on it, followed shortly by CM11 M1. I've kept up with the Milestones ever since, with the one skip, until August when I heard that the flow had stopped.
If I want new Milestones, I guess I'm going to have to do it myself. Assuming I can get the hang of it, I'll presume I can put out weeklies, as well. This can turn into even more of a learning experience than I first anticipated.
Though I'm new to phones, I've got a lot of years (several decades) as a VLSI designer, including doing some of my own CAD tools and CAD support for my department. My home machines have also been on Gentoo Linux for over a decade, so I'm decently versed.
I can't start now, because my development system is dead. I'm posting from an Asus EEE Box, which while serviceable, is barely keeping up with my typing right now. My birthday is later next month, and I'm planning on getting a new development system then. In the meantime, I plan to do some reading. Beyond the basics they have at the CM11 pages, any other suggestions would be appreciated. Only specific is that there seems to be a generic CM11 release, plus some phone-specific files. Is there a convenient source for those latter files, rather than trying to do them from essentially no experience?
phred14 said:
I think I may be willing. I'm quite a newbie, getting this as my first smartphone - really first cell phone, for Christmas. I got it partly for utility, mostly as a learning vehicle, and one of the first things I did was flash CM10.2 on it, followed shortly by CM11 M1. I've kept up with the Milestones ever since, with the one skip, until August when I heard that the flow had stopped.
If I want new Milestones, I guess I'm going to have to do it myself. Assuming I can get the hang of it, I'll presume I can put out weeklies, as well. This can turn into even more of a learning experience than I first anticipated.
Though I'm new to phones, I've got a lot of years (several decades) as a VLSI designer, including doing some of my own CAD tools and CAD support for my department. My home machines have also been on Gentoo Linux for over a decade, so I'm decently versed.
I can't start now, because my development system is dead. I'm posting from an Asus EEE Box, which while serviceable, is barely keeping up with my typing right now. My birthday is later next month, and I'm planning on getting a new development system then. In the meantime, I plan to do some reading. Beyond the basics they have at the CM11 pages, any other suggestions would be appreciated. Only specific is that there seems to be a generic CM11 release, plus some phone-specific files. Is there a convenient source for those latter files, rather than trying to do them from essentially no experience?
Click to expand...
Click to collapse
wiki.cyanogenmod.org/w/Build_for_apexqtmo
orange808 said:
wiki.cyanogenmod.org/w/Build_for_apexqtmo
Click to expand...
Click to collapse
Reading... First annoyance I see is translating from Ubuntu packages to Gentoo. Some move directly, some won't be needed, like the -dev stuff. Every Gentoo system is a development system. Some trial and error will be called for. Can't wait to get started. (I may try putting this on my wife's computer, if I can't wait a month.)
I've decided I can't wait, and am installing on my wife's computer. I'm running into a few Gentoo-isms trying to get this installed with the icedtea-7 - it wants to use icedtea-6. I'll be back when I get there.
phred14 said:
I've decided I can't wait, and am installing on my wife's computer. I'm running into a few Gentoo-isms trying to get this installed with the icedtea-7 - it wants to use icedtea-6. I'll be back when I get there.
Click to expand...
Click to collapse
It may be easier to use a container or VM, rather than using your system proper. I use Gentoo for my main server, but just used Ubuntu 14.04 in a VM for my build system. At least to verify you have a working build environment, I recommend sticking to Ubuntu (13.x or 14.x).
For APEXQTMO building, the instructions on the CM site are reasonably complete. You probably want to skip the "pull binaries from the phone" part, and just update the local_manifest to get the binaries from TheMuppets GIT.
Let me know if I can help.
I'm headed out of town for a few days, and will think harder about it when I get back. I don't mind installing (and uninstalling) stuff on Gentoo. My wife's machine is only 4G, which is a bit tight to run a VM in. At the moment I don't even have the VM stuff turned on in my kernels, but that can change, of course.
The "pull binaries from the phone" part was interesting. I take it that these are different binaries than the radio and bootloader firmware I had to update on my wife's phone? (Mine came with 4.1.4, and didn't need the update.)
phred14 said:
I'm headed out of town for a few days, and will think harder about it when I get back. I don't mind installing (and uninstalling) stuff on Gentoo. My wife's machine is only 4G, which is a bit tight to run a VM in. At the moment I don't even have the VM stuff turned on in my kernels, but that can change, of course.
The "pull binaries from the phone" part was interesting. I take it that these are different binaries than the radio and bootloader firmware I had to update on my wife's phone? (Mine came with 4.1.4, and didn't need the update.)
Click to expand...
Click to collapse
Proprietary blobs.. Basically the drivers for the phone's hardware. Unfortunately, most manufacturers don't open source them.
phred14 said:
I'm headed out of town for a few days, and will think harder about it when I get back. I don't mind installing (and uninstalling) stuff on Gentoo. My wife's machine is only 4G, which is a bit tight to run a VM in. At the moment I don't even have the VM stuff turned on in my kernels, but that can change, of course.
The "pull binaries from the phone" part was interesting. I take it that these are different binaries than the radio and bootloader firmware I had to update on my wife's phone? (Mine came with 4.1.4, and didn't need the update.)
Click to expand...
Click to collapse
They are very different binaries. The blobs here are drivers for the OS level, not the bootloader and modem level.
Very likely if you follow that step from the CM wiki, it will break. As others have mentioned, pull from TheMuppets instead.
Also, to address another point you brought up -- You can use icedtea-7, I build with it all the time.
I'm of the opinion if you can make the build process work on your 'bare metal' OS, it's a much better option than using a VM (Heck, a chroot with the debian/ubuntuisms would be a MUCH better option than a VM, as the VM adds significant overhead and time to the build process. I don't know how easy it would be to get the 'debootstrap' and schroot programs on gentoo, which would make setting up an appropriate chroot pretty trivial)
Any building questions, feel free to stop by the irc channel listed in my sig.
So far, so good...
So the SDK and Eclipse are both installed on my wife's computer, though I'm not really using the latter at the moment.
I've been following the HowTo instructions from the Cyanogenmod page and this morning ran "breakfast", after an overnight repo fetch. At this point it's time to either fetch files from my device or TheMuppets, and the latter has been strongly urged here. I've found instructions for building local_manifest.xml for CM10, as well as a sample file as a start point. Does revision="cm-10.2" become revision="cm-11" or revision="cm-11.0", or is it something else entirely? This sample file looks like it's for the "Toro", though it has lines with "Tuna" as well, which I presume is a similar-enough device. Is there a better source for this file, can someone post theirs, or is it just time to stumble around?
Next question... According to this post http://forum.xda-developers.com/showpost.php?p=55045664&postcount=63 a simple build just isn't going to work. I've never actually used git, and even with what I've done so far it's so deeply buried that I don't really see it except as a name. But it looks as if I have to remove those two commits in order to have a chance of building a working rom. Can someone give me a start? I can RTFM, but I suspect that things are also buried here in android-conventions so that even with the manual, how to do this won't be obvious.
Thanks...
phred14 said:
So the SDK and Eclipse are both installed on my wife's computer, though I'm not really using the latter at the moment.
I've been following the HowTo instructions from the Cyanogenmod page and this morning ran "breakfast", after an overnight repo fetch. At this point it's time to either fetch files from my device or TheMuppets, and the latter has been strongly urged here. I've found instructions for building local_manifest.xml for CM10, as well as a sample file as a start point. Does revision="cm-10.2" become revision="cm-11" or revision="cm-11.0", or is it something else entirely? This sample file looks like it's for the "Toro", though it has lines with "Tuna" as well, which I presume is a similar-enough device. Is there a better source for this file, can someone post theirs, or is it just time to stumble around?
Next question... According to this post http://forum.xda-developers.com/showpost.php?p=55045664&postcount=63 a simple build just isn't going to work. I've never actually used git, and even with what I've done so far it's so deeply buried that I don't really see it except as a name. But it looks as if I have to remove those two commits in order to have a chance of building a working rom. Can someone give me a start? I can RTFM, but I suspect that things are also buried here in android-conventions so that even with the manual, how to do this won't be obvious.
Thanks...
Click to expand...
Click to collapse
Yes, you want "cm-11.0". For example, you'll have lines in local_manifest.xml like:
<project name="TheMuppets/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm-11.0"/>
For reverting a specific commit (like the two that @Magamo mentioned in the post you referenced), you can use git-revert. Check out http://git-scm.com/blog/2010/03/02/undoing-merges.html as a starting place.
Note that for your first build, you don't need to use git (just repo). A breakfast and brunch should work - you should get the UNOFFICIAL-nightly.zip file built, it just (potentially) won't work if you were to flash it. I recommend making sure brunch creates a .zip file with all the bits you expect it to have, before you start messing with git and reverting the commits that potentially broke the device. IMHO anyway.
scotte9999 said:
Note that for your first build, you don't need to use git (just repo). A breakfast and brunch should work - you should get the UNOFFICIAL-nightly.zip file built, it just (potentially) won't work if you were to flash it. I recommend making sure brunch creates a .zip file with all the bits you expect it to have, before you start messing with git and reverting the commits that potentially broke the device. IMHO anyway.
Click to expand...
Click to collapse
So overnight last night "brunch" built a .zip for me. I presume that it built at all is a good sign, but "with all the bits you expect it to have" is another test. I struggled a bit with local_manifst.xml, and ended up unzipping my cm11-M8 zip, which actually didn't help, because nothing in that list came from TheMuppets. More about that later. In the meantime, I presume I should unzip the rom file I just created and compare it to my unzipped cm11-M8 files?
As mentioned, I have relatively low confidence in my local_manifest.xml file. I found one on the web which was clearly for a different Samsung phone, changed the obvious things to apexqtmo and the "msm8960" that it appeared to be derived from. Then I started removing lines flagged when I started running the "breakfast apexqtmo" command. What I wound up with is this:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="gh" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_nxp" path="vendor/nxp" remote="gh" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_samsung_t1" path="kernel/samsung/t1" remote="github" revision="cm-11.0" />
</manifest>
Most of it makes sense, but it really depends on vendors imgtec, broadcom, invensense, widevine, and nxp covering the apexqtmo as well, since they originally covered the "tuna", which appeared to be a later phone. It also depends on kernel_samsung_t1 covering the apexqtmo. I did a bit of browsing around on github to get to this point, as well as the manifest unzipped from the cm11-M8 file I'm currently running.
Sorry for being a complete noob about this, but I guess I am. Thanks for your help. I'm also looking at your pointers on reverting commits, but I'm guessing that eventually we'll need a location to fork the affected files.
phred14 said:
As mentioned, I have relatively low confidence in my local_manifest.xml file.
Click to expand...
Click to collapse
Attached is what I use. It's not apexqtmo specific, since I have multiple devices that I like to build for, but if you can afford the disk and bandwidth it should "just work" for apexqtmo.
scotte9999 said:
Attached is what I use. It's not apexqtmo specific, since I have multiple devices that I like to build for, but if you can afford the disk and bandwidth it should "just work" for apexqtmo.
Click to expand...
Click to collapse
The format looked slightly different, but I have a copy, and I grabbed a few of the lines, tweaked to the format I have. Some of those entries looked like phones, and some looked like hardware vendors with components on phones. I was most interested in the latter.
One question... The other night my build went to completion and produced a zip file. Obviously those two commits will prevent it from booting on my phone, but other than that was it probably a good zip. What I'm really asking is, if the process completes, has it run correctly? Or will it continue running in spite of errors, producing a bogus zip file?
It's late tonight, but I think tomorrow morning before I leave for work I'll do another repo sync. This time before I build I'm going to set up ccache.
Once the zip is produced it is good, yes there can be issues like the commits you mentioned but in theory it should be ready to flash
phred14 said:
The format looked slightly different, but I have a copy, and I grabbed a few of the lines, tweaked to the format I have. Some of those entries looked like phones, and some looked like hardware vendors with components on phones. I was most interested in the latter.
One question... The other night my build went to completion and produced a zip file. Obviously those two commits will prevent it from booting on my phone, but other than that was it probably a good zip. What I'm really asking is, if the process completes, has it run correctly? Or will it continue running in spite of errors, producing a bogus zip file?
It's late tonight, but I think tomorrow morning before I leave for work I'll do another repo sync. This time before I build I'm going to set up ccache.
Click to expand...
Click to collapse
In general, 'breakfast' will produce a very workable local manifest for you, you just need to add the project for the proprietary blobs.
scotte9999 said:
For reverting a specific commit (like the two that @Magamo mentioned in the post you referenced), you can use git-revert. Check out http://git-scm.com/blog/2010/03/02/undoing-merges.html as a starting place.
Note that for your first build, you don't need to use git (just repo). A breakfast and brunch should work - you should get the UNOFFICIAL-nightly.zip file built, it just (potentially) won't work if you were to flash it. I recommend making sure brunch creates a .zip file with all the bits you expect it to have, before you start messing with git and reverting the commits that potentially broke the device. IMHO anyway.
Click to expand...
Click to collapse
Today I scripted the build process and let it whirl away. Other than making the computer more than a bit sluggish for my wife, it completed just find and created a .zip for me. At this point I think it best to let this run at night - what I really need to do is find what suspend command xfce is using, and have it auto-suspend when the job is done.
It's time to revert so I can build a zip that is worth flashing, and after reading your link I have another question... It looks to me as if once I've reverted those 2 commits, they will stay reverted even through repo sync commands, until I decide to revert my revert. (It also looks like it would be a good idea to save away the commit numbers git gives me for the reverts..)
Plus one more question... There is a clockworkmod recovery image file in the directory along with the cm11. Is there any reason to use this instead of the clockwordmod recovery I flashed back around the beginning of this year, when I first started by flashing CM10.2?
Finally, it appears that these are nightly builds I'm getting, basically like the trunk in subversion. At some point I would like to build Milestones, if only for my wife. How does one choose that?
phred14 said:
It's time to revert so I can build a zip that is worth flashing, and after reading your link I have another question... It looks to me as if once I've reverted those 2 commits, they will stay reverted even through repo sync commands, until I decide to revert my revert. (It also looks like it would be a good idea to save away the commit numbers git gives me for the reverts..)
Click to expand...
Click to collapse
Yes. You really want to make your own fork, etc., but for a GIT newbie that might be too much to tackle at once.
phred14 said:
Plus one more question... There is a clockworkmod recovery image file in the directory along with the cm11. Is there any reason to use this instead of the clockwordmod recovery I flashed back around the beginning of this year, when I first started by flashing CM10.2?
Click to expand...
Click to collapse
I *think* you need an updated recovery (I use the latest TWRP, found over in the Development forum) and it works fine. If you like CWM, then I'd update to a CM11 CWM.
phred14 said:
Finally, it appears that these are nightly builds I'm getting, basically like the trunk in subversion. At some point I would like to build Milestones, if only for my wife. How does one choose that?
Click to expand...
Click to collapse
If you followed the instructions on how to retrieve the source via repo, then you've actually downloaded the Milestone source as well. To build a milestone, you'd need to check out a specific tag (e.g., "M8") then build. Not that hard, but I recommend baby steps.
scotte9999 said:
Yes. You really want to make your own fork, etc., but for a GIT newbie that might be too much to tackle at once.
I *think* you need an updated recovery (I use the latest TWRP, found over in the Development forum) and it works fine. If you like CWM, then I'd update to a CM11 CWM.
If you followed the instructions on how to retrieve the source via repo, then you've actually downloaded the Milestone source as well. To build a milestone, you'd need to check out a specific tag (e.g., "M8") then build. Not that hard, but I recommend baby steps.
Click to expand...
Click to collapse
There's really little reason to use the updated recovery, if you're only focusing on Android 4.4 builds, unless there's some whizbang new feature included in an updated build. The older one is tested, stable, and very fine. If you're looking to flash anything OTHER than an Android 4.3.X or 4.4.X build, you'll want to update -- I know that the newer TWRPs have made it so that you can flash ancient images with it (I've tested it all the way back with one of the first CM9 alphas TeamApexQ released.) If CWM hasn't included that feature, then you may have some problems flashing the latest baseband and bootloader firmwares, as those are using the old format installer scripts, that google broke with Android 4.4 recoveries until the community fixed them.
OK, I'm now responding to both scotte9999 and magamo, so I guess quote time is over.
First, I've been delaying this trying to get further on a specific train of thought. But here it is Sunday night and I haven't been able to yet, so I'm just going to keep in touch and ask more newbie questions. I guess I'll say first that right now I'm backing up android/system/vendor/samsung, and in a moment I'm going to try to revert those two commits. Now that I think of it, I'm going to back up that rom image I built earlier. I am intentionally not re-syncing, so that I'll have two copies of 20130904, one stock and one with the commits reverted. From there I can compare. I was hoping to get more of this done before tonight, but no time. Yesterday we had an "emergency pool closing". The 13 yo pump died, and rather than try to fix then close, we just closed. I'm distributing the chemicals with a utility pump and hose for a few days. I think I can rebuild the pump over the winter, but didn't want it in series with pool closing. We're a week late, as is. Pools close early in Vermont.
Second, I'm just a tad worried that at some point the codebase will be cleaned / rebased / whatever, and the content I'm attempting to revert to will be just plain gone. No doubt a git-master could get it back, but not me. That's also why I'm not doing another repo sync.
So much for that attempt:
~/android/system $ git revert -m 1 187689ea76effd42b680a147d080512ac62a0fed
fatal: Not a git repository (or any parent up to mount point /local)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
I'm sure it's something so basic it wasn't covered in the document scotte9999 pointed me to. I'd already done everything to get my environment ready - my own exec to get started and "source build/envsetup.sh", so I presume everything would have been in place to run the revert.
As for the revert itself, I found the 2 commits on github and have looked at them. It appears that someone was trying to move a bunch of common code together under msm8960-common, generally a good idea, except when it doesn't work. I presume had one of the old Team apexqtmo developers still been around the current situation would have been corrected, presumable in a minimal fashion rather than reverting the whole commits.
Looking at the commits...
Minor oddity with the "aec" commit - libinvensense_hal.so disappeared from the "after", but when I look in the phone build I'd just done, it was still there. Maybe it was a duplicate? A little more looking, and this appears to control the sensor to get the "position" of the phone, which I'd hope wouldn't keep it from booting, just from making things upright when you rotate 90.
Even though it isn't listed in the "after" side of that commit, I find that lib in the relevant msm8960-common directory, and when I diff it against the one in the apexqtmo directory they don't match. (specifically, diff apexqtmo/proprietary/lib/libinvensense_hal.so msm8960-common/proprietary/lib/libinvensense_hal.so) Maybe there's a build date buried in the lib, so that they will never match, but I would have hoped that if it was a simple move, code unchanged, they would have.
Most important question - what's the correct syntax for the git revert? Obviously my attempt to RTFWP didn't work.
Second question - M10 is coming up next week, and if I can get the revert done, I'd really like to build this and make it work, if only to get the camera video, which is known-broken in M8, working on my wife's phone. Reading build/envseup.sh I get the impression that the magic invocation will be "breakfast apexqtmo-M10" and "brunch apexqtmo-M10", and someone must have been really hungry the morning he wrote this code. Is that presumption correct?
Thanks...
Note: This is not a ROM release but does contain links to the source repos and a brief guide for building yourself; I don't have the time to support and maintain a ROM and I'm happy enough with what works right now, it would be all too easy to get pulled in to trying to fix every little thing! Instead, I figured I'd share the work so far so anyone else can use it, fix it up or create a whole new ROM using it as a base.
I recently got myself a laptop/tablet hybrid and put Linux on it to replace both the TF700t and my old laptop but actually missed some of the parts of android that aren't quite as good on linux, namely games and 'reddit is fun' . So, given I no longer needed the keyboard dock as anything that requires it I just do on the laptop, I thought I'd try getting a mostly pure AOSP rom running for just 'tablet mode' to see if it was any smoother than CM by not having all the code required to support every possible device as well as all the extra CM features.
So, that's what I did and it runs pretty well requiring only a couple of ports of some legacy code required for our vendor blobs.
Sound and graphics work (and that's all I need for my intended use of the tablet)
The dock does charge the tablet and the keyboard works. but without the function keys
The camera isn't working, but that's probably a straight forward fix requiring a couple more ports of missing functions.
The only differences in the code to pure AOSP (most of which are ported from CM)
Required changes to framework and system/core for TF700t
NFC Unlock (useless to us but I added this for my Nexus5)
Option to maximize lockscreen widgets
Option to disable safe headset volume warning
Integrated SuperUser
Support init.d scripts
Lockscreen battery % while discharging
Clear all button on task switcher
Reboot option (with long press options for recovery/bootloader)
Re-arranged the quick settings tiles slightly.
The repo's are all here: https://github.com/AospPlus
To compile,
Code:
repo init -u https://github.com/AospPlus/android_manifest -b aosp-plus_4.4
repo sync
. build/envsetup.sh
time brunch tf700t
Finally, a huge thanks to @dasunsrule32 and @jruesga for all their work on this device (it's their device tree that I've used for this) and as well to the CyanogenMod team as more than a few of the changes come straight from their code