PLEASE HELP VOTING FOR THE FEATURES I COMMIT!
Current CyanogenMod has some bugs and limitations which I try to resolve. Some solutions were found by others. Some solutions I found.
I also try to put more features into CyanogenMod's kernel. So there is no need going for another one.
You want to see a new feature in CyanogenMod?
If you want to see a new feature in CyanogenMod please let me know. I only handle new kernel features at the moment. If you want to see new governors or new IO schedulers for example let me know and I will push them into the official repositories.
Approved commits
- Change Ic8722ac5: Added scripts to extract proprietary files to comply with the CM9 tutorial
- Change I7fc7c517: Fixed overclocking Power HAL module
- Change Ia93c111a: DPLL_CORE_M6_OPP100_RATE should be 266666666 (Ezekeel)
My patches for CM10
Here are my contributions listed. My changes will eventually arrive in every CyanogenMod based ROM. If they are denied to the official CyanogenMod kernel I might still include them here in my ROM. Note that I might discard the denied features at any time.
If you like my work feel free to buy me a beer. (Belgium has so many beers I'd like to try)
http://review.cyanogenmod.com/#/dashboard/4343
ROM Features
+ Custom Voltage v3 (Ezekeel)
+ I/O Schedulers added/modified:
----- BFQ v4
----- Deadline: fifo_batch 1
----- SIO v0.2
Downloads (CyanogenMod with pending or unapproved commits)
Cyanogenmod 10 Build 20120912
Cyanogenmod 10 Build 20120913 (NEW: change GPU OC from Settings application)
Cyanogenmod 10 Build 20120918
- MPU Undervolted (if you get a random reboot let me know and i will up all voltaged by 25mv until it's stable for everone.) Undervolted from 750mv (350mhz) to 1175mhz (1350mhz)
- Custom voltage from ezekeel.
- Disable MPU Smartreflex to use my custom voltages
- Make sure you have a rom backed up in case the mpu voltages are too low for you
Google Nexus Device Maintainers
- Robert Burns
- Kalimochoaz (Rafael Salas)
Documentation
- http://www.kernel.org/doc/Documentation/
Please vote and review my commits so they can be included faster in CyanogenMod, also motivate in your review why you would like to see it in the official CyanogenMod kernel
Updated thread. Please make a account at the link and vote +1 on every patch I have made. So we have these bugs fixed faster
add Rafael Salas (the cm galaxy nexus mantainer) and Steve Kondik (cyanogen) as reviewer, they will check, approve and merge ur patch..otherwise no one will care about ur patch..no need other people to signup
about the kernel upstream update, im not sure thats the way the cm team usually do it
Thank you. I added them as a reviewer.
Have you actually built the CM10 source? I am really confused on how to build it. I start screaming at the part with the proprietary files because there is no extract-files.sh
I have put the binaries in the correct folders like I did with AOSP ROMs but I get a boot loop at the bootlogo.
in the past i built cm9 using cm wiki here
I guess it should be something similar for cm10 (apart from the branch to be jellybean of course)
i don't know to much details anyway
andQlimax said:
in the past i built cm9 using cm wiki here
I guess it should be something similar for cm10 (apart from the branch to be jellybean of course)
i don't know to much details anyway
Click to expand...
Click to collapse
I used that one as a reference too, but this section is not applicable to cm10:
Copy Proprietary Files
So I was hoping for a workaround like this:
http://rootzwiki.com/topic/32731-how-to-get-the-proprietary-files-for-cm10-galaxy-nexus/
But I think there are erros in the guide
local_manifest.xml should be:
<?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="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_maguro" path="device/samsung/maguro" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="jb" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="jellybean" />
</manifest>
Click to expand...
Click to collapse
then a repo sync and you will have everything. but it doesn'T seem to be working.
Then again I took the latest proprietary files from google as well
djjonastybe said:
Thank you. I added them as a reviewer.
Have you actually built the CM10 source? I am really confused on how to build it. I start screaming at the part with the proprietary files because there is no extract-files.sh
I have put the binaries in the correct folders like I did with AOSP ROMs but I get a boot loop at the bootlogo.
Click to expand...
Click to collapse
me too...same problem mate..try with THIS,is made by a guy (not found nick).It's for gsm maguro,if anyone want to use that on others gnex variants,some modifyes are needed.
after searching a lot,it seems that the extract-files it isn't available for cm10 yet and it doesn't sync with repo.place that in coreect folder and run it like every official scipts.
This,is the problems that i have from a month..tried without that,but build compile but don't works (same problems,no boot animation,and stuck at it.phone seems powered off)
there wont be a extract-files.sh in CM10 because it was changed to generate-packages.sh I believe.
generate-packages.sh looks like it.
I will try extract-files.sh as well. Together with:
https://github.com/CyanogenMod/android_device_samsung_maguro/blob/ics/setup-makefiles.sh
We need the stock OTA package and place it in the same dir as generate-packages.sh I think
We need this zip: yakju-ota-398337.zip
Googled it but no dice
btw: the 3.0.39-3.0.41 patches have been rejected already. Still no response for the real hotfixes yet
do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app
llohcyoing said:
do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did that. But I will end up with a boot loop anyway.
It's so depressing.
mbh87 you did realise you may have been missing setup-makefiles.sh ? You can copy that script from ics as well.
I am now compiling again.
Seen the reviews of your patches, I told you those changes to the PowerHAL would be problematic, PowerManager service ****s itself.
I built CM10 successfully with extract-files.sh he gave me. then I added another file and I have it.
franciscofranco said:
Seen the reviews of your patches, I told you those changes to the PowerHAL would be problematic, PowerManager service ****s itself.
Click to expand...
Click to collapse
I just noticed. I will try a different way. Thanks for telling me.
I removed the commit and changed it. This should work.
I also pushed extract-files.sh and setup-makefiles.sh for reviewing
flashed your cm10 0828, cpu settings set on but with your/cm10 kernel and trinity kernel (without their app). thx, nice work!
djjonastybe said:
I built CM10 successfully with extract-files.sh he gave me. then I added another file and I have it.
Click to expand...
Click to collapse
do you used mine extract-files.sh linked above?
QUOTE=llohcyoing;30811974]do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app[/QUOTE]
OP referred to "copying propriretary files" from phone...instead you refer to "copying proprietary drivers",both needed,but 2 distincts operations.me too did the drivers parts..but not the files part..
sert00 said:
do you used mine extract-files.sh linked above?
QUOTE=llohcyoing;30811974]do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
OP referred to "copying propriretary files" from phone...instead you refer to "copying proprietary drivers",both needed,but 2 distincts operations.me too did the drivers parts..but not the files part..[/QUOTE]
Do a repo sync. extract-files.sh is now excluded along with another file required to build CM10:
http://review.cyanogenmod.com/#/c/22331/
This should now work for everyone ! No need to do additional work that is not mentioned in the tutorial. Just execute the commands and you will be alright.
http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_9_(Linux)
The feautures i'd like to have:
- no conversion sms in mms after 3
- battery percent (text only)
- navbar mods
- call icon in contacts that works
- back button pressed to eliminate background apps
Some of those are included in JellyBro. If anyone can do that i would be to the 7th sky
Inviato dal mio Galaxy Nexus con Tapatalk 2
HTCDevil said:
...
- back button pressed to eliminate background apps
...
Click to expand...
Click to collapse
back button kill should be already there, its under settings->developer options
andQlimax said:
back button kill should be already there, its under settings->developer options
Click to expand...
Click to collapse
I know...but never works in my case.
Inviato dal mio Galaxy Nexus con Tapatalk 2
Related
As an exercise to figure out how all of this works, I'm currently trying to build an AOSP Cupcake image with the stock HTC kernel. From what Lox posted earlier, a lot still didn't work.. and I think this is right in line with issues we're finding overall. It's my starting point, and so I'm posting here about how I'm accomplishing things. Follow along if you'd like and post any issues you come up with.. or if you make it to the next step!
1. Get a stable development environment with the right tools. Ensure you follow all of the information on the Android Source [1] page to make sure you have the right versions of GCC and Java.
2. Follow the instructions here: http://github.com/kiall/cupcake_platform_vendor_htc_hero
Thanks to Lox for his original work on the platform vendor repo, and to kiall for spending time this weekend to help pare the process down to be as easy as possible. The more people we have building stock AOSP builds, the more eyes we have working on the hardware issue. Keep it up guys!
Thanks for the guide was looking for something similar this afternoon
I set same goal for myself, to build a AOSP Cupcake ROM from the source. I have a question, though. What exactly is the purpose of loxK's cupcake_platform_vendor_htc_hero repo? I suspect it has something to do with the boot process since there are some init files..
And thanks for the guide!
Samek said:
I set same goal for myself, to build a AOSP Cupcake ROM from the source. I have a question, though. What exactly is the purpose of loxK's cupcake_platform_vendor_htc_hero repo? I suspect it has something to do with the boot process since there are some init files..
And thanks for the guide!
Click to expand...
Click to collapse
That is the product description that describes the device specific stuff needed to build for the Hero. Like what proprietary files needs to be saved, device specific init files, etc etc.
Would you guys mind deleting your posts above.. so I can have a bit more space to work?
Known Issues
Make fails with "No module defined for the given PRODUCT_POLICY (android.policy_phone)."
Make the following change to build/tools/findleaves.sh: https://review.source.android.com/#patch,sidebyside,9284,1,tools/findleaves.sh
On point 6, I assume you mean BoardConfig.mk and not BuildConfig.mk, right?
Yep, sorry =)
By the way, if you want WLAN, you can compile the driver from the AOSP tree, something like this:
Code:
[email protected]:~/android/src/cupcake/system/wlan/ti/sta_dk_4_0_4_32$ make KERNEL_DIR=~/android/kernel/kernel_hero
~/android/src/cupcake is my AOSP dir.
~/android/kernel/kernel_hero is where my Hero kernel source is.
This drops a wlan.ko in the current dir that you can get into your update package, make sure you get the correct wpa_supplicant startup for it (check from the normal hero rom).
Bluetooth stuff is also in system/bluetooth dir in AOSP tree. I've not messed so much with it, don't use BT myself, but it looks like it's all in there to make it function.
Headset is probably just some keycodes in an XML file, it seems to register like normal keystrokes. There are some h2w_headset (or something like that) files on the release roms, have a look at those.
And also, thanks for this nice clean guide jnwhiteh, my old AOSP build dir was a mess. So this was nice way for me to clean it up and at the same time check your guide
My suggestion is that we keep this thread for discussions regardning it, and maybe keep an actual up to date guide on the wiki, what do you think?
I've forked loxK's vendor stuff on github, and am adding as much of this as I can.. still a WIP
http://github.com/kiall/cupcake_platform_vendor_htc_hero
Hopefully I'll be able to put as much as possible of this in there so we can build with far less steps!
Thanks jnwhiteh
Also ... if anyone wants commit on the repo (esp jnwhiteh!) let me know...
like the progress i see
keep it up you guys, and thanx for the great how-to, will try it out as soon as i got some sparetime
I've got this process down to...
1. Get a stable development environment with the right tools.
2. Create a .repo/local_manifest.xml with the following contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="git://github.com/" />
<project path="vendor/htc/hero" name="kiall/cupcake_platform_vendor_htc_hero" revision="refs/heads/master" remote="github" />
</manifest>
3. repo sync
4. cd build && git cherry-pick 1e0847c2fcbe1b95464f32a719d2b9e620d1e6ec && git cherry-pick 6ea3b8856d656752c0310ca237ed99e7451be83b && cd ../system/core/ && git cherry-pick 2a63bb7abf1b27a7a2e8fd5951d77f71a2f290d4 && cd ../..
5. cd vendor/htc/hero/ && ./extract-files.sh && cd ../..
6. Download a recovery image from here and save it as recovery.img (I'll likely remove this part..)
7. make -j4 otapackage
8. .. Apply the update.zip generated ... no changes necessary
I'll update the github repo with this in a bit
I've pushed my changes to http://github.com/kiall/cupcake_platform_vendor_htc_hero
There is an updated readme / instructions at that page!
Right now - this is 99.9% jnwhiteh's stuff, just slightly more "automated"..
Thanks jnwhiteh!
Great work guys. At least some other guys to work on Hero developpement.
May I suggest a central git repo ? I can add you as collaborators to my git if you wish so you could submit your own patches with your names.
Yep, that would work for me, we'll see what kiall wants to do =)
jnwhiteh said:
Yep, that would work for me, we'll see what kiall wants to do =)
Click to expand...
Click to collapse
works for me aswell - only thing is, I've got *loads* of changes in my fork.. its git after all... we can pull and push each others changes pretty easy!
So, the issues that we're having:
Headphone:
Everything appears to start fine and the hardware/software properly detects the plugging in and unplugging of headphones, but it doesn't actually change the sound output. It says, instead, that it's ignoring the switch:
Camera:
Force close on the camera application
Bluetooth:
SIGSEGV
Trackball
Does not work
Actually, the issue with the headphone isn't due to some missing parts in your builds : http://code.google.com/p/android/issues/detail?id=2534
That's using the HTC heaphone_adapter_, which we don't have on the Hero. We can certainly try to patch AOSP and check it.. but the G1 uses an external usb adapter, and that's whats been reported as broken. One person there says they have a Sprint HTC Hero, but again...
Thanks!
Oups, I had no idea that an adapter was needed on some HTC device, my bad...
Np =) It still might be related, but I doubt it.
Here we go
Common gingerbread-samsung git branch for all of us
This branch contains the fixed Gingerbread source (compiling and working) everyone of us may use as reference git repository.
Fixed in this source:
- all cleaned up gitignores
- missing FSR in Makefile
Take also a look at the updated README.txt that will explain you how to compile and get it working with modules
Also: makes sure you disable, in .config:
[*] Automatically append version information to the version string in menuconfig or CONFIG_LOCALVERSION_AUTO in .config
It will help each developer to exchange patches easily because of the common starting point.
bilboa1 said:
What supercurio means, is that he's offering to have a common GIT repository for the official Samsung kernel of the GT-I9000 (and similar phones).
The GIT tree would contain only Samsung drops and possible other upstream fixes/changes (the kernel being loosely based on the Nexus S kernel, there's at least Samsung and Google as different upstream), as well as bug fixes. No new features etc except maybe Voodoo.
The advantage of that is that the ones not using GIT yet could fork it and make their own kernel variation on a STABLE base. They could also issue pull requests for fixes they made, which would profit everyone. That's the open-source spirit and way of doing things efficiently by the way.
Note that the current GIT already contains fixes for compiling and using Samsung's GB sources with Samsung's firmwares (and binary modules).
I certainly support this idea.
Click to expand...
Click to collapse
How you can fork this repository:
- clone it via github directly
or, if you prefer keeping only this gingerbread branch directly, on your dev computer:
Code:
git clone git://github.com/project-voodoo/linux_gt-i9000.git -b gingerbread-samsung
cd linux_gt-i9000
git remote rm origin
git remote add origin git://your-new-remote-repository.git
git remote add common git://github.com/project-voodoo/linux_gt-i9000.git
This way, for people re-using Vodooo sound for example, it will be as easy as:
Code:
git fetch common
git merge gingerbread-voodoo-sound
If you have more idea of collaboration like that, express yourself
FAQ:
Q: Bleh! I hate this Kernel/ directory.
A: Yes, this was the case for the original commits but now it's a standard Linux repository with everything on its root.
But it didn't worked as expected, so I had to make the change, sorry for the inconvenience to the early adopters.
Q: What happens when Samsung update their source code tarballs
A: I'll update the common git repository accordingly (hopefully fast enough for you)
On your side, all you'll need to do will is.
Code:
git fetch common
− or git fetch git://github.com/project-voodoo/linux_gt-i9000.git
git merge gingerbread-samsung
Say good bye to messy tarballs!
PS: if you're looking to initramfs, take a shot at https://github.com/project-voodoo/samsung_initramfs − contribution welcome.
Good idea, I second that, it will be easier
wrong link
Github reads http://project-voodo.org/
What supercurio means, is that he's offering to have a common GIT repository for the official Samsung kernel of the GT-I9000 (and similar phones).
The GIT tree would contain only Samsung drops and possible other upstream fixes/changes (the kernel being loosely based on the Nexus S kernel, there's at least Samsung and Google as different upstream), as well as bug fixes. No new features etc except maybe Voodoo.
The advantage of that is that the ones not using GIT yet could fork it and make their own kernel variation on a STABLE base. They could also issue pull requests for fixes they made, which would profit everyone. That's the open-source spirit and way of doing things efficiently by the way.
Note that the current GIT already contains fixes for compiling and using Samsung's GB sources with Samsung's firmwares (and binary modules).
Forking in git hub is VERY VERY easy btw.
I certainly support this idea.
Awesome! - I also support this idea
United Galaxy S Developers
Nice idea! Perfect spirit of open source
I hope good things come out og this.
Great move Supercurio - once again !
Simply awesome men
Will the github include the multitouch fix(SGS only using two fingers rather than multiple fingers) that affects Google Maps rotation?
pikachu01 said:
Will the github include the multitouch fix(SGS only using two fingers rather than multiple fingers) that affects Google Maps rotation?
Click to expand...
Click to collapse
The gingerbread-samsung branch promoted here will only contain Samsung kernel sources and won't interfere with other developers modifications.
Only exception is if this source is broken and needs something to work, like nikademus's patch: https://github.com/project-voodoo/linux_gt-i9000/commit/6c8f989f58999770d23236bb172c3a4e1c80586b
It seems that JVK and JVB was pulled from Kies because of an update problem. Looks like we're going to have new ROMs to play with in a week or two (maybe less)
Edit: What about the SSL fix (http://forum.xda-developers.com/showthread.php?t=1040005)
Great, good idea. That's how community development should work!
zorxd said:
Great, good idea. That's how community development should work!
Click to expand...
Click to collapse
Agreed! Thanks for getting things started Supercurio! Now I have to start making a Vibrant branch.
Any chance this code will boot with preempt enabled? Does the MTD driver work with the OneNAND partitions like the NS code does? I'd kind of like to get away from FSR/RFS and such....
Still cloning...
ttabbal said:
Any chance this code will boot with preempt enabled? Does the MTD driver work with the OneNAND partitions like the NS code does? I'd kind of like to get away from FSR/RFS and such....
Still cloning...
Click to expand...
Click to collapse
The code has many similarities with Nexus S one (build from it IMO) and is preempt too
Just a note, I had to edit the Makefile to set the crosscompile variable to the right path
Question: is the generated zImage flashable through ODIN? Don't we need to add the initramfs?
supercurio said:
The code has many similarities with Nexus S one (build from it IMO) and is preempt too
Click to expand...
Click to collapse
Excellent! I just did a defconfig to check it out and saw the preempt in there.. Nice to see Samsung fixing things up a little. Now I need to get a GB ROM to install so I can try to boot.
Thanks again. I'll send a pull request when I have a Vibrant branch ready. Going for minimal modifications, fix touch button mapping and such. People can add whatever they want after that. Now I need to learn the new code tree... wheee! Hopefully the basics are the same, getting the changes into an i9k froyo kernel is pretty easy.
zorxd said:
Just a note, I had to edit the Makefile to set the crosscompile variable to the right path
Question: is the generated zImage flashable through ODIN? Don't we need to add the initramfs?
Click to expand...
Click to collapse
You will need an initramfs... anyone have a default one we can start with for 2.3?
zImage will have to be in a TAR file to flash with Odin. Heimdall can flash a bare zImage, as can the SGS Kernel Flasher tool for Android.
Oh... think I saw a setting in "make menuconfig" for the cross-compiler prefix. Might be able to avoid Makefile mods....
Sorry for the newb question, but how do we generate the initramfs? I guess we could take the one from stock JVB. But how do we extract it and how do we combine our compiled kernel with it?
On a side note, I noticed that CFQ is the default scheduler. Isn't it better to use No-op for flash memory?
I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest.
Sorry about the long wait but, until recently there were a lot of issues regarding the ParanoidPrefs App, they are now fixed.
If your new, follow this link to see a quick tutorial on how to use Paranoid Preferences.
http://forum.xda-developers.com/showpost.php?p=31610815&postcount=2
Install Instructions
Full wipe
Flash zip --->
Both MDPI and Large MDPI are now hosted on Google code
https://code.google.com/p/paranoidandroid-kfire/downloads/list
Flash GApps for 4.1.2 ----> http://goo.im/gapps
First Boot may take a while, may also restart once before loading the UI.
Expect the same bugs as in Hashcodes CM10
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode the Paranoid Android team and rohan32 for his Paranoid preferences guide.
Changelog
Code:
[B][U]PA Otter 08[/U][/B]
PA 2.54 Changes
* Fixed after breaking Phablet Mode Navigation Bar
* CM Bugfixes and updates
Full Changes can be seen in the ParanoidAndroid Github http://github.com/ParanoidAndroid
Device Changes:
Includes hashcodes latest kernel updates.
[B][U]PA Otter 03[/U][/B]
10/7
re-uploaded with calculator FC fixed
[U]Paranoid Android 2.17 Changes[/U]
New toggles style. They're unified now to all possible UIs
Navigation bar transparency (i9100)
Double token encryption for security
Double ime button fixed (aosp bug)
Gmail crashes fixed (app bug)
Google now hold-off delay fixed after sysUI restart (aosp bug)
Double notification ticket avatar fixed (aosp bug)
Memory leak fixed by CM! (i9100). Use only stock kernel for now, most of custom kernels won't boot at all untill changes made to fit new blobs / mali code.
[B][U]pa otter 02[/U][/B]
[U]Paranoid Changes[/U]
Button panel fixes, also in landscape
Transparent statusbar (navbar comes soon)
4.1.1_r6 from aosp
Lag fix for Nexus devices
Nexus 7 new hybrid properties
Backup/restore is 100% fixed
SuperSU instead of SuperUser
new ParanoidWallpapers app including solid color selection
Moar stuff!
[U]Device Changes[/U]
Charging is now fixed. Including basic OTG support.
Backlight / Panel driver updated. This was probably causing some of the battery drain.
Current CM10 and Kernel info can be found here.
http://forum.xda-developers.com/showpost.php?p=24665559&postcount=1
//These changelogs are from the respective posts from the Paranoid Android Team, and Hashcode
Waited for PA for the fire
Will test asap and report back.
Sent from my GT-I9300 using xda app-developers app
Reserved
Sent from my PC36100 using xda premium
I've been really excited about this one. Can't wait to see how it turns out.
johnwayne007 said:
I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest. So far it seems to work decently on the Fire although it is scaled kinda small more for a 10" tablet. If I can figure out how to change that and people are interested i'll keep posting these.
Install Instructions
Full wipe
Flash zip ---> http://www.mediafire.com/?6i49oip6klii5q0 MD5: C4D46F46C9F92CA374FAB2852F6F0309
Flash GApps ----> http://goo.im/gapps
First Boot may take a while
Expect the same bugs as in Hashcodes CM10
I have also noticed that when you make a change in the Paranoid Preferences app and it reboots, it reboots into recovery. I'll see if i can figure out why.
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode and the Paranoid Android team!
Click to expand...
Click to collapse
Thanks for your Rom!
Paranoid Android's Rom in Nexus 7 is Perfect!
Hope this perfect for Kindle Fire.
Thanks for this! I actually like the small bars, it makes the screen look bigger, but I loathe the extended notification.
Update: Somehow, I got it to normal.
wow, great news! I'll try this soon! ty
Is this with the latest kernel release.
Sent from my Amazon Kindle Fire using XDA Premium HD app
What's the score on antutu?
Solid-Dado said:
What's the score on antutu?
Click to expand...
Click to collapse
It is 6630.
Sent from my Amazon Kindle Fire using XDA Premium HD app
I synced the repos just before building so as far as i know it's current with with Hashcodes latest kernel source.
Sent from my HTC One XL using xda premium
johnwayne007 said:
I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest. So far it seems to work decently on the Fire although it is scaled kinda small more for a 10" tablet. If I can figure out how to change that and people are interested i'll keep posting these.
If your new, you can change the app size in paranoid preferences, in the apps part. Find the app in the list and change the size for the app there, its the first option. Screenshots in second post.
Install Instructions
Full wipe
Flash zip ---> http://www.mediafire.com/?6i49oip6klii5q0 MD5: C4D46F46C9F92CA374FAB2852F6F0309
Flash GApps ----> http://goo.im/gapps
First Boot may take a while
Expect the same bugs as in Hashcodes CM10
I have also noticed that when you make a change in the Paranoid Preferences app and it reboots, it reboots into recovery. I'll see if i can figure out why.
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode and the Paranoid Android team!
Click to expand...
Click to collapse
Paranoid Android team told me the 2.12 isn't stable, but 2.13 is stable.
When i test the 2.12 Rom you provided, the Rom is surely not stable.
The font size is too small in the Setting. I can't run Antutu benchmark to test, can't run Goomanager to get update unless i reboot my KF.
Can change the sources to 2.13?
Thanks!
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Solid-Dado said:
What's the score on antutu?
Click to expand...
Click to collapse
I test it, the score is 6620.
Agreed, I'll resync and rebuild. But you may also want to change the size of the app where the font is too small, I did that in my settings in order to make it easier to read/use. Instructions to do so are in first post with Screenshots in the bottom of the second post.
Sent from my HTC One XL using xda premium
johnwayne007 said:
Agreed, I'll resync and rebuild. But you may also want to change the size of the app where the font is too small, I did that in my settings in order to make it easier to read/use. Instructions to do so are in first post with Screenshots in the bottom of the second post.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />
ive been waiting on this for a while. i attempted to port it a while back but i had absolutely no time and of course, no experience either. so thanks man! and our you please update it to the stable version on 2.13 this one is not as stable and has bugs
twa_priv said:
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />
Click to expand...
Click to collapse
Cool thanks for that, when I sync tonight I'll make sure to update the manifest.
Sent from my Amazon Kindle Fire using XDA Premium HD app
johnwayne007 said:
Cool thanks for that, when I sync tonight I'll make sure to update the manifest.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Click to expand...
Click to collapse
Looks awesome. I will have to give it a good try this weekend after exams. I had PA on my galaxy nexus and loved it. Will be awesome to mess with the DPI for some apps that could display a little better on the fire.
Very interesting. Sub'n to this thread. Pa on the fire actually makes sense.
twa_priv said:
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />
Click to expand...
Click to collapse
So, i changed that in my local manifest synced and built, now i get a bootloop and ADB wont recognize the device to get a logcat. Any suggestions?
http://pastebin.com/VYGMHV6Q
http://pastebin.com/YCYAk8sJ
Anyone with UART or USB access to u-boot willing to help with a dev project?
Devs only ATM, too many serious bugs
And there is the possibility of screen damage
If it hardlocks with papyrus ic on
test build #1 pulled due to poweroff/screen burnin bug
Test build #1: http://forum.xda-developers.com/showpost.php?p=60336716&postcount=14
Test build #2: http://forum.xda-developers.com/showpost.php?p=60453540&postcount=74
Test build #3: http://forum.xda-developers.com/showpost.php?p=60677266&postcount=136
Kernel Tree: https://github.com/kfazz/android_kernel_bn_zoom2/tree/nook_nst_3.0
zoom2 device tree: https://github.com/kfazz/android_device_bn_zoom2
vendor tree: https://github.com/kfazz/propietary_vendor_bn.git
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_build" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<remove-project name="CyanogenMod/android_frameworks_native" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="frameworks/base" name="kfazz/android_frameworks_base" revision="nook"/>
<project path="frameworks/native" name="kfazz/android_frameworks_native" revision="nook"/>
<project path="bootable/recovery" name="TeamWin/Team-Win-Recovery-Project" revision="android-5.1"/>
<project path="build" name="kfazz/android_build" revision="nook"/>
<project path="device/bn/zoom2" name="kfazz/android_device_bn_zoom2" revision="master"/>
<project path="kernel/bn/zoom2" name="kfazz/android_kernel_bn_zoom2" revision="nook_nst_3.0"/>
<project path="vendor/bn" name="kfazz/propietary_vendor_bn" revision="master"/>
</manifest>
Done:
Kernel 3.0.8 boots
Zoom2 devicetree
Cm11 boots
Twrp boots and installs ROM
Wip:
Ghosting
Ram usage
Suspend
To do:
WiFi sleep of death,
USB(works, but kinda slow) fixed adb gets ~4mb sec mtp gets ~2.8
Integrate epdcontroller in framework (partially done)
Pngcrush grayscale all images done, by adding back custom squisher to android/build
Fastmode,
multitouch, done, using 1.3.1 zforce driver + changes based on http://lwn.net/Articles/572311/
USB host not sure what the limit is but a 100mA usb mouse works without a powered hub, and a 200mA usb stick doesn't
Themeing
Gapps don't work (but too much lowram lag to be practical)
kfazz said:
Anyone with UART or USB access to u-boot willing to help with a dev project?
Devs only ATM, too many serious bugs
And there is the possibility of screen damage
If it hardlocks with papyrus ic on
Done:
Kernel 3.0.8 boots
Zoom2 devicetree
Cm11 boots
Twrp boots and installs ROM
Wip:
Ghosting
Ram usage
Suspend
To do:
WiFi sleep of death, USB, fastmode
Integrate epdcontroller in framework
Pngcrush grayscale all images
Fastmode, multitouch, USB host, etc
Themeing
Gapps don't work
Click to expand...
Click to collapse
Woah, this looks sick! I'd be glad to help you in any way I can. I've got a Nook Touch Glow running a customized version of the 1337 ROM, a modded framework-res.apk, and a modded Settings.apk (see my sig for full specifications). Let me know how I can assist!
By the way, I'm inviting you to my Nook Touch Devs group now, so we can talk in there.
ИΘΘK¡€ said:
Woah, this looks sick! I'd be glad to help you in any way I can. I've got a Nook Touch Glow running a customized version of the 1337 ROM, a modded framework-res.apk, and a modded Settings.apk (see my sig for full specifications). Let me know how I can assist!
By the way, I'm inviting you to my Nook Touch Devs group now, so we can talk in there.
Click to expand...
Click to collapse
if you'd be willing to try compiling it, javifo has a u-boot tree that looks like it supports ttyUSB.
https://github.com/javifo/NST/tree/master/u-boot
I'm not sure if my kernel supports usb because my usb port is broken, but if you can get u-boot access over usb
i'll try to build a kernel and bootscript that will be debuggable over usb.
My current setup is completely self contained on the sdcard and doesn't touch stock partitions except reading device specific data from /rom
kfazz said:
if you'd be willing to try compiling it, javifo has a u-boot tree that looks like it supports ttyUSB.
https://github.com/javifo/NST/tree/master/u-boot
I'm not sure if my kernel supports usb because my usb port is broken, but if you can get u-boot access over usb
i'll try to build a kernel and bootscript that will be debuggable over usb.
My current setup is completely self contained on the sdcard and doesn't touch stock partitions except reading device specific data from /rom
Click to expand...
Click to collapse
I'll give it a go on the weekend when I have some free time.
rendering from userspace
omap3pfb drawing modes:
pageflip mode: (non deferred)
turned on by writing a 1 to
/sys/devices/platform/omap3epfb.0/graphics/fb0/pgflip_refresh
apps that are unaware of bn's eink setup work fine.
this is how stock recovery uses the display, and also bootanimation on stock rom (i think).
Downside: ghosting, no control over waveform used to draw ( that i know of )
'command' mode.
display update is controlled by various private ioctl commands to the /dev/graphics/fb0 file.
ioctl -> * -> EpdService function -> EpdController function
OMAP3EPFB_IO_SET_REGION <- * <- configureRegion <- setRegion
OMAP3EPFB_IO_GET_REGION -> * -> UNUSED
OMAP3EPFB_IO_RESET_REGION <- * <- resetRegion <- resetRegion
OMAP3EPFB_IO_FILL_REGION < * <- fillRegion <- fillRegion
* is jni function calls in libandroidruntime.so
EpdController.epdRefresh writes to /sys/devices/platform/omap3epfb.0/graphics/fb0/epd_refresh
1 = Gray Clear
0 = update
epdDisable writes to /sys/class/graphics/fb0/epd_disable
value is timeout period in milliseconds
by themselves these writes and ioctls do nothing. the magic is in libui.so
stock rom calls OMAP3EPFB_IO_REQ_AREA_UPDATE in FramebufferNativeWindow::queueBuffer()
to update the display. No idea what logic the is used to decide when or whether to update.
Deferred Rendering:
this is turned off in kernel config for stock rom, and theres a typo in one of the ifdefed clauses which
leads me to believe this code path was abandoned early in development of the driver
i got it to work, but it doesn't seem to have many advantages over regular pageflip mode, and it's slow.
more info on deferred io: http://elinux.org/images/2/25/E_paper_Displays.pdf
anyone see any errors or have any insights as to how to implement this on Kitkat's graphics stack?
Oh Wow !!!
is that really a cm11(KITKAT) lock screen on a NST G ???
thanks for trying @kfazz following this thread, look forward to what will materialize out of this GREAT effort. kitkat is known to support low ram devices, hopefully it will accommodate our Nook Simple Touch activity which is only static read centric operations.
thanks for attempting
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
coolius said:
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
Click to expand...
Click to collapse
I to can't believe it. but this is cool. I hope it will be usefull since I thought the cm7 would have the highest version of cyanogenmod to work well on our devices.
coolius said:
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
Click to expand...
Click to collapse
dorfd1 said:
I to can't believe it. but this is cool. I hope it will be usefull since I thought the cm7 would have the highest version of cyanogenmod to work well on our devices.
Click to expand...
Click to collapse
I mean, the source to compile is right there, and he last updated it about an hour ago... Id compile a version to test for myself, but my server that I've used in the past for compiling android has yet to be set up again(new install )
Im honestly amazing that kfazz got it working, major props to him and hopefully this would allow more funtionality to come out of my old nook(s)
Edit: Oh, and this would also open up a wider range of usb devices to plug into the nook, as well as better compatibility for any new apps
---------- Post added at 10:54 PM ---------- Previous post was at 10:46 PM ----------
Also, to kfazz, Ive got an extra nook that doesnt matter if the screen gets damages(a new one is fairly cheap anyways), Id love to help you test out this project. I can also get access to the uart if needed, ill just have to pop open the case and solder on a few points(right? I last read about the access to the uart on the nook many months/year ago and I may be mistaken)
Yes, yes, and yes. UART access isn't strictly necessary, but there are a few issues I want to resolve before release. Mainly the circle animation android draws on loading screens, and auto partitioning sdcard. PS delete system/core/ uncrypt/android.mk and it should build. (Twrp conflict)
Wow, unbelievable we have WIP and moreover kitkat of all, Can't wait to try it out.
switching off all possible animation is best don't want to lose out on valuable battery time.
thanks Guys.
aiamuzz said:
Wow, unbelievable we have WIP and moreover kitkat of all, Can't wait to try it out.
switching off all possible animation is best don't want to lose out on valuable battery time.
thanks Guys.
Click to expand...
Click to collapse
I think the boot animation would have to be disabled.
Trying to be optimistic ...
A LG optimus Pro C660 with 256 RAM and less than 200MB internal storage for apps.
Came across this Lollipop
I believe Kitkat was also attemtpted for this device. but the ROM file is purged and no longer available.
If this device can operate as a full fledged phone, Will our device hold any promise for static reading purposes only ?
super buggy test build #1
super buggy test build #1:
update: pulled due to serious bugs. poweroff may fail with the screen on, buring in an image.
First up, to the best of my knowledge this rom won't melt your eink screen, wipe your sd, or cause your nook to spontaneously combust, but NO WARRANTIES.
With that out of the way, here is a test build. I'm not publishing it because it's done, but rather to encourage others to sync the source and try bulding it.
backup contents of sdcard first
write sd.img to a sdcard in the usual way. (sd_img.zip is attached to this post)
nook_nst_3.0 kernel: (this still has wifi sleep of death bug)
Same thing built with encore_merge kernelno wifi sleep bug, may have other problems, probably usb)
copy rom zip and md5 to nook's media partition
boot from sdcard, mount media
install rom (make sure signature verification is on)
reboot
if it doesn't boot hard reboot by pressing power and home for 9 seconds
"Where's the source?"
See the first post.,
Specifically the kernel in this rom was built from commit 7c944768270ec14736c7977b876a107e0a30b87f (current tip of nook_nst_3.0 branch)
except arch/arm/mach-omap2/board-3621-gossamer.c which was checked out from commit fbd1b8ccbebcb483eed158c5b6d51a4f44bbd2c4 (current tip of encore_merge branch)
"How can I help?"
sync my code and send me patches
sync my code and build it yourself
make a cm11 theme and test it
patch apps to use EpdController
What isn't helpful:
it's buggy. it's slow.
feature x is broken / app x doesn't work.
it's ugly. etc.
"Where're the gapps? I really want gapps, even though i know they will run all the time stealing my precious ram"
try the pico ones, or pico(uni). you probably won't be able to run browser after they're installed
http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Alternative: https://f-droid.org/ has a market app for free/foss software, and lost of reading apps
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Kralik said:
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Click to expand...
Click to collapse
For Ghosting, its basically the same as the regular OS, theres issues after a while of use, but I havent seen much from a few hours of trying out the build.
And also to kfazz, this build is awesome! Ive been trying to compile the OS, but have been having issues compiling(last time I compiled an android zip was like 2 years ago for my Nook Color), Although I am not done trying yet
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
kfazz said:
super buggy test build #1:
First up, to the best of my knowledge this rom won't melt your eink screen, wipe your sd, or cause your nook to spontaneously combust, but NO WARRANTIES.
With that out of the way, here is a test build. I'm not publishing it because it's done, but rather to encourage others to sync the source and try bulding it.
backup contents of sdcard first
;
;
;
Click to expand...
Click to collapse
Hey this is really great !!!
but too early for me to try ... not a techie who understands all this stuff.
We have CWM recovery installed and using yattaro&nookie's ROM
Can't this be flashed from CWM ?
Twrp Recovery a must ?
dombeef said:
For Ghosting, its basically the same as the regular OS, theres issues after a while of use, but I havent seen much from a few hours of trying out the build.
And also to kfazz, this build is awesome! Ive been trying to compile the OS, but have been having issues compiling(last time I compiled an android zip was like 2 years ago for my Nook Color), Although I am not done trying yet
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
Click to expand...
Click to collapse
Hey dombeef, great to hear you complied it and have flashed it on your device.
Looking forward to your feedback on its performance.
Excited !!!
Just remembered -- I have the Glowlight model. Is turning the light on/off and adjusting the level supported? Is it possible to customize the left/right side buttons?
Kralik said:
Just remembered -- I have the Glowlight model. Is turning the light on/off and adjusting the level supported? Is it possible to customize the left/right side buttons?
Click to expand...
Click to collapse
Well @Kralik as you can see its a little too early for that ... i believe this is not even a beta build !!!
am i right @kfazz ?
dombeef said:
...
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
Click to expand...
Click to collapse
change touch.orientationAware = 0 to touch.orientationAware = 1 in /system/usr/idc/zForce_Touchscreen.idc (device/bn/zoom2/prebuilt/usr/idc/zforce_ts.idc)
Fix tested and pushed
Kralik said:
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Click to expand...
Click to collapse
Ghosting: Screen updates in GU mode most of the time, so previous contents of screen are faintly visible.
Wifi Sleep of Death: sometimes after the nook is in suspend for a while, the wifi chip doesn't power back on and toggling wifi from the android settings will cause the nook to lockup in a bad state.
Based on Demetris' LOS 14.1, with :
Android security patch level updates, currently 2020-02-05
tracking LA.BR.1.2.9 from CAF, currently 1.2.9_rb1.44
WIP upstream with linux-stable, currently upgraded from 3.10.49 to 3.10.68 3.10.75
SELinux enabled (better security, SafetyNet & PlayStore should be ok, if not check @tess1 clear caches post )
2018 fixes : MTP, battery consumption, camrecorder crash, wifi, OpenGL ES version, dualsim 6045K (update to MM first), lid & proximity sensor
known problems :
camrecording low brightness
mobile internet connectivity loss and battery drain after a while (days) : toggle airplane mode and back, or reboot
new problems : none known at the moment, but the ROM is not so thoroughly tested before publication
How to investigate and report problems :
sudo adb shell dmesg > dmesg.txt
sudo adb logcat > logcat.txt
sudo adb logcat -b radio > radio.txt
Credits : @FireLord, @Demetris, @Unjustified Dev and all the giants whose shoulders we stand upon !
Source code : Kernel | Device | Vendor trees | Local manifest : View attachment idol3.xml
Changes since previous build : see the build release post
Downloads : lineage-14.1-20200226-UNOFFICIAL-idol3.zip | other releases
Kernel alternative (cam might not work since 20190619 build) : overclocked kernel by @DepressedHedgehog
Reserved
Thanks a lot for sharing this build. Now that the method for restoring our phones to stock has been taken away from us, I'm hoping that more people will jump in and try to solve some of the few remaining issues with this ROM.
Personally I'd like to figure out why the Play Store is installing old versions of certain apps and listing other apps as being incompatible while they can be still sideloaded without any problem. I've found many threads on XDA with people complaining about the same issue but no solution that worked so far. Is this an issue with opengapps, or bad entries in the build.prop? I've compared with the original build.prop from stock 6.0.1 and tried changing values around but no success.
Also battery life seems a lot shorter with Nougat, and there is no way to find out which apps/processes are being power hungry as you have already pointed out.
Issues aside this ROM still makes this phone quite usable and stable compared with other ROM's I have tried so good job and I'm looking forward to testing out new builds.
new thread - we're open for business!
@vknecht once again, thanks for your continued efforts... I tried your Sept 12 release with opengapps Sept. 12 as well - the Play store continues to thwart our efforts in the same manner.
@upyisfar I found that the battery drain during sleep could be reduced to almost nil with the following settings:
- turn off WIFI during sleep - Settings-> WIFI -> Gear Icon -> Keep WIFI on during sleep -> change to....
- turn off Emergency Broadcasts - Settings -> ...More ->Emergency Broadcasts -> Uncheck all
20180918 build : add ptt_socket_app for better wifi and battery
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Battery updates to follow
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Click to expand...
Click to collapse
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
vknecht said:
[*]SELinux enabled (helps with safetynet basicIntegrity test ; also better security, but some glitches here and there)
[*]new problems : probably due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
tess1 said:
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
Click to expand...
Click to collapse
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
tess1 said:
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Click to expand...
Click to collapse
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
upyisfar said:
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
Click to expand...
Click to collapse
I think if it was in LOS it should appear here : https://github.com/LineageOS/android_system_extras/commits/cm-14.1/ext4_utils
upyisfar said:
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
Click to expand...
Click to collapse
I'm using Fedora 28 ; note that you'd have to update the local manifest ($ANDROID_ROOT/.repo/local_manifests/idol3.xml) using given kernel/device/vendor trees as linked in OP, so at the moment it should look like :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vknecht/android_device_alcatel_idol3" path="device/alcatel/idol3" remote="github" revision="fix-ptt_socket_app" />
<project name="vknecht/android_kernel_alcatel_msm8916" path="kernel/alcatel/msm8916" remote="github" revision="upstream-lxstable-cafrb144" />
<project name="vknecht/proprietary_vendor_alcatel" path="vendor/alcatel" remote="github" revision="fix-ptt_socket_app" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
(to use july kernel change revision to "upstream-lxstable").
For idol3 build environment setup help, feel free to send me private messages or join #idol3 on Freenode, or maybe even create a thread, for the more we are able to build, the better...
vknecht said:
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
Click to expand...
Click to collapse
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
tess1 said:
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
Click to expand...
Click to collapse
I've tried the july 3.10.68 kernel (used in 20180718 and 20180905 builds) with current device/vendor trees, and still G compat problems, so it leaves the Android/LineageOS diffs from 2018-06-05 to 2018-08-05 patch levels (afaik there was no 2018-07-05 for LOS 14.1 and there's no 2018-09-05 yet).
20180924 build : 2018-09-05 android security patch level
Only change is Android/LineageOS framework (repo sync) for 2018-09-05 update
Too sad, it doesn't seem to solve the some-apps-in-proeminent-vendor-store incompatibility problem...
@upyisfar : I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
lineage-14.1-20180924-UNOFFICIAL-idol3.zip | or OTA zip
Q
vknecht said:
I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
Click to expand...
Click to collapse
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
upyisfar said:
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
Click to expand...
Click to collapse
@upyisfar
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
@vknecht
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
Click to expand...
Click to collapse
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
Click to expand...
Click to collapse
OK. I was wondering if Alcatel was geo-blocking some countries seeing how some people have success and others don't. I'm in Canada too so I guess that isn't the issue. For now I'm more interested in trying to find a solution to the opengapps compatibility problem.
---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------
tess1 said:
[MENTION=9435528]
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
Click to expand...
Click to collapse
See these commits https://github.com/vknecht/propriet...mmit/f84888778905c179e0d49d7587bc5467248e4b01 and https://github.com/vknecht/android_...mmit/dc64e2c79616e33640a2680451e2fe5ab0152d89
... and the workaround for disabling the bogus 3rd camera mode
https://github.com/vknecht/propriet...mmit/b57afd7960943e0dc8f0c593ae25cb74b5351a3f
6045K / dualsim / multisim
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
vknecht said:
new problems : probablymaybe due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
Appears to be working since the 2 latest builds, with SELinux set to enforce:
[/COLOR]
upyisfar said:
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
Click to expand...
Click to collapse
SECONDED - Confirmed fixed! and the Play Store also reports that my Device is Certified under Play Protect Certification.
Thank you upyisfar
vknecht said:
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Click to expand...
Click to collapse
6045I single-sim here, can't test this, sorry.
BTW can you add "low brightness in camera video capture mode" to list of known issues in the op? thx