Related
Hey all,
Firstly I'll introduce myself as I'm relatively new around here. My name is Geoff (aka ravenge) and I'm a 22yo, IT Systems Support Manager in South Australia. Things that take up most of my time lately are Work, LANning and tinkering with my G1 that I've had since a few weeks after Optus released them in AU.
Since purchasing my phone, I've thoroughly enjoyed gaining root, and playing with the works of JF, TD, Haykuro and Cyanogen (to name a few). In a nutshell I've tried dozens of excellent ROMs thanks to these guys.
After much experimentation, I decided to move away from the shiny hero as I found it to be rather unreliable and relatively slow. I loved the HTC apps of Hr's Sapphire ports and I loved the speed of ION, then came Rogers, a fully finished, fully packaged rom made by HTC for Rogers in Canada. This meant that the HTC apps were stock and didn't need any porting, and more importantly the rom was designed for the G1 so it ran fantastically on my handset!
I loved the rom but, stock, I found it a little lacking in the features dept. Many people have repacked their own flavours of Rogers, but none fitted my desire for a 'complete' rom.
Since I rebuild my phone consistantly, I wanted a rom that has all the core applications that I use. firstly Apps2SD with ext3 had to be standard. I wanted superuser, terminal, mtt browser, and all the other goodies you've seen floating around the forums. I also wanted to change some options to AU standards so that i wouldn't need to do it later. An example was the Date format from MM-dd-yyyy to dd-MM-yyyy.
After much bug testing, and a LOT of help from awesome xda users such as Haykuro, Cyanogen, MarcusMaximus. I'm happy to have finally reached a stable build.
Starting with the original Rogers rom graciously provided by Haykuro here
History:
This Build is based on the Rogers rom provided by haykuro. I take no ownership for the original files, or any of the
modifications made (except where labelled otherwise).This Build would not be possible without the awesome works of: Haykuro,
JesusFreke, Cyanogen, TheDudeOfLife, and all the developers of the apps included. <3 your work!
To make it significantly easier to differentiate between my rom and other rogers repacks, I am nicknaming mine 'ramjet'.
r7 FEATURES LIST:
Optimisations from Cyanogen's 3.4.4 build:
Cyanogen's 2.6.27.25 kernel (anticipatory iosched, enabled multicast and max cpufreq at 528MHz)
boot.img
a2sd scripts - automatic A2SD using bind mounts
various other file system tools and libraries
AUTO Apps to SD - Standard:
As mentioned above, we're now using bind mounts. This means more stability and flexibility for filesystems. Apps to SD will automatically run for you with next to no setup required (apart from needing a partitioned SD card). If you don't have the partition, it will operate as per any build without a2sd (more or less)
Applications:
-All rogers specific apps removed
/system/app
+amazon mp3
+superuser
+Terminal Emulator
+Browser with multitouch (will possibly replace with HTC browser)
+bugreport.apk
+Google Voice Search
+Latest Google Maps
+spareparts
+updated Quick office to 1.0.1
+HTC Sync
+IM
pre-installed to /data/app
+Backup for root users
+apps2sd
+wifitether 1.51
+Fbook.apk
+Forecast Widget by Koxx
+mymaps 1.1.6
+smspopup 0.9.96
+linda file manager 1.2.10
+NetCounter 0.8
+Locale 0.611 beta
+Astrid 2.8.6
+TwitterRide 1.3.1
Cosmetics:
added images (my own)
in app/launcher.apk
transparent handle for app drawer (just because I prefer it)
in framework/framework-res.apk
battery depletion images with % included (cause I didn't like the battery icon going GREEN GREEN GREEN GREEN RED-FLAT)
NOTE this works off of modifications on the original images. As such, there are only levels at 0% 10% 20% 40% 60% 80% and 100%.
boot animation / audio copied from hero, cause its fancier and modified to include some build details and a picture of roger ramjet (note, Roger Ramjet the cartoon character is copyright of someone else, NOT ME)
3G:
A HTC lib was causing some problems for HQ youtube over 3G. Replacing with the lib from ION seems to fix it.
Audio Mod:
Max Volume mod by Meltus (V5.3+Bluetooth fix)
Dalvicvm:
dalvicvm from ION - cause it's shown speed improvements
Localisations:
Changed date format default to dd-MM-yyyy
Changed build.prop ro.product.locale.region=AU
Added Haykuro's APN List, modified by me to include the AU Carrier 'YES OPTUS' and many other AU carriers (that still need testing) http://forum.xda-developers.com/showthread.php?p=3891703
Added Optus voicemail config.
Changed default languages to en-AU for dialer and ime.
Click to expand...
Click to collapse
WHAT YOU NEED!
rooted g1 (duh)
I've just started using Cyanogen's recovery, it's great!
The Latest RADIO and SPL from Haykuro's here: ** Potential Bricking ** read up properly on this!
Apps2SD needs a Decent SD Card with an ext3 partiton. But a2sd is NOT a requirement to run this rom.
my rom: ravenge-ramjet-r7-signed-update-AU.zip
md5sum: f90b7db7768f6d431af079e97775e288
I recommend wiping, but it may not be necessary.]
The first boot will be very slow if you have lots of apps on your SD.
TODO:
APNS/Voicemail - Read up HERE
Homescreen customisation, such as TD's 5 home screens mod, when I can get my hands on the 'how to' doc.
Investigate ODEX for /system/app
FAQ:
Apps 2 SD: a lot of people have asked "Do I have to use apps to sd?" - you do not.
"if i had apps to sd before?" - thanks to cyanogen's handywork, it will automatically find what you have and set it up for you.
"can you port something from hero?" - probably not, the launchers / framework are different causing problems in most circumstances
"Do I need to wipe?" Probably. You may or may not need to wipe depending on where you've come from. You might be able to get away with just deleting cache (note cache may also be stored on your sd card from apps2sd and will need to be removed manually). If you get lots of force closes, chances are you need a wipe!
Has anyone made any themes? OPhone-V1.0 - ported by barakinflorida
P.S. I added a splash screen for those who know what it is.
If you have any problems, I'll do my best to support them. If you don't like my rom, use someone elses. If you have any useful suggestions, I'd love to hear them!
Regards,
ravenge
CREDITS:
This build was based on Haykuro's rogers.
In the past, Haykuro has been legendary at providing awesome HTC stuff ported from here and there, and a lot of the great roms that are around today are especially thanks to him.
If you would like to support Haykuro, you can buy him some nesquik!
I also got a lot of help, and used a lot of Cyaonogen's optimized android files and kernals from his latest builds. This helped me implement Apps2SD and get the build running nice and fast. For mor information about all of his great work, take a look here
Feel free to Buy Cyanogen a beer!
The AppstoSD2.apk Application comes straight from MarcusMaximus with an updated icon by me.
If you like this App please support Marcus by donating (aka purchasing it) in the Paid market.
MarcusMaximus and his Apps2SD thread is [http://tinyurl.com/n2ah4z]here.[/url]
As mentioned I have used Meltus's audio mod. The one I used is quite loud so you may prefer to check out Meltus' thread here and apply your own. Donate to Meltus here
I also believe that a lot of credit to certain parts of the android development should go to JesusFreke.
Go visit his Blog here and honour his work by donating here
The apks I included were from various sources and in general were extracted from other peoples builds, for example TheDude's 1.2b or Cyanogen or Haykuro's work. If I have forgotton to credit someone somewhere (which is pretty likely - SORRY!) Please PM me so I can give credit where it's due!
Click to expand...
Click to collapse
Previous versions:
r3 AU
r4 AU
r5a AU
r6 AU
Latest Revision Notes
UPDATES
Updated with r7
ravenge-ramjet-r7-signed-update-AU.zip
md5sum: f90b7db7768f6d431af079e97775e288
This patch includes some signifant changes to the guts of the build like the kernel and a2sd. If you experience problems, a wipe may be necessary.
+more useful apps
/data/app
astrid
locale
twitterride
+boot.img/kernel change to Cyanogen's 2.6.27.25 (anticipatory iosched, enabled multicast and max cpufreq at 528MHz)
This should fix a LOT of problems people were having, including the "coma" bug where the phone would run out of memory and wouldn't wake from standby.
a2sd now uses bind mounts (instead of aufs) allowing better stability and compatibility etc.
+replaced default google maps with newer one
+IM app. (let me know if I missed some files)
/system/app/IM.apk
/system/app/TmoImPlugin.apk
+replaced libhtc_ril.so with the one from ion. This should give '3G' and allow HQ youtube over 3G.
+boot.mp3 update
+localisation settings language default to en_AU for locale and dialer \customize\MNS\default.xml
+modified update-script (now closer to cyanogens) and
cleaned out xbin
Updated with r6
linky: ravenge-ramjet-r6-signed-update-AU.zip
md5sum:
a6c7e0eeb0145e5ca18e06e755a10d11
APPS
/system/app
+fix amazon.mp3
+google voice search (yay)
+spareparts
+updated Quick office to 1.0.1
+HTC Sync (W00t) seems to work too, which is a bonus
+IM (hopefully - someone please check)
/data/app
+FBook.apk
+updated Forecast Widget by Koxx - http://forum.xda-developers.com/showthread.php?t=511351
+added the google maps update 3.1.1 & mymaps 1.1.6 (to /data/app) uninstall it if you dont want it
+smspopup 0.9.96
+linda file manager 1.2.10
+NetCounter 0.8
Cosmetic
+new boot animation screen bkg (was bored lol)
Audio Mod
included Meltus' V5.3+bluetooth fix (if you prefer a different one, go see his thread)
default wallpaper switched
Free space:
with pre-installed apps
/data: 91904K total, 34336K used, 57568K available (block size 4096)
Without pre-installed apps
/data: 91904K total, 29760K used, 62144K available (block size 4096)
========================================================
Updated with r5a
ravenge-ramjet-r5a-signed-update-AU.zip
md5sum: 9d294c49d853ac0db67a9571d115898e
r5a: simply fixes a n00b mistake where I didn't upload the rom that included the new lines in the update-script.
r5:
+altered mount auto in a2sd to use busybox to avoid boot loop, allowing potential compatibility for other card types.
(though i'm still fairly certain that e2fsk and tune2fs are meant to convert the partition to ext3 file system anyway)
+Updated Meltus V4 (quality) loud mod. Sounds better than the V3 though not quite as loud.
+moved some apps to /data/app to clear up some system space and make it possible to update/remove them as normal if required. (this required an update to the update-script)
========================================================
Updated with r4
Since I don't have a lot of room left in my initial post at the moment (needs tidying) here is my changelog for r4
the major focus being Default APNs!
(thanks to shellite for having more foresight than me and getting his original files backed up!)
Changelog:
ravenge-rogers-r4-signed-update-AU.zip 09-06-2009
Code:
apns-conf fixed for AU and included more carriers (needs testing)
optus internet -works
optus mms -works
IDEAS -untested
IDEAS MMS -untested
Three -untested
Three MMS -untested
Vodafone Internet -untested
Vodafone MMS -untested
Telstra 3G EDGE GPRS -untested
Telstra GPRS -untested
Telstra 3G Databundle -untested
Telstra 3G Pay by time -untested
Vodafone NZ -untested
Vodafone NZ MMS -untested
voicemail-conf added for Optus AU. If anyone has more carriers to add, let me know
updated build.prop
I could use some help confirming/fixing any of the APNs I used, as I'm with OPTUS I don't have the opportunity to work with the other carriers. I'd love to hear from you.
I'll try this out, sounds good! Its good to see an Australian build pop up, now I won't have to deal with switching date formats every time xP
in case you didn't know.. it's Rogers without the D.. they're a mobile carrier in Canada.
sounds good.. but does this only work with ext3?? i have ext2
yingjai said:
in case you didn't know.. it's Rogers without the D.. they're a mobile carrier in Canada.
Click to expand...
Click to collapse
haha thanks, correcting now
robpet2 said:
sounds good.. but does this only work with ext3?? i have ext2
Click to expand...
Click to collapse
Theoretically, cyanogen's script converts the filesystem to ext3 to make it compatible, I'm yet to try it though. (adding it to my TODO list)
Edit: Apologies for the double post. didn't realise I couldn't delete unwanted posts.
holy moly the HTC start-up sound went through my ear drums~ I am still at the HTC screen but I guess it's gonna take a little longer than ususal due to the extensive inclusion of this and that I think I'm gonna love this thanks Ravenge~ I did a wipe and it works now... hey hold on... omg... My Apps2SD is working too!!... my ext2 was corrupted though I just kept on using the same sd regardless the reduced capacity... (Too busy these days) now it mounts back nicely...
wow... wow... this is insane... btw u have all the goodies working flawlessly.
man i told my slef i was not going to try rogers but...ok you talked me into to it.
Use busybox to mount -t auto
ravenge said:
NOTE: Originally this is supposed to support ext2 however, leaving mount -t auto caused a boot loop in my build. I imagine something is missing.
If anyone could provide some insight, this would be awesome. For the time being ONLY ext3 is supported.
Click to expand...
Click to collapse
The stock 'mount' binary doesn't support an auto mount. If you do a logcat, you'll see it's failing to mount the second partition and therefore can't access the dalvik cache, which is required for a full boot.
The fix is easy, just use 'busybox mount' instead of the regular 'mount'. You can even do this from an adb shell from inside the boot loop and you'll see the system finishes booting and comes online
Kinslayer81 said:
The fix is easy, just use 'busybox mount' instead of the regular 'mount'. You can even do this from an adb shell from inside the boot loop and you'll see the system finishes booting and comes online
Click to expand...
Click to collapse
Great tip, I'll give that a shot for future releases.
As I'm a lazy sod and dont want to mess around flashing my phone again tonight, (hopefully I didnt miss this in your first post) is your AU build based on EU firmware? (eg, no myfaves) ?
just downloaded your rom and about to flash it....hope all goes well............ya it does.....its great as of now will post regular feedback on this.....
thank you....
screenshots plz
sry 4 being a noob,but does anyone have any screenshots ?
looks almost the same as the other original build but anyway the sound is way too loud and the meltus sound thing isnt working can you build the update with the v4 best quality pre-installed thanks really fast I ran a script to odex all system apps and its running really fast love it
5 homescreen launcher.apk
props just flashed your rom, so far so good
Crazy Nice
i just went on ahead and flashed it.. and im lovin this its smooth and fast.. my apps 2 sd worked as a charm..the responsivness is accurate..so far what i notice is a big change in my opinion keep up the good work. would like to see more like a working flash player 10 or having your g1 play any type in movie format..
@ N3xt2N0N3
N3xt2N0N3 said:
5 homescreen launcher.apk
Click to expand...
Click to collapse
Doesnt work dude......says cannot install on this system......
the Rom is very stable and is very good......mixture of all available rom's but the genius has picked up the best among all and given us on one shot....
good work......thank u.....
Sorry to sound ignorant, but I've never used any Apps2SD modification.
Do I need an Apps2SD capable card to run this rom, or will it work fine without it?
this is a work-in-progress development project for porting CyanogenMod 9 (ICS/4.0.4) and ClockworkMod Recovery 5 to Amlogic AML8726-M tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* project page
http://androtab.info/cyanogenmod/amlogic/
* supported tablets
ainol NOVO8 Advanced
Digma iDx7 (a.k.a. WayteQ xPAD-70)
Digma iDx10/iDx10 3G
* CM9 current status (2012/4/12)
not work:
3G, camera, and many things which you expect to work
work:
3D, accelerometer, audio, gapps, hardware accelerated video, HDMI, internal NAND flash, remote controller, SD card, touchscreen, USB host/device, vibrator, wlan
* changelog
refer git log
* resources
http://www.cyanogenmod.com/ (What is CyanogenMod?)
http://source.android.com/source/
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
http://goo-inside.me/gapps (Google Apps)
http://review.cyanogenmod.com/#q,status:merged,n,z (CyanogenMod merged changes)
https://github.com/naobsd/cm_bootable_recovery/compare/ics...ics-naobsd (placeholder to cherry-pick changes)
https://github.com/naobsd/cm_external_e2fsprogs/compare/ics...ics-naobsd (placeholder to cherry-pick changes)
https://github.com/naobsd/cm_system_core/compare/ics...ics-naobsd (placeholder to cherry-pick changes)
https://github.com/naobsd/cm_device_amlogic_aml8726m
* links
http://www.chinadigitalcomm.com/ainol-mid-f105/source-code-ainol-novo8-android-t10767.html
http://forum.xda-developers.com/showthread.php?t=1478734 (psquare's CM7/9 for NOVO8 Advanced)
http://ct704ct1002.forumgratuit.org/t711-cyanogen-9-sur-ct704-et-ct1002 (users' forum for CT704/1002)
* How to boot ClockworkMod Recovery 5
1. download recovery.zip and unzip it
2. put aml_autoscript and uImage_cwm on root of SD card
3. insert SD card
4. power on
you can flash uImage_cwm directly into recovery partition. then, you can boot recovery with VOL+ + POWER.
ClockworkMod Recovery 5 can't install official update.zip. if you want to reinstall official ROM, use uImage_recovery in official ROM.
* How to control ClockworkMod Recovery 5
for ainol NOVO8 Advanced
VOL-/jogball down: down, VOL+/jogball up: up, POWER/jogball push: select, SEARCH/BACK: back
* How to install CyanogenMod 9
1. download update.zip and put it on internal NAND flash or SD card (don't unzip it)
2. reboot recovery
3. install update.zip
4. wipe data/factory reset *1
5. reboot
*1 only if you are upgrading from non-CM9 ROM (CM9 1st install)
* issues
- mic input(audio record) doesn't work.
- accelerometer orientation on Digma iDx7 is wrong. please disable it for now.
- scaling and rotating are not worked for hardware accelerated video. video is always displayed as fullscreen and landscape. please use media player which has fullscreen mode (no UI parts).
- to use USB mass storage mode, /sdcard needs to be mounted. i.e. SD card need to be inserted, or, internal NAND flash need to be mounted on /sdcard (by Settings -> Storage -> Storage configuration -> Use internal storage).
- TS calibration is missing. resistive touch screen will not work.
* random notes
- external SD card and internal NAND flash
on CWM, external SD card is mounted on /sdcard. internal NAND flash is mounted on /emmc and referred as "internal SD card".
on CM9, external SD card is mounted on /mnt/sdcard. internal NAND flash is mounted on /mnt/nand.
- ubifs
no ubifs support for now. which is better, yaffs2 or ubifs?
ubifs should be supported if clockworkdmod is used as backup tool for official rom.
- rootfs
currently ramdisk in kernel is used as rootfs. modifying kernel by hand is not so smart.
should try to make initrd separately and pass it via bootm 2nd arg.
- reboot
reboot doesn't work. if power is connected, reboot will work, but power off also act as reboot
reboot recovery/bootloader doesn't work at all. use VOL+ while power on.
- memsicd
is running to use accelerometer (and magnetic field sensor). it also tweak axes by ro.sf.hwrotation and ro.sf.gsensorposition.
- magnetic field sensor
is detected but not worked/not existed. magnetic field aware apps may not work correctly.
hi
hello
works great.
You are really great.
your work with the de novo 8 will be finally a good tablet.
sorry I do not speak English
good luck
Thank you very much from France for your work !!!
I will try this version as soon as possible.
Bye.
First of all: Thank you! It looks great! ;
But, the "- no ubifs support" means I can't mount sd-card or connect internal memory to pc?
I tried, but it not works...
Thanks again!
bigdee888 said:
I can't mount sd-card or connect internal memory to pc?
I tried, but it not works...
Click to expand...
Click to collapse
thank you confirming "not work" things.
for ubifs, please learn about it. this project/thread is for developers.
smeexx said:
your work with the de novo 8 will be finally a good tablet.
Click to expand...
Click to collapse
I can't promise my CM7 port will be good for you. I'll do what I can do, but I can't do what you want.
thank you for your cooperation!
from my personal experience, probably some non-dev people will start to complain "XXX is not working! I need it! please support it asap!". and, 1 month after, "XXX is still not working! terrible! tell me current status of your work!".
this is development project. my files are just for dev people, and non-dev people who know dev work is really difficult or need a lot of time.
my git repo are pushed to github. anyone who can build android/cyanogenmod can build my CM7 for novo8 with it. (how to build is around here and there. don't ask here)
about me(currently only 1 dev here), I'll work for this project only on my free time. I don't have enough time as usual. nothing may be changed within a month. don't ask ETA even if I say "I'll do it soon".
as a fact, on my another project, some people waited some months to get working accelerometer.
test report is always welcome from everyone. but don't expect that issues/missing featues will be fixed if you can't fix yourself without effort.
if you don't like my CM7, please use another one. I never say my CM7 is best, I don't force people to use my CM7.
I'm looking ZT-280 gingerbread (it seems CM) rom. I think something can be used for us. e.g. they have latest mali modules
there is also Gadmei T720 (probably froyo) rom posted on www.chinadigitalcomm.com. I'll check it too.
if you know another rom for other AML8726-M based tablets, please tell me.
USB device function, mount from PC, seems to be working.
USB host function is also working.
paths in vold.fstab are wrong so SD card and USB disk can't be accessed in CM. I'll fix it in next image.
HDMI output can be enabled via set_display_mode.sh command. it may need to connect HDMI cable before booting. screen is not scaled. 720p is shifted, probably set_display_mode.sh need to be tweaked.
I need to check how it works on stock rom.
Its really great to see that some initial work is being done for that niche-tablet with great hardware potential.
I really can't await for the first working GB rom on the novo 8.
@fun_ As you mentioned yourself to have less time to work on the rom, would it be possible to share the source? As it might be a good base for other people to help improving your work.
Cheers
Toshimitsu said:
I really can't await for the first working GB rom on the novo 8.
Click to expand...
Click to collapse
"waiting" doesn't help this project at all. why you didn't try 1st?
Toshimitsu said:
@fun_ As you mentioned yourself to have less time to work on the rom, would it be possible to share the source? As it might be a good base for other people to help improving your work.
Click to expand...
Click to collapse
really soon unless no one prevent me by posting worthless question.
(for me, soon is one of which, within a day, within a week, within a month, within a year, or never happen)
--
I forgot to write (and did it just now) "don't ask ETA" on post#9.
HDMI output is tweaked. remote controller is working properly now.
20111023 files are uploaded.
repos are pushed to github. see OP. some tips should be added (will do later).
20111024 uploaded (replaced few hours ago)
fix small graphics issue
You are really cool man. Nice job.
Excellent development, Mr. fun_!
I plan to do a write up in my blog about this. As for your questions about Zenithink ZT280 of different form-factors, it's unclear whether they based on Android 2.3 or -- most probably for me, at least -- on Android 2.2.
Together with Ainol Novo 8 and Gadmei T820 there's another device looking like an Ainol's rebrand: Aigo M801.
Can anyone with this build make some screenshots, or better video clips and post them (link) here? Of interest are:
-- 2D (GUI rendering/video decoding and rendering) hardware acceleration/performance, preferably with some comparison to stock A2.2;
-- overal agility of the build, maybe some benchmarks;
-- what doesn't work at this point?
Thank you! Can't wait to publish this Mr fun_'s great breakthrough for my readers in English, Russian, Japanese.
aludal said:
I plan to do a write up in my blog about this. As for your questions about Zenithink ZT280 of different form-factors, it's unclear whether they based on Android 2.3 or -- most probably for me, at least -- on Android 2.2.
Click to expand...
Click to collapse
as I wrote Zenithink released 2.3 rom. and I found Pandigital Nova has 2.3.
aludal said:
Together with Ainol Novo 8 and Gadmei T820 there's another device looking like an Ainol's rebrand: Aigo M801.
Click to expand...
Click to collapse
I got my novo8 few weeks ago, until then I didn't care any amlogic tablets at all. I need more time to learn about them
aludal said:
Can anyone with this build make some screenshots, or better video clips and post them (link) here? Of interest are:
-- 2D (GUI rendering/video decoding and rendering) hardware acceleration/performance, preferably with some comparison to stock A2.2;
Click to expand...
Click to collapse
I think 2D is not so fast due to screen size. hardware video decoding doesn't work. I didn't use stock rom well (only few days). I need to reinstall stock rom to check some things.
aludal said:
-- overal agility of the build, maybe some benchmarks;
Click to expand...
Click to collapse
I'm not sure benchmark is meaningful at this stage. anyway, I'll post 0xbench result soon.
(but some 2D/3D score may not be reliable because it reaches limit(refresh rate) easily on 0xbench)
is there any other good benchmark app? I don't like Quadrant.
http://www.glbenchmark.com/ looks nice but I need to register to get result.
i/o may be slow. I feel lags e.g. while installing app.
aludal said:
-- what doesn't work at this point?
Click to expand...
Click to collapse
I'm not sure what/how works on stock yet "work" things are listed on OP.
please write review freely, but I don't think my CM7 port is excellent further development is needed to get excellent one. I can't promise I can do it.
thank you for your cooperation!
fun_ said:
as I wrote Zenithink released 2.3 rom. and I found Pandigital Nova has 2.3.
yes, I looked up these devices myself (was actually watching Nova since August), and then there's at least 3 models of Zenithink 280.
I got my novo8 few weeks ago, until then I didn't care any amlogic tablets at all. I need more time to learn about them
Hah! I admire your speed, Sir. CM7 Team must get you as their "official" developer ASAP. (In fact, I have a vested interest in that: I run CM7 on my Nook Color since last winter, and if you ask me, they stuck on hardware acceleration for Nook)
I think 2D is not so fast due to screen size. hardware video decoding doesn't work. I didn't use stock rom well (only few days). I need to reinstall stock rom to check some things.
Screen size/pixel count, or resolution has no effect on 2D HW accelerated rendering as long as Mali400 MP's limit on pixel count is not broken. 1280x768 is well within that limit. Hardware video decoding worked quite well in stock (A2.2) for 1080p/720p quite high bitrates, so please don't lose it, LOL.
I'm not sure benchmark is meaningful at this stage. anyway, I'll post 0xbench result soon.
(but some 2D/3D score may not be reliable because it reaches limit(refresh rate) easily on 0xbench)
is there any other good benchmark app? I don't like Quadrant.
Nobody likes Quadrant. It's the Quadrant of A2.2 vs. Quadrant of CM7 that matters, on the same Ainol Novo
http://www.glbenchmark.com/ looks nice but I need to register to get result.
i/o may be slow. I feel lags e.g. while installing app.
That would be an overkill, sir.http://media.xda-developers.com/images/smilies/tongue.gif. Usual Neocore, Nenamark scores will be fine.
I'm not sure what/how works on stock yet "work" things are listed on OP.
please write review freely, but I don't think my CM7 port is excellent further development is needed to get excellent one. I can't promise I can do it.
You achieved a TON already, during last 2-3 days. Question is, can you do ALSA/Open GL ES/NEON/stagefright work at least no worse than in stock A.2.2? Original/stock FW coders struggle with it since this April and stay at A2.2 still. Yet Nova has it, but the quality of HW support is questionable.
thank you for your cooperation!
Click to expand...
Click to collapse
I will do whatever I can in support of this development. Meanwhile, you're welcome to comment on my write-up in fineoils.blogspot.com
aludal said:
I will do whatever I can in support of this development. Meanwhile, you're welcome to comment on my write-up in fineoils.blogspot.com
Click to expand...
Click to collapse
yup. at least I need to comment about motoya font
Stuff that doesn't work: 3G/LTE, accelerometer, GPS, camera, and maybe some other stuff that I'm not remembering
Stuff that does work: GPU (full OpenGL 4.5 and Vulkan), sound, USB device and host, WiFi, Bluetooth, touchscreen (including stylus), SD/USB install
Downloads:
Linux4Tegra R24.1 beta (mirror) (updated on February 18th 2016)
Linux4Tegra R23.1 (mirror) (updated on November 21st 2015)
Linux4Tegra R21.4 (mirror) (updated on July 21st 2015)
Linux4Tegra R21.3 (mirror) (updated on March 9th 2015)
Installation instructions:
Install MultiROM (+ TWRP + touch support + patched kernel)
Download Linux4Tegra and install it through TWRP (Advanced -> MultiROM -> Add ROM)
Tips/notes:
To enable the on-screen keyboard during setup or login, press the blue icon in the corner and select on-screen keyboard from the menu that appears.
To enable the on-screen keyboard on desktop, run Onboard.
If your touch input becomes misaligned, install and run xinput-calibrator.
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Gnurou said:
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Click to expand...
Click to collapse
I've tried L4T 21.2, 19.3 and Lollipop. All of them need a small kernel patch (which might break HDMI, I have no idea) for the graphics to work, but apart from that they should all work fine for the most part.
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Edit: this actually isn't needed, I was just using the wrong cmdline
Getting Started
THESE INSTRUCTIONS ARE OUTDATED. CONSIDER USING THE PREBUILT INSTALLER FROM THE MAIN POST INSTEAD!
You need a computer with Linux installed and some free space (I don't have the exact numbers, but 5GB would probably be enough). On the tablet, you need 2-3GB of free space (on the internal memory), an unlocked bootloader , root and you need Busybox installed too.
On the computer, you'll need to compile your kernel first (this guide includes the compiler, and there's a prebuilt boot.img in the attachments if you want to skip this part). I recommend using https://github.com/Bogdacutu/STLinux-Kernel, with st8_linux_defconfig.
The initramfs is pretty simple, it just mounts the relevant system partitions and loads Linux from them: https://github.com/Bogdacutu/STLinux-Initramfs. You'll need to edit KERNEL_PATH in build.sh and make the kernel beforehand, then running build.sh will result in a boot.img which you can boot with fastboot:
Code:
fastboot boot new_boot.img -c "console=tty1 fbcon=map:10 fbcon=rotate:2 fbfix"
For the rootfs, Linux4Tegra is the easiest place to start from. All the Tegra K1 versions should work fine. For example, with R21.2: (the sudo is necessary there)
Code:
$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra124_Linux_R21.2.0_armhf.tbz2
$ tar xfvj Tegra124_Linux_R21.2.0_armhf.tbz2
$ cd Linux_for_Tegra
/Linux_for_Tegra$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar xfvj ../Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra/rootfs$ cd ..
/Linux_for_Tegra$ sudo ./apply_binaries.sh
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar cfvj ../rootfs.tar.bz2 .
The resulting rootfs.tar.bz2 you'll need to somehow get on the device. For the next part, I'll assume it's in /sdcard/rootfs.tar.bz2. You'll need to do this on the device (through ADB or through Terminal Emulator)
Code:
$ su
# cd data
/data# mkdir linux
/data# cd linux
/data/linux# tar xfvj ../media/0/rootfs.tar.bz2
Enabling Bluetooth with brcm_patchram_plus:
Code:
$ sudo brcm_patchram_plus -d --patchram /system/etc/firmware/bcm43241.hcd --baudrate 3000000 --enable_lpm --enable_hci --use_baudrate_for_download --no2bytes --tosleep 1000 /dev/ttyTHS2
Prebuilt boot images:
new_boot(80).img - working WiFi and sound
new_boot(90).img - added pointer emulation to touchscreen driver
new_boot(94).img - fixed Bluetooth stability
new_boot(114).img - fixed HDMI, added support for non-LTE partition table, my tegra driver patch is now optional (without it fbcon doesn't work properly, enable by adding fbfix to cmdline)
new_boot(123).img (newest at the moment) - fbfix isn't needed anymore, added support for tmpfs ACLs, enabled XZ compression (because after reaching a certain size, the kernel wouldn't find the initramfs anymore), enabled KVM
Bogdacutu said:
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Click to expand...
Click to collapse
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
_TB_TB_ said:
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
Click to expand...
Click to collapse
It will always return -ENOENT except for the first time the function gets called (which is enough for the screen to get initialized).
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
joshtheitguy said:
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
Click to expand...
Click to collapse
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Bogdacutu said:
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Click to expand...
Click to collapse
Thanks, that was the command I couldn't remember. Let me do a backup of it first then I will try again to see if the outcome is any different, I'll let you know how it goes once I have a chance.
Great i need a dual boot Android/Linux
Bogdacutu said:
What works:
Audio
WiFi
Click to expand...
Click to collapse
Bogdacutu said:
Got it working thanks to /u/GenuineAster, will post a full guide in a day or two.
Click to expand...
Click to collapse
Bogdacutu said:
Photos:
https://s3.amazonaws.com/pushbullet...OAfew/Screenshot from 2014-12-28 12:51:51.png
Click to expand...
Click to collapse
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
etienne51 said:
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
Click to expand...
Click to collapse
I just updated the boot.img from post #4, WiFi and sound work now, Bluetooth works if you load firmware but it's pretty unstable at the moment.
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
etienne51 said:
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
Click to expand...
Click to collapse
Not really, you can try messing with the governors and max frequency, iirc there's a script in the driver package that automatically sets the CPU frequency lower on boot.
Update: I got the touchscreen to work with the Android drivers! I will upload the changes to my kernel repo soon (as soon as I figure out which of all the changes I did are actually required).
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
No idea if HDMI works, I don't have a cable (my patch might break it though, in which case we'll probably need to change it). And it works on LTE tablets, but mobile data doesn't work (at least for now).
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
I just ordered a Mini HDMI to HDMI cable, it will arrive in less than a week. As soon as I get it, I'll tell you guys how it works!
/u/GenuineAster confirmed that HDMI isn't working. I'm going to get an Ethernet adapter for netconsole soon, so that I can find out why it doesn't work with my patch to the tegra driver (which I'm sure is the reason HDMI isn't working). I'm also working on a way to get libGL.so to work in an i386 chroot (so that we can try to play desktop games that aren't compiled for ARM yet).
I'm impressed that this actually works so well. Makes what I have on my Shield Portable look pitiful. No sound, no video acceleration, etc. Now the question is, what changes have to be made to a mainline kernel to get similar results? Well, minus the video acceleration that's likely hard-coded to a specific kernel version. Bogdacutu, do you have a patch of your changes? Your github repo isn't a forked copy of the kernel, so it's hard to see the initial changes. I'd like to get a copy of Fedora running. Also looking forward to your touchscreen fix. My usb-otg cable is flakey to the point it causes Ubuntu to reboot if I bump it too much...
Question to the larger community: Anyone know how to get the wireless controller to work with this? I poked at wpa_cli and a couple of the p2p_ commands, but so far haven't picked up anything from the controller when it's searching.
Edit: Seems the otg charging thing doesn't work either. Makes long-term use impracticle when an input device has to be plugged in. Any of the kernel hackers know the bits that changed in nvidia's lollipop kernel to allow this?
Code:
*** Disclaimer
As usual, I am not responsible for thermonuclear war or other apocalyptic futures.
TL;DR: If you break your device with this project, it's not my fault (although I will of course be willing to help you in your troubles!!).
Introduction
Have you ever wanted to use your Android device as a fully-fledged desktop Linux box? Now you can, with Tuxoid!
A year or two ago, I discovered the Linux-on-Android project. (http://forum.xda-developers.com/showthread.php?t=1585009) I was fascinated by the possibility of running Linux on top of Android and using a desktop environment. However, I was slightly disappointed by the lack of some features, as well as a lack of development over the time of the project's existence. Thus I embarked upon an epic quest (well maybe not quite that dramatic) to build my own version from the ground up, basing it upon the ideas explored by Linux-on-Android.
After some on and off hacking on my OnePlus One, I now have some very early working code.
Below is a video demonstration of the current state of Tuxoid, demonstrating a few of its features.
Here is a list of some of these features:
- The big one: fast and high quality display system
- Native keyboard and mouse support (automatically disables Android's built-in system)
- Audio support. Audio from the desktop environment is piped into Android's audio system, so you can use your device's speakers, headphones or bluetooth etc
UPDATE: First builds!
I've built the first publicly available versions of the project. Before you get excited, I should warn you that they are in an unstable state. You can grab the APKs in the Downloads section of this project, as well as on the Releases page of the project on GitHub. These builds are not for n00bs! If you're still determined to give them a try, here are the instructions:
Requirements
An Android device running 4.1 or newer (it will be availabe for older versions in the future, but for know only Lollipop is supported) Older versions now supported!
Root with SuperSU for managing permissions. I will not explain this here, as there are already hundreds of guides available. If you don't know how to root your device, this project (at least in these early stages) is not for you.
A reasonable amount of internal storage (at least 1-2 GB free)
A stable internet connection. Make sure you're using WiFi for best results.
A mouse and keyboard to control the desktop environment. You should be able to use wired ones (via an OTG adapter) or wireless via bluetooth. As long as Android recognizes it, you should be good to go.
This is not a requirement, but you won't be able to do much without it (for now): knowledge of the Linux command line and preferably how to use the pacman package manager for Arch Linux, as that is the distro upon which Tuxoid is based (more distros will be available down the line!)
Setup and installation
Once your device is rooted, open up the SuperSU app and go to the Settings tab. Find an option labelled "Mount namespace separation" and ensure it is UNchecked. (Make sure to reboot before continuing if you had to do this)
Download and install the APK for Tuxoid. Again, if you don't know how to do this, you shouldn't be attempting to install an early build Tuxoid...
Open the Tuxoid app and tap the gear in the actionbar to go to the settings menu. There are a few options you can tweak here, but the main one you should be interested in right now is 'Disk image size'. Select a size that suits the amount of space you have free on your internal storage. I would recommend 4GB (the default) to allow room for installation of your own packages later. If you have less space free on your internal storage than you select here, the setup process will fail.
Go back to the main screen of the app and ensure you have a stable internet connection. Now connect your keyboard and mouse (you must connect them before booting Tuxoid up every time). Then, press 'Start' to begin the setup process. This will probably take a while, so just leave your device down for a while and check up on it every once and a while.
Eventually, if all went well, you should see a screen with a grey background and an xterm window. Feel free to run some commands. To start, I'd recommend installing the Chromium browser (open source version Google Chrome). To do this, run 'sudo pacman -S chromium' (without quotes). The password is the same as your username. Once installed, run 'chromium' to start the browser. For those who are interested, the window manager installed by default is Openbox. If you want to install some more packages, the list of available ones in Arch Linux for ARM devices is available here: http://archlinuxarm.org/packages If you weren't able to get up and running (i.e. no screen with a cursor and no xterm), you can try some of the steps described in Troubleshooting & Tips.
When you're finished playing around, follow the steps below to ensure clean shutdown of Tuxoid. If you want to boot up again, you can just open up the app at any time and tap on the start button. Tuxoid will use your existing system image.
Shutdown procedure
When you're done, simply press the back key on your device to close the GUI and press the stop button to shutdown Tuxoid. After a few seconds, the log will show "SHUTDOWN!", meaning the shutdown procedure was completed successfully.
Troubleshooting & Tips
If Tuxoid failed to boot during the initial setup, you can retry by first removing files in the 'droidtop' folder on your internal storage (usually 'system.img' and 'arch.tar.gz') and then pressing 'Start' again in the app.
If your mouse and keyboard aren't working in Tuxoid, ensure that they were connected to your device BEFORE you pressed the start button and make sure they were detected by Android. If they weren't detected by Android itself the they definitely won't work with Tuxoid.
If you something goes wrong at any stage while using Tuxoid, please press the 'Send log' button in the app to send me a copy of the log shown on the main screen.
If the app crashes, a dialog will pop up asking you to send a report. Please do this as it makes it much easier for me to fix bugs!
If you have any feedback and suggestions, feel free to post them here in the forums! You can also submit issues on the GitHub project (although this is really more orientated towards developers)
If you are a developer and want to get involved in the project, you can post here in the forums and/or submit pull requests on GitHub.
Source code
I've published all of the source code for the app to GitHub (http://github.com/jackos2500/tuxoid) Feel free to fork and make changes, and, even better, submit pull requests to move the project forward!
Finally, I would like to say thanks to the guys over at Linux-on-Android for their great work, without which the idea for this project would never have existed!
XDA:DevDB Information
Tuxoid, App for all devices (see above for details)
Contributors
jackos2500
Version Information
Status: Testing
Created 2015-06-13
Last Updated 2015-06-14
Reserved
Changelog
v0.1.1
Adds compatibility for Android versions as far back as 4.1 (API level 16).
Bug fixes:
screen resolution could be detected incorrectly
'setenforce' could fail to execute due to its lack of existence on older platform versions
v0.1
Initial public release.
Reserved
Its really interesting to hear about linux on android
shahzu3 said:
Its really interesting to hear about linux on android
Click to expand...
Click to collapse
Yup! I think I'll put out a build later with some instructions so that people can try it for themselves.
Mm
shahzu3 said:
Mm
Click to expand...
Click to collapse
Well I've pushed out the first public build. Give it a try and tell me what you think!
Hi. Your project sounds great ??
Is really necessary to have so internal space or could it be possible one day to have the whole stuff on the external sd.??
That is just amazing, thanks for your work, a tablet running this would be really nice... I'm going to try it out.
Hello! This looks very promising but I can't find any download link. Is it missing?
Edit: My phone just didn't load the page fully, the download section is on the top.
DirkStorck said:
Hi. Your project sounds great
Is really necessary to have so internal space or could it be possible one day to have the whole stuff on the external sd.?
Click to expand...
Click to collapse
Good point! I'll see if I can do something about that sometime soon. Unfortunately if the chroot environment is not stored in a disk image the filesystem it is stored on must support Unix permissions, so no FAT32 formatted sdcards without disk images. FAT32 also limits file size to 4GB, so that would be the max size for a disk image there. I'll probably add a way of optionally adding an extra partition to your SD to get around this at some stage.
WideBRs said:
That is just amazing, thanks for your work, a tablet running this would be really nice... I'm going to try it out.
Click to expand...
Click to collapse
Cool, tell me what you think when you give it a go!
jackos2500 said:
Good point! I'll see if I can do something about that sometime soon. Unfortunately if the chroot environment is not stored in a disk image the filesystem it is stored on must support Unix permissions, so no FAT32 formatted sdcards without disk images. FAT32 also limits file size to 4GB, so that would be the max size for a disk image there. I'll probably add a way of optionally adding an extra partition to your SD to get around this at some stage.
Cool, tell me what you think when you give it a go!
Click to expand...
Click to collapse
I have been using Linux Deploy on my tablet and it worked quite well. They have the environment as an image on the internal or external sd card. I think 4GB is a enough for a Linux system. For those who want more would have to format the external as ext4.
DirkStorck said:
I have been using Linux Deploy on my tablet and it worked quite well. They have the environment as an image on the internal or external sd card. I think 4GB is a enough for a Linux system. For those who want more would have to format the external as ext4.
Click to expand...
Click to collapse
I've pushed a new release with support for devices running Android 4.1 and above. I think I'm going to start working on improving the user-friendliness of the project tomorrow. This will probably include improving the UI and setup process, as well as better error handling. Once that code is in place I won't have to refactor any new features I add to the new UI, so it makes sense to do it first. It will take a while, and whenever it's done, I'll probably start working on some of those new features.
Hi,
Could you tell me if:
a) my phones built-in keyboard will work?
b) if there's an option to use the touch screen to control the mouse?
Thanks
moodroid said:
Hi,
Could you tell me if:
a) my phones built-in keyboard will work?
b) if there's an option to use the touch screen to control the mouse?
Thanks
Click to expand...
Click to collapse
Right now, no. Both of these are definitely a high priority though.
jackos2500 said:
Right now, no. Both of these are definitely a high priority though.
Click to expand...
Click to collapse
Excellent, thanks. I'll keep an eye on this...
Can i decompile and compile apk with this Linux for Android? I havent pc
this is really amazing, as it is very useful for tablets, at least for my tab s 10.5 inch, keep it up!
Currently using Xserver Xsdl, with the pain of slow refresh rate and input interrupt.
Thank you for this effort!
Hello,
So far, I had these issues before it worked, otherwise its awesome, the only way to render x server on android smoothly and no input latency without using direct (kernel) framebuffer:
1)Latest arch armv7hf use xorg-server and xf86-input-evdev compiled for/by version 1.18.x , had to recompile 1.17 from source since your module (the source code isnt released in your github :/, guess you forgot) is compiled for ABI module 20, currently 23.
2) High cpu usage, probably implement refresh rate limitation on the app side for displaying the shared memory framebuffer, though having the source code for the module would really help, guess its a modified dummy.so (?) to copy framebuffer to shm? Anyways ill try to workaround the issue using a compositor.
Thats all! working perfectly... If anyone need the compiled 1.17 versions of xorg-server and evdev, just use ABS or pm me.
Thanks!
EDIT: I think it would be better to turn this into X server framebuffer viewer app, and combine it with Linux deploy (+ 'custom scripts' option is already implemented in Linux Deploy, useful for evdev and xorg config) for more linux flavours
apparently, it seems that you have copied droidtop project without mentioning it (license: MIT) : https://code.google.com/p/droidtop/
which has been archived now with no public access
This thread, and Marshmallow/Nougat porting in general, are a continuation of the previous KitKat and Lollipop development; the general installation steps are more or less the same. If you need a very detailed guide, PeteInSequim's is a good resource, especially if moving from stock. Read/search through the previous threads for any missing information (CM12.1 OP). That being said, I'm uploading personal builds of AOSP 6.0/7.1, CM 13.0/14.1, TWRP, etc, here.
Some of the important device-specific changes from KitKat/CM11 are described in Hashcode's thread. The goal is to remain fairly close to CM or AOSP upstream, and integrate whatever fixes and enhancements in unified device trees. More progress information will be added here gradually, as I have time. A lot of useful discussion happened on the previous CM11, CM12.[01] threads, and the status of things is available to anyone willing to search. I am not a developer, mostly a hobbyist, and the usual disclaimers apply.
AOSP vs CM
Initially, AOSP builds happened out of curiosity, but also necessity, since CM13 needs some time to stabilize. As expected, an AOSP ROM is a lot more barebones than CM, and there are pros and cons for each flavor. Now that initial porting is done following the previous philosophy of reusing and common-izing the device trees, it seems feasible to maintain both AOSP and CM ROMs (whenever 13 is usable), although nothing is promised.
In truth, the current builds are more accurately described as AOSP-ish; at the very least, a few core components need to be modified for our HALs, proprietary blobs, etc. On top of that, I've been adding features and fixes that seemed essential to me. Still, major differences remain compared to CM, and before people deem them as bugs, here are a few:
Wake with Home button: not an AOSP feature; I took the CM code to make it work in these builds.
The Advanced reboot menu: also a custom feature; may be ported at some point.
Mounting exFAT or NTFS media: not AOSP-supported filesystems, but a priority for me.
BusyBox was a CM extra, but I'm including it starting with the November 8th builds.
Etc, etc.
Because we have a reasonably flexible build system, other ROM flavors could happen in the future. A custom ROM like CM is actually easier to maintain than AOSP given all the fixes and enhancements that need separate maintenance with the latter.
The major difference with the first November builds is having SELinux enabled (albeit Permissive). It had to be kept completely disabled during the initial porting, due to a kernel bug/missing feature that took more than a week to track down. Thus, logs contain lots of AVC denials now, as sepolicy has not been fully updated for MM; no need to report or worry about these yet.
On a personal note, posting on my threads is pretty tricky business... My builds were never intended for general consumption, but rather a way to move porting and development forward, and I often debate only keeping the GitHub repositories for people to build themselves. Obviously, that would upset hundreds of people at this point, so I make an effort to upload reasonably bug-free builds, as well as help even with trivial non-problems whenever I can. Nevertheless, low quality, or badly written posts (and I don't mean bad English) are a sure way to get ignored, and my memory is pretty long term Basically, I won't police content here, but I also don't want to deal with the the kind of stupidity and entitlement so prevalent in real life.
In conclusion, no need to thank (unless you really want to), or ask about donating, etc, but do reassess the limits of your current understanding before making bold claims, as I do too. Nothing worse than having to fix a trail of misinformation... Also, comparisons to other people's work (unless constructive), complains about the state of things, or simply starting with "no offense" and such, will make your problem much less likely to be solved by me.
XDA:DevDB Information
AOSP 6.0/7.1; CM 13.0/14.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
amaces, Hashcode, verygreen
Source Code: https://github.com/airend/android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2015-11-02
Last Updated 2018-07-29
GApps & Partitioning Info
With unusual issues, especially if connected to Play Services, I recommend testing the ROMs without GApps before reporting bugs.
Currently, pico Open GApps should work on all AOSP, CM, or Lineage builds (M & N), although initial flashing should to be done before first boot (wiped data). With CM/Lineage 14, system space is barely enough, yet I still think we're fine with the current partitioning scheme. Changing it can introduce other complications, and haven't found an absolute reason for doing so. Nevertheless, it is possible to alter the partition sizes after installation, and thus increase available system space; @Lanchon prepared a pretty nice guide specifically for the Nook HDs.
About including GApps directly into the ROMs, I had tested this approach using the Open GApps manifests. While things can work better that way, legally, it wouldn't be a good idea to distribute these builds (for the same reasons CM had to stop including them). Also, I think there are a few people who wan't nothing to do with Google's proprietary services, so a likely deal breaker for them. We'll have to wait for the established packagers to decide how to deal with the MM changes, although my manifests are available, and one can include anything in personal builds.
Manifests & GitHub Branches
For people making their own builds, the customized manifests including my forked branches, and other changes, are kept more or less up to date at github.com/airend/android. There are currently three main branch pairs: cm-12/lolli, cm-13/marsh, and cm-14/nougat, the latter two being most updated. As the name implies, these manifests are based (and actually constantly rebased) on the corresponding upstream branch, either AOSP or CM/Lineage. Theoretically, once these manifests are stable, there is no need for local additions, but corrections might be needed nonetheless.
No need to repo init more than once, unless you're switching manifest branches (e.g., LP to MM, CM to AOSP, etc); repo sync will pull all manifest changes.
About naming conventions for my branches, I try to reuse as much as possible between CM/Lineage and AOSP, and when that's possible, branches are named lp-12, mm-13, etc. Otherwise, branches are named lolli, marsh, nougat, or cm-1*, depending on their base and specificity.
Upstream Lineage branch names haven't changed from old CM, and no current branch will be renamed here either (despite rebase).
The kernel repo contains additional feature branches named base/[subsystem], on top of Hashcode's last CM12.0 kernel. The main stable kernel is roughly equivalent to merging all these feature branches, although the history is different.
Recovery Information
We do have official TWRP images (https://twrp.me/Devices). While they don't work with CM12.1 anymore (for reasons described in that thread), they should be usable with all current Marshmallow builds.
More up to date eMMC TWRP images are included in the respective device folders. Personally, I've had a good experience with TWRP, and do not plan on looking at other recovery distributions. Now, there have been (very) sporadic reports of broken partition tables, soft-bricked devices, etc, blamed on recovery. Although recovery is usually not the actual culprit, here are some ways you can rescue a completely unresponsive device:
The instructions below are generic, and were meant for CWM. TWRP has all these image flashing features in the GUI, so CLI/shell is not strictly needed.
It's a good idea to keep a microSD card around, with my external recovery image, or verygreen's.
Once booted off the external recovery, you can easily fix whatever is broken (ADB is your friend here). There's no need to re-install CM11, as re-flashing recovery and/or boot will most likely fix your issue.
Recovery partition: dd if=<path to recovery image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
Boot partition: dd if=<path to boot/kernel image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
Afterwards, you should at the very least have a working internal recovery. I don't recall any instance where /system and/or /data became corrupted because of recovery, but you can certainly fix them now.
I've never tested this part, but I believe that you may be able to install an eMMC CM12 ZIP with verygreen's external CWM, even if /data and /cache are F2FS (assuming you copied all ZIPs onto the external card). My understanding is that only /dev/block/platform/omap/omap_hsmmc.1/by-name/system (always ext4, mountable by any recovery) is touched during installation, so you may even bypass TWRP completely.
P.S. If you broke you bootloader by flashing the wrong recovery flavor, despite all images being clearly labeled as hummingbird or ovation, well, no sympathy for you… Still, you can bring your device back to life within minutes as described above.
Selected FAQs
Should I use AOSP or CM/Lineage?
Depends entirely upon personal preference, which requires testing, and some amount of research into what makes a ROM different. There are substantial core differences between the two flavors, which are not obvious immediately. If installing for the first time, flip a coin (and avoid builds in experimental, of course).
How do I get root back?
Until recently, some type of SU binary was included with all ROMs (WITH_SU=true on CM/Lineage, or using this repo on AOSP). This was needed because third-party system-less solutions don't work with our quirky bootimages, and system-mode installers have other issues on N. As builds mature, I'm separating the SU backend from main OTAs, roughly like CM/Lineage did. On my Nougat builds, there are currently two system-mode options:
On AOSP, I adapted phh's OSS backend for system-mode install (addonsu-phh-arm.zip). You need the matching manager to control access. Later on, I ported CM/Lineage's AppOps-based SU to AOSP, so that addon works here as well (see next item). These binaries need to be flashed after every ROM update, same as GApps.
On CM/Lineage, you can install their official add-on (addonsu-arm-signed.zip); it will use the baked-in manager, so no extra APK required. Or, you can install phh's SU and manager, like on AOSP. Neither needs to be flashed more than once here given the existing addon.d support.
Why no official CM/Lineage builds since 12.0?
The answer involves both technical complications, and some amount of politics. Getting changes accepted for non-mainstream/deprecated platforms like ours has been an uphill battle. Over time, many OMAP4 improvements have been developed outside CM, formerly by OMAP4-AOSP, now the Unlegacy-Android project. Those common hardware improvements have made it into 13.0/14.1 only recently, due to other people's perseverance. Although we're much closer to upstream Lineage compatibility, the hundreds of device tree, and more than a thousand kernel changes would still need to go through review. Given how long that takes for each item, and occasional opposition from non-OMAP4 reviewers, I decided to allocate my resources towards bettering these devices rather than official status. The downside is that people may feel dependent on my builds, which shouldn't be the case; I constantly rebase and maintain complete manifests, optimized for these devices. All the relevant changes are open and available in public GitHub repositories, which means anyone can submit them/try to work with upstream Lineage. However, for the above reasons, it's unlikely that I will make that effort.
What's the current status of full screen casting, Miracast, HDMI, etc?
Full screen casting to a Chromecast sink (either real, or emulated) works on all current Nougat builds. CM13 builds may have issues there, but AOSP M was fixes. Chrome casting from apps (the preferred way, if available) was never broken. Miracast in AOSP is pretty much legacy tech now. It also requires more hardware support compared to Chromecast-ing, and it probably doesn't work on any recent builds. Fixing HDMI is still a goal; it got broken on our devices after some Marshmallow revision. Until HDMI can be fixed, I disabled it completely to recover its unused VRAM allocation.
Will this (continue to) be based off AOSP, or CM?
belfastraven said:
@amaces, I am currently running with the 11/01 hummingbird build from experimental, which I installed yesterday. It doesn't work as well for me as the 10/29. It is laggier, and for some reason right now, I can't log into from the kindle app. I also note that on rebooting, it will go through the boot cycle more than once, optimizing various apps each time. Of course, since it just numbers the apps, you can't actually tell what it is doing. . I think there are olicy/permission issues since trickster mod can't install busybox into the system partition and, as stated before, system won't boot into to revery, soft boot, or shutdown, without use of power,home keys. Do you wan't logs?
thanks again.
Click to expand...
Click to collapse
On Ovation it is the same: 10/29 is far better than 11/01.
Graphics problems on 11/01: the screen shows some green lines sometimes and it feels laggier.
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
twiztid_ said:
Will this (continue to) be based off AOSP, or CM?
Click to expand...
Click to collapse
I would prefer AOSP: less customization means less resources needed.
...and for Ovation every MB of ram free can be fundamental.
Or maybe both versions
For some happy news, multi-window mode (enable in developer options) seems to work pretty well (on my HD) It's probably even more useful on the HD+ where you have more real estate.
Thank you @amaces for M!
Questions:
Are your repos in a state that I can start trying to build it?
Is this your (local) manifest https://github.com/airend/android/blob/marsh/default.xml
I saw the above manifest and tried to build a couple of days ago and got many errors just updating my local repo. I'm reckoning that the manifest has such a mishmash of projects that I should probably delete my entire repo and download it all again. Is this likely the case?
Again, thanks. I'm so excited!
Things are still busy till probably tomorrow afternoon, but I will add proper replies here, and on the CM12 thread soon. As of now, there must be a few dozen posts I need to go through, plus lots of other updates.
amaces said:
Things are still busy till probably tomorrow afternoon, but I will add proper replies here, and on the CM12 thread soon. As of now, there must be a few dozen posts I need to go through, plus lots of other updates.
Click to expand...
Click to collapse
Is gapps for 6.0 available? If so, which one do you recommend?
js290 said:
Is gapps for 6.0 available? If so, which one do you recommend?
Click to expand...
Click to collapse
OP has only two paragraphs. Try reading it again.
I have 2 HD+ and wanted to dedicate one to Marshmallow. I spent time with this build and it just became too frustrating.
I did find a gapps benzo-gapps-M-20151011-signed-chroma-r3.zip that did get rid of the nag messages with settings in settings-apps. I'll get links if others are interested. AdaWay 2.2 did give some strange messages about BusyBox scripts but it turns out there is a Mars working version of AdaWay, AdAway-release_Build-Oct.09.2015.apk that I haven't tried yet.
Very frustrating not really being able to use the ExtSdcard. Installation of apps is not that simple without using a third party browser.
First efforst here are great. If you look at first efforts on phones, disaster and pre=alpha is what is going on.
And for those of you who, like I, have been looking to find where the external sd carded is mounted if you want to keep it as an external sd card, on 11/1 build ,it is at /mnt/media_rw/FFF9-7EC0 on my HD-I think that that actual hex address part may vary. I was able to manipulate the files on it with the root explorer app. I think other apps will work as well--they just don't know where to find the external sd card... .
Root Explorer lets you set that path.
Also, I was able to enable and use the Sytem UI Tuner setting...
belfastraven said:
And for those of you who, like I, have been looking to find where the external sd carded is mounted if you want to keep it as an external sd card, on 11/1 build ,it is at /mnt/media_rw/FFF9-7EC0
Click to expand...
Click to collapse
Couldn't you use a script to mount(or link?) the folder to its "proper" location at start up?
I thought that's what the system did anyway.
twiztid_ said:
Couldn't you use a script to mount(or link?) the folder to its "proper" location at start up?
I thought that's what the system did anyway.
Click to expand...
Click to collapse
I think the issue is that it's "proper" location for Marshmallow (the system locates the card with no problem) is different from where older apps are looking for it. I'm sure one could add a link or links I was just happy to locate it
sephiroth2k said:
Got a working keyboard by flashing attached, Google Play Services crashes constantly and the screen randomly flashes garbled graphics, then locked up. Not exactly a daily driver, but cool nonetheless!
Click to expand...
Click to collapse
That's a problem with whatever GApps package you flashed; there are many crappy ones floating around. Either way, a clean AOSP installation has none of those issues.
games906 said:
What gapps do I need to use for the 6.0? One was too big, another wouldn't flash, one flashed but all of the Google apps crashed. Help!!
Click to expand...
Click to collapse
Read post #3.
Monfro said:
Other bugs I have found: SD is not recognized, home button is not mapped to wake the device.
AOSP keyboard crashes, but we can flash others. Google Play services crashed in the first minutes...I don't know if it started working well maybe after a silent update or it was not starting again.
Click to expand...
Click to collapse
Read OP about the distinction between AOSP and custom ROMs such as CM. Also, the AOSP keyboard is fine unless you flash GApps (see post #3.)
asakurato said:
It's not for daily use. Performace is quite good, if not better, but there are many bugs, like computer can't recognize both Internal and external sd (in mtp), file managers can't recognize external sd, constant keyboard crashes (you can use any other) and many other which I have forgotten or haven't found yet.
Click to expand...
Click to collapse
Monfro said:
So the only important bug I found is SD card not accessible: only built in file browser can correctly access it.
Click to expand...
Click to collapse
There are significant changes to storage management in Marshmallow, and I suspect those basic AOSP apps were once-again left behind, and are not using the newer APIs.
belfastraven said:
On Hummingbird, same as above re sdcard. Also location services seem not to be working properly. Accuweather, google maps don't seem to be able to access the services even though they have permission.
Click to expand...
Click to collapse
It's probably a missing location provider issue, like we had in the early days of CM12.0 (and which CM fixed). I'll need to track that down.
belfastraven said:
I've noticed a bit of what seems to be a memory management problem... once you have been using several apps for a while, (for me, NYTimes, kindle, Chrome_dev, settings, gmail, e.g. ) apps become rather laggy and you get the application not responding message. I am going to attempt to keep using this as my daily driver, however. Is there a way to do a soft reboot in this rom--previously you could do it from the power menu.
Click to expand...
Click to collapse
Although I haven't noticed that, all is possible; I haven't used my device for more than a few hours before having to work on fixing stuff, followed be reboot. The reboot options you're familiar with were a CM feature as described in the OP, but I plan to adapt their code. Beyond that, soft/reboot/recovery/power off don't seem to work at all, root or no root. It's possible CM was setting those in a legacy fashion for our devices (and even then, they were falling apart as you know).
toplist said:
Reboot to recovery isn't working for me. Currently, I'm running the latest experimental marshmallow build. I've been running op's cm12.1 build even before this thread was created. I didn't have recovery or power off problem like some users until the last cm12.1 10/18 build. When I saw the marshmallow build and decided to try it, that's when I found out that reboot to recovery and complete power off are not working properly. The way I access recovery now is manually pressing power button to shut it off and do power+home to boot to recovery. I tried flashing twrp 2.8.7.4 from amaces's folder and also twrp 2.8.7.0 using flashify. It doesn't fix the problem. I can't access fastboot from computer. When I use adb reboot bootloader command, it loads to cyanoboot and few seconds later shows android boot window. How can I get reboot recovery and power off working again?
Click to expand...
Click to collapse
The devices never had reboot to bootloader or fastboot support, and TWRP doesn't have much to do with reboot/power off within the ROM. Otherwise, read above; currently, if you need to power off, hold the power button for a few seconds to force shutdown.
belfastraven said:
@amaces, I am currently running with the 11/01 hummingbird build from experimental, which I installed yesterday. It doesn't work as well for me as the 10/29. It is laggier, and for some reason right now, I can't log into from the kindle app. I also note that on rebooting, it will go through the boot cycle more than once, optimizing various apps each time. Of course, since it just numbers the apps, you can't actually tell what it is doing. . I think there are olicy/permission issues since trickster mod can't install busybox into the system partition and, as stated before, system won't boot into to revery, soft boot, or shutdown, without use of power,home keys. Do you wan't logs? […] Have trickster mod running now--needed to install busybox through recovery. If there is anything you want looked at, let me know. I note that the system is "idling" a bit warmer than it was onlast Lollipop build--at a little over 30 degrees C. "miscellaneous" is using 22% of battery.
Click to expand...
Click to collapse
Didn't notice new lags on non-GApps install, but again, I must've tested a dozen builds since last week. The only major difference with 11/01 was turning SELinux on (albeit Permissive, see OP), after a week-long bug hunt. In the meantime, the repos jumped to r26 (MDB08M, same as latest Nexus 6P builds), which represents about two months of development upstream, so hopefully the next builds will be better. AOSP doesn't include busybox as you discovered, but you can easily install the package once you have root (Trickster MOD's dev publishes a good installer, so no need to flash stuff in recovery, although that works too).
Logs won't help much at this point since I can see all these issues on my device as well; I'm tackling them sequentially, but all these take a lot of time, so it'll be a while until decent ROMs happen.
Tschumi said:
In the experimental folder are the Marshmallow builds, did you flash over Lollipop? There are still a lot of kinks.
Click to expand...
Click to collapse
Definitely factory reset before installing Marshmallow.
belfastraven said:
no--I had been running the 10/29 Marshmallow--. I know that these are very early, but I think the 10/29 was working better for me. I'm sure some of this is not the rom, but the apps. I do note a lot of avc permission problems in the logs, as well as Choreographer complaining about missed frames..., I am excited that this is running at all.
Click to expand...
Click to collapse
The AVC denial messages finally show up after I fixed SELinux, and Permissive shouldn't negatively impact performance, but yeah, sepolicy needs to be updated for MM soonish. The missing frame issue is troubling, and I'll definitely investigate if it persists into what I deem as stable builds.
Monfro said:
On Ovation it is the same: 10/29 is far better than 11/01. Graphics problems on 11/01: the screen shows some green lines sometimes and it feels laggier […] I would prefer AOSP: less customization means less resources needed. ...and for Ovation every MB of ram free can be fundamental. Or maybe both versions
Click to expand...
Click to collapse
Same as above, and do let me know if these issues happen on a clean GApps-free installation.
twiztid_ said:
Will this (continue to) be based off AOSP, or CM?
Click to expand...
Click to collapse
OP updated with relevant info, but yeah, ideally both will be maintained side-by-side. Of course, CM13 is in huge flux right now.
Zippy Dufus said:
Are your repos in a state that I can start trying to build it?
Is this your (local) manifest https://github.com/airend/android/blob/marsh/default.xml
I saw the above manifest and tried to build a couple of days ago and got many errors just updating my local repo. I'm reckoning that the manifest has such a mishmash of projects that I should probably delete my entire repo and download it all again. Is this likely the case?
Click to expand...
Click to collapse
I've be trying to keep everything on GiHub up-to-date and reasonably stable. As you noticed, I've been crafting a de-bloated manifest that will make it even easier to replicate my builds (details in post #2).
Now, you can repo init on top of the CM12 sources, but you'll need to --force-sync since many repos are overwritten. That would only matter if you made local commits, especially if you didn't upload them, because you'd likely lose them. Better yet, I suggest keeping the CM folder separate, then initialize another one for AOSP with the --reference option. By referencing the CM folder, repo will attempt to reuse common repositories, which is the majority of Git objects. The checkout will still consume space, but the hidden .repo folder will be much smaller. Of course, referencing is not needed if you have enough space. Conversely, if you delete everything (that is including .repo) and initialize anew, you avoid all these issues, but going back will be a hassle.
Otherwise, I'm using a 4.9 EABI for kernel, but Google may insist on 4.8. If that creates issues (it'll be obvious, missing compiler type errors), you can either remove those prebuilts in your local manifest additions plus bring in a 4.9 kernel toolchain, or simply create a symbolic link (ln -s arm-eabi-4.8 arm-eabi-4.9) in platform/prebuilts/gcc/linux-x86/arm.
king200 said:
I have 2 HD+ and wanted to dedicate one to Marshmallow. I spent time with this build and it just became too frustrating. I did find a gapps benzo-gapps-M-20151011-signed-chroma-r3.zip that did get rid of the nag messages with settings in settings-apps. I'll get links if others are interested. AdaWay 2.2 did give some strange messages about BusyBox scripts but it turns out there is a Mars working version of AdaWay, AdAway-release_Build-Oct.09.2015.apk that I haven't tried yet.
Very frustrating not really being able to use the ExtSdcard. Installation of apps is not that simple without using a third party browser.
First efforst here are great. If you look at first efforts on phones, disaster and pre=alpha is what is going on.
Click to expand...
Click to collapse
You gotta read the OP, especially the end of it... But yeah, I'm sure you did your research regarding GApps; the end of October packages were much better, albeit still very flawed (see post #3). AdAway works perfectly once you're rooted, even with versions older than 10/09 in the semiofficial thread, which should've been your first go to. There's no issue with SD card mounting, but you should be aware that fancy filesystems (e.g., exFAT, NTFS) are not supported by AOSP. Also, apps need to use the MM storage APIs. In conclusion, do your testing on a clean slate, before flashing any GApps; all are buggy currently, and that situation has nothing to do with these ROMs.
twiztid_ said:
Couldn't you use a script to mount(or link?) the folder to its "proper" location at start up?
I thought that's what the system did anyway.
Click to expand...
Click to collapse
That won't work well since that path is not constant or universal. I'm sure we'll learn more about these new storage APIs, but I'm only providing the hooks based on the official documentation at: https://source.android.com/devices/storage/config.html#android_6_0.
belfastraven said:
I think the issue is that it's "proper" location for Marshmallow (the system locates the card with no problem) is different from where older apps are looking for it. I'm sure one could add a link or links I was just happy to locate it
Click to expand...
Click to collapse
Has anyone tried BaNKs MM gapps? People seem to be using them on the N4 with MM builds without any issues.
I'm doing much better with the 0129 build than the 1101. The 1101 build is unresponsive. Also, something like opening an SMB tab doesn't work.
I did this to solve the Google Play Services fc http://www.ibtimes.co.uk/android-6-0-marshmallow-gapps-how-fix-google-play-services-force-close-error-1524431
------------------------------------------------------------------------
With aosp_ovation-ota-MRA58K.151029.zip:
Avoided many hangs and reboots. Developer options->background processes limit->3 max has to be reset on each boot.
Green streaks on screen: developer options_>disable HW overlays. Select but after reboot, will reset to off.
Could browse to MicroSD card with Root Explorer, mnt/media_rw/147E-92D1, was not able to set the path for external card to that value.
Was able to set Home to card with Root Browser https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree
Moon Reader could find the card but not see any files in the root folder.
AnTuTu starts test but then closes.
Google Text-tospeech Engine give error messages. Pico TTS works but has to be set to very slow speech rate to be intelligible. Voice search works but, again, difficult to understand.
Kodi ran well. A big battery eater and video intensive.
Use Swype keyboard and freeze Android Keyboard.
Adaway, even the AdAway-release_Build-Oct.09.2015.apk would not install. Placed a working Hosts from another device file in /system/etc and it works fine.
Adb is more reliable with WiFi than cable.
king200 said:
I'm doing much better with the 0129 build than the 1101. The 1101 build is unresponsive. Also, something like opening an SMB tab doesn't work.
I did this to solve the Google Play Services fc http://www.ibtimes.co.uk/android-6-0-marshmallow-gapps-how-fix-google-play-services-force-close-error-1524431
------------------------------------------------------------------------
With aosp_ovation-ota-MRA58K.151029.zip:
Avoided many hangs and reboots. Developer options->background processes limit->3 max has to be reset on each boot.
Green streaks on screen: developer options_>disable HW overlays. Select but after reboot, will reset to off.
Could browse to MicroSD card with Root Explorer, mnt/media_rw/147E-92D1, was not able to set the path for external card to that value.
Was able to set Home to card with Root Browser https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree
Moon Reader could find the card but not see any files in the root folder.
AnTuTu starts test but then closes.
Google Text-tospeech Engine give error messages. Pico TTS works but has to be set to very slow speech rate to be intelligible. Voice search works but, again, difficult to understand.
Kodi ran well. A big battery eater and video intensive.
Use Swype keyboard and freeze Android Keyboard.
Adaway, even the AdAway-release_Build-Oct.09.2015.apk would not install. Placed a working Hosts from another device file in /system/etc and it works fine.
Adb is more reliable with WiFi than cable.
Click to expand...
Click to collapse
On the 11/05 hummingbird rom, rooted, but without gapps or any additional app loaded, I have no sound
or video . Loading a couple of apps from APKs, no location services, Amazon Kindle not responding, same as earlier.
This was a clean flash--wiped system, data, cache, dalvik...
I'll try playing with this a bit more.
belfastraven said:
On the 11/05 hummingbird rom, rooted, but without gapps or any additional app loaded, I have no sound
or video . Loading a couple of apps from APKs, no location services, Amazon Kindle not responding, same as earlier.
This was a clean flash--wiped system, data, cache, dalvik...
Click to expand...
Click to collapse
Hmm, the A/V stuff may be due to the inclusion of media_codecs_ffmpeg.xml, which is present only in CM. Since you're rooted, you could test this by deleting the <Include href="media_codecs_ffmpeg.xml" /> line at the end of /system/etc/media_codecs.xml.
The Amazon Kindle issue is intriguing; do you remember if you had it on the last CM12.1 builds? There could be several reasons, including a heap change that I made about a month ago. Either way, can you describe in more details what happens, and possibly capture a log?
amaces said:
Hmm, the A/V stuff may be due to the inclusion of media_codecs_ffmpeg.xml, which is present only in CM. Since you're rooted, you could test this by deleting the <Include href="media_codecs_ffmpeg.xml" /> line at the end of /system/etc/media_codecs.xml.
The Amazon Kindle issue is intriguing; do you remember if you had it on the last CM12.1 builds? There could be several reasons, including a heap change that I made about a month ago. Either way, can you describe in more details what happens, and possibly capture a log?
Click to expand...
Click to collapse
Deleting the line from /system/etc/media_codecs.xml fixed the sound and video problems.
Amazon definitely was fine on lollipop builds--it may have even worked on 10/29 Marshmallow, but I was so excited about that build I can't remember now It's one of my 3 or 4 most used apps.
What happens is that the application will start and if you are not logged into it already, will allow you to click on "start reading" and will bring up a log in page. Sometimes I have had the page come up, sometimes the application seems to freeze and then quit, sometimes I will get the "xxxx application is not responding..." message, sometimes it appears to restart on its own. I managed to log in once on the 11/01 rom, and then the application would die/freeze/etc when synching content so it never was usable. I could make no sense of the messages in the logs because I'm not experienced enough with this.
thanks for your help.
p.s. I cannot get the "file manager" app root access...