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...
Has anyone actually succeeded in merging the Samsung eclair code into the android-2.1_r2 tree and building a viable image that will run in the emulator (let alone the device itself). I am running into libwebcore.so problems, specifically with the nativeSetUploadFileName function that Samsung added - somehow the emulator didn't like it and said it wasn't found. I am now building a generic android-2.1_r2 to see if that can load in the emulator in case I am just messing it all up.
I downloaded the android-2.1_r2 source, and just copied the whole tree onto the eclair tree from Samsung, leaving the Samsung code in case of conflicts and the tree built fine. But loading the image onto the emulator just crashed at startup with the libwebcore.so problem due to nativeSetUploadFileName not found problem.
-Atin
Looks like Samsung did not put out the changes they made to the frameworks webkit java files for the native functions they added. So I am slowly adding them into the relevant files by hand, recompiling, finding the next missing symbol, repeat...
Till now I've found the following missing from the java files:
In WebView.java:
class WebFeedLink
nativeGetWebFeedLinks
nativeGetWebFeedData
In WebViewCore.java:
nativeSetUploadFileName
nativeHandleMultiTouchEvents
atinm said:
Looks like Samsung did not put out the changes they made to the frameworks webkit java files for the native functions they added. So I am slowly adding them into the relevant files by hand, recompiling, finding the next missing symbol, repeat...
Till now I've found the following missing from the java files:
In WebView.java:
nativeGetWebFeedLinks
nativeGetWebFeedData
In WebViewCore.java:
nativeSetUploadFileName
nativeHandleMultiTouchEvents
Click to expand...
Click to collapse
Screw it . . . need to find the implementations for WebFeedLink and WebFeedData that Samsung added but didn't put out in their eclair dump. Maybe the Vibrant or just the plain GalaxyS dump would have them - taking forever to download those.
No luck. Vibrant source dump is a lot smaller, missing a lot of files that the Captivate and GalaxyS dumps have. And both the Captivate and GalaxyS eclair are missing the same files so can't pull from one for the other. Pain.
Just commenting out the nativeGetWebFeedLinks stuff, can't see where it is used in the code anywhere. Possible that it is used by one of the Samsung apps that they didn't release the code for - like the SocialMediaHub thing.
The reason I'm trying to just build Eclair is because if I can do that, I'll be confident that I have everything that I would need for Froyo to work. I can build vanilla Froyo, but am not confident it will use everything on the phone right now!
Keep up the good work! If i knew at all how to do that kind of stuff i would help you. But i don't . Im here for a tester if you need one
Sent from my SAMSUNG-SGH-I897 using XDA App
atinm said:
Screw it . . . need to find the implementations for WebFeedLink and WebFeedData that Samsung added but didn't put out in their eclair dump. Maybe the Vibrant or just the plain GalaxyS dump would have them - taking forever to download those.
No luck. Vibrant source dump is a lot smaller, missing a lot of files that the Captivate and GalaxyS dumps have. And both the Captivate and GalaxyS eclair are missing the same files so can't pull from one for the other. Pain.
Just commenting out the nativeGetWebFeedLinks stuff, can't see where it is used in the code anywhere. Possible that it is used by one of the Samsung apps that they didn't release the code for - like the SocialMediaHub thing.
Click to expand...
Click to collapse
You should contact samsung. Others have had responses from them when it comes to kernel code.
Sent from my SAMSUNG-SGH-I897 using XDA App
staticfish said:
You should contact samsung. Others have had responses from them when it comes to kernel code.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Wrote to Samsung - no response yet. I'll keep at it in the background, and hope that the Froyo source release will be better! Am a little unhappy that I can't build Eclair with a merge of the Android Eclair sources and Samsung's sources that actually works. The problem I am running into now has to do with the Calendar app dying because of a missing subscriberFeed provider and the Calendar app is the one I want to fix on my phone so that it doesn't always use the "My phone" calendar by default when that calendar is disabled!
-Atin
bump
any updates?
Nothing from Samsung. I've put this on the backburner until wes gets the Vibrant up with Cyanogen and will start hacking in that source tree to get it onto Captivate.
Hi, I recently bought fantastic tablet Point of View Protab 2 IPS 9.7. Basically it is Allwinner A10 device. I tried to install new CyanogenMod 10 on it. Everything works flawessly, except one thing. I don't have any touchcontrols, probably because, I don't know what compatibility pack should I install. Could someone please give me advice, what drivers should I install to get working touchscreen on jelly beans 4.1(CM10)?
Same Here
frees11 said:
Hi, I recently bought fantastic tablet Point of View Protab 2 IPS 9.7. Basically it is Allwinner A10 device. I tried to install new CyanogenMod 10 on it. Everything works flawessly, except one thing. I don't have any touchcontrols, probably because, I don't know what compatibility pack should I install. Could someone please give me advice, what drivers should I install to get working touchscreen on jelly beans 4.1(CM10)?
Click to expand...
Click to collapse
I have been trying to get it running myself so far I have tried just about every compatibilty pack.
All I know so far is this device has an upsidedown screen, and other users have had to make thier own comp packs with the "sun4i" which I think is the touch control.
Please let me know if you have any luck.
times iiescre
Hm, that's too bad. I hope, that someone will have drivers. Anyway, I will try to lsmod loaded drivers and built my own pack. Wish me luck.
Since I recently bought one of this, I would like to know if you had any effort on making it compatible to CM10. I really would like to use it. If I could help you with anything, let me know
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
palmino said:
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
Click to expand...
Click to collapse
has anyone found or compiled the module yet?
I looked through most of the compatibility files and could not find it.
Would be awesome to have a good 4.1 on this tablet!
---------- Post added at 12:21 PM ---------- Previous post was at 12:00 PM ----------
palmino said:
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
Click to expand...
Click to collapse
perhaps this helps:
http://downloads.pointofview-online...ab-ips 8GB TAB-PROTAB2-IPS9 Firmware Upgrade/
I have send a mail to their support people to request the kernel source.
Let's hope they comply to the GPL.
Another approach would be to donwload a kernel tree from CM 10 and try to compile the source code you linked to.
Are you sure it is the proper driver?
Would be awesome if this pulls off
No i'm not sure. This is the only pixcir driver file I could find on the Internet
Hopefully they reply to your mail. The current Rom is very slow compared to the cm10.
Unfortunately my device was in a bootloop and i had to return it for repair.
Let me know when you receive an answer
palmino said:
No i'm not sure. This is the only pixcir driver file I could find on the Internet
Hopefully they reply to your mail. The current Rom is very slow compared to the cm10.
Unfortunately my device was in a bootloop and i had to return it for repair.
Let me know when you receive an answer
Click to expand...
Click to collapse
Well, I did receive an answer, which in short said they cannot provide the source code.
I pointed to the GPL license and requested them to contact the lawyer department if they have one.
If they refuse, I am not sure what options there are to enforce it.
Some usefull info I found here:
https://android.googlesource.com/ke...885aa51f1abf3c40/drivers/hid/hid-multitouch.c
I read somewhere that support for this display is added by Stephane Chatty of ENAC.
Maybe someone can work with that source?
Mr. Chatty helped me before with a touch driver, if you do you some proper work and get stuck, I am sure you can contact him for help.
Personally I would love to dive in, but I can't find the time now.
Perhaps this helps some devs?
Can't imagine those drivers can't be made. Probably some dev setup on Linux for the proper 4.1 kernel version.
There is a ton of information on that.
this link is also interesting:
https://build.pub.meego.com/package...Project:KDE:Mer_Extras:Adaptation:Archos-gen9
It suggests they are in the Archos gen 9 and also that some kind of calibration is being developed.
Perhaps the ko can be pulled from an Archos gen9 rom ?
I saw your posting over in the Archos G9 Forums. Hopefully there is a chance to reuse this. I posted the same question in a large german Android-Forum. Maybe we can get it from there if noone replys here.
Furthermore the Archos seems to use two different touchscreen-devices: bit.ly / VUo71L
If you're correct, this might be the uncompiled driver: bit.ly / UIJ2Bq
But still I neither have an idea how to compile this, nor is my device back from repair.
palmino said:
I saw your posting over in the Archos G9 Forums. Hopefully there is a chance to reuse this. I posted the same question in a large german Android-Forum. Maybe we can get it from there if noone replys here.
Furthermore the Archos seems to use two different touchscreen-devices: bit.ly / VUo71L
If you're correct, this might be the uncompiled driver: bit.ly / UIJ2Bq
But still I neither have an idea how to compile this, nor is my device back from repair.
Click to expand...
Click to collapse
can you please use full links instead of those very irritating-twitter-like short-urls ?
I would like to know where it is pointing to (and it did not work on my android).
I think there is a good chance it might work.
Last time I compiled kernel modules, i noticed it is importent al versioning stuff is matched properly.
POV is not really cooperating in terms of open source obligations.
They are not the first.....
I really would like to post normal links but I cant since I'm not meeting the conditions for posting links here in the Forums (I need at least 10 posts hiere in the forums). I'm close to this.
Removing the whitespace before and after the slash should do it. Sorry for the inconvenience!
palmino said:
I really would like to post normal links but I cant since I'm not meeting the conditions for posting links here in the Forums (I need at least 10 posts hiere in the forums). I'm close to this.
Removing the whitespace before and after the slash should do it. Sorry for the inconvenience!
Click to expand...
Click to collapse
ok, np. sorry did not know that. I think we have gathered quite some resources for devs.
Perhaps someone can create a forum item for our device?
Sorry, personally I cannot find time at the moment.
I do have time to test any dev builds by the way...
another tip.
The main reason I wanted to update, because the browser was performing like thick **** rolling up a mountain against the wind.
And it hanged too sometimes.
When checking processes I noticed the nandd process being on top often.
After googling that process, I found somebody else also had a slow browser issue caused by this process.
He fixed it with a factory reset.
I did that too, and now the problem is solved.
I can also recommend installing setcpu. You can overclock till about 1200 (mine 1152 now) which makes it a bit snappier.
Mine is rooted by default, it just works, not sure if this is always the case.
And please mail POV for the kernel source .
OpenMinded said:
another tip.
The main reason I wanted to update, because the browser was performing like thick **** rolling up a mountain against the wind.
And it hanged too sometimes.
When checking processes I noticed the nandd process being on top often.
After googling that process, I found somebody else also had a slow browser issue caused by this process.
He fixed it with a factory reset.
I did that too, and now the problem is solved.
I can also recommend installing setcpu. You can overclock till about 1200 (mine 1152 now) which makes it a bit snappier.
Mine is rooted by default, it just works, not sure if this is always the case.
And please mail POV for the kernel source .
Click to expand...
Click to collapse
Yeah, The overclcok makes a huge difference also changing governer to performance and io sceduler to noop.
Before my 8 year old used my tablet as a frisbee, I was trying to tweak it futher with pimp my rom from the market, it has some great tweaks for this tab.
I never got any increase in the benchmarks but resposiveness was up with my tegra phone.
Also opera is a fantstic browser for this tab, once ya figure out how to use it you will be hooked.
williamsjp said:
Yeah, The overclcok makes a huge difference also changing governer to performance and io sceduler to noop.
Before my 8 year old used my tablet as a frisbee, I was trying to tweak it futher with pimp my rom from the market, it has some great tweaks for this tab.
I never got any increase in the benchmarks but resposiveness was up with my tegra phone.
Also opera is a fantstic browser for this tab, once ya figure out how to use it you will be hooked.
Click to expand...
Click to collapse
Nice tips! How to swt io scheduler?
Fantasy schedular seems to work better than on demand on this.
OpenMinded said:
Nice tips! How to swt io scheduler?
Fantasy schedular seems to work better than on demand on this.
Click to expand...
Click to collapse
You can change the sceduler in SetCPU
Also i found if i had performance governer enabled i couldnt over clock past 1100 or it would reboot its self
Bought myself this tablet as well. is all nice and good but the 3G is giving me a headache. with the stock rom it works excatly as long as you don't turn on wifi. after that even if you turn wifi off again it wont connect to 3G anymore.
Firmware side isn't helping much either. V4.008 is without 3G (in the settings there is now only a list of supported dongles. and the 3Gfix image has same issue, you see 3G only once until you turn on wifi)
So i was hoping for a better rom but looks like the CM9/CM10 department can't help either. So i was hopin if you guys have had any progress.
E: i have been in contact with POV support over the last week and the only useful intel i ahve gotten out of them is that as far as they are aware there are no clones for this tablet. Also it appears that there is a android 4.1 based firmware for the tablet in the testing. They are not sure if they release it tough.
anybody tried to fix a touch driver for this device?
I had to send my tab back for repair since my headphone jack wasn't working anymore.
Unfortunately they were out of stock so that they couldn't send me a new one and refunded me.
I will not buy a new protab2 9,7 because it's so laggy. I hope you all can figure out a solution for the touch-issue. I'll leave you here, guys. Thanks for your help anyways
Nothing yet?
I see there are a compability zip for the protab2xxl at http://forum.xda-developers.com/showthread.php?t=1760929, annyone knows if that is helpful for the protab 2 IPS 9?
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...
Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU