Ok, I´m working on CM7.2 for our device, almost all works perfect except few things. I do some research, but I don´t come to any working solution. So I want to discuss with you, maybe you´ll help or give me some advice.
Sd card or internal storage isn´t mounted correctly (one of them), if I get to work one, another stops and vice versa.
In system/etc/vold.fstab
http://pastebin.com/mqAfxeEZ
In system/build.prop
http://pastebin.com/2pFt6Kmu
SD/internal (one of them) isn´t shows in filemanager. What is strange is that I find the non working one in folders! Okay, for example SD card shows properly and I find another storage in folder Root/ss (example for folders understand Root/mnt/sdcard)
If nothing better, is there a way how I can mount folder "ss" as storage or sd card?
I appreciate any help, thank you.
This rom has non working camera also (and I also found some strange things), after I solve major problems I´ll release it. I successfully ported Some Miui GB on it, but I would like to solve problems on CM7.2 and then I can work on port. Because this problems remain in port as well.
In safestrap sdcard shows in the same folder "ss"
Maybe you've already looked into it, but what about searching into Hashcode's CM7 build? for what i can remember, sd was working, but i could be wrong...anyway Hash himself could throw some advice
Sorry but i didn't have the technical knowledge to actually help you with code, but i am working on getting it
All Hashcode links on his builds are dead =(, as far as I know this is based on Hashcode and DrWowe work. I tried mount it as it is on original 2.3.4 for our device, but thats non working, there is some different mount technique or I missing some point.
Thank you for reply, I didn´t have much experience yet too. I hope so Hash could help me, or anyone whos interested.
i find it sad, that we don´t have any working cm7 for now or Miui, because I love this one.
That's why I started working on it, even though I do not have much knowledge needed.
pepe55 said:
All Hashcode links on his builds are dead =(, as far as I know this is based on Hashcode and DrWowe work. I tried mount it as it is on original 2.3.4 for our device, but thats non working, there is some different mount technique or I missing some point.
Thank you for reply, I didn´t have much experience yet too. I hope so Hash could help me, or anyone whos interested.
i find it sad, that we don´t have any working cm7 for now or Miui, because I love this one.
That's why I started working on it, even though I do not have much knowledge needed.
Click to expand...
Click to collapse
Awww, right! i forgot that, i was able to find a build some time ago, but it was just the rom, not source code, i can find it, or re-upload (if i have it) if it's useful!
EDIT: found it on XDA right now
There you go: http://forum.xda-developers.com/showthread.php?p=23905801
Thank you very much, I must go to work now, but I look at it later and we´ll see what I can do =).
edit: Problems is still same on Hascodes build.
pepe55 said:
Thank you very much, I must go to work now, but I look at it later and we´ll see what I can do =).
edit: Problems is still same on Hascodes build.
Click to expand...
Click to collapse
Well, as of now, i am using eclipse rom, and in the vold.fstab the line are those:
Code:
# external sd card
dev_mount sdcard-ext /mnt/sdcard-ext:none:lun1 auto /devices/platform/goldfish_mmc.0 /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
# internal eMMC
dev_mount sdcard /mnt/sdcard 25 /devices/platform/mmci-omap-hs.1/mmc_host/mmc1
They look different, maybe you could try something like this then in the build.prop the lines should change too, if i guessed right, with something like:
Code:
# Mount the internal SD card, too
ro.additionalmounts=/mnt/sdcard-ext
# ADDITIONAL_BUILD_PROPERTIES
ro.additionalmounts=/mnt/sdcard-ext
ro.vold.switchablepair=/mnt/sdcard,/mnt/sdcard-ext
Just look into your build, when you can, or i'll try with Hash's build when it's possible
It doesn´t work that way. I have already tried something similiar, this one mount blank folder, mine mount internal(or sd), but always only one of them. (I tried setting from steel droid for example) As I can see, some roms has different mount setting. Cm7 maybe has some original one, which I cannot deal with.
I get half working camera, yes! =D But not for very long...
Yeah, anyway i wrote BS on the build.prop part, the first line is wrong,
pepe55 said:
I get half working camera, yes! =D
Click to expand...
Click to collapse
LOL, throw the mounting question away, i just miss a new build with functioning camera!
EDIT: Anyway...are you using Safestrap 3.05 for tests? i think it doesn't work at all with CM7 builds...i flashed a plain cm7.2 build in every slot and it gave me a black screen...hmmmm....
For the people who dont need this, the non mounted storage is still accessible throught filemanager, usb on pc mount it succesfull too. I see that camera is working on ICS builds, some of them, so I hope its not that hard to fix it on GB rom, maybe I´m wrong. I just need to test third party camera apps and see if one of them works. Maybe I need to merge some files from hashcodes cm7, but now I must really go =D.
edit: Yea mine edited builds are working with safestrap 3.05, thats main point =).
AWWWW YEA
I was searching some new GB goodness these days! waiting for the public build!
On hashcodes cm7 3rd party cameras worked
Sent from my XT860 using xda premium
Okay, I have got one camera app working, but its paid app, and not working in full resolution, Camera Illusion, but paid app isnt working...free version worked, maybe its because lower resolution...
i have 2 builds here:
- CM4D3-nightly-20111116-1445
- cm-7-20120708-UNOFFICIAL-solana
i can upload, if you need.
I modified both and it work with SS3.05 Its pretty stable, but suffers from non working camera and internal storage isnt mounted right (but it works anyway)
giovannipaquier said:
i have 2 builds here:
- CM4D3-nightly-20111116-1445
- cm-7-20120708-UNOFFICIAL-solana
i can upload, if you need.
Click to expand...
Click to collapse
can you upload cm-7-20120708-UNOFFICIAL-solana?
uploading at dropbox right now. will be in this folder: https://www.dropbox.com/sh/zw20u8hgrrdom3g/xW6EBXI030
will take some time .. tell me if there is something wrong.
---x---
DONE!
For reference my gits for CM7 are still around. Tho, I'm sure they are very outdated compared to 7.3 sources:
https://github.com/Hashcode/android_device_motorola_solana/tree/gingerbread
https://github.com/Hashcode/android_vendor_motorola_solana/tree/gingerbread
https://github.com/Hashcode/android_vendor_cyanogen (added the solana device)
https://github.com/Hashcode/android_frameworks_base/tree/gingerbread (with some omap4 patches)
https://github.com/Hashcode/android_system_core/tree/gingerbread (with the motorola device/permission patches in init)
https://github.com/Hashcode/android_hardware_ti_omap3 (motorola / ti patches)
https://github.com/Hashcode/android_hardware_ti_omx (motorola / ti patches)
https://github.com/Hashcode/android_hardware_ti_syslink (motorola / ti patches)
https://github.com/Hashcode/android_hardware_ti_wpan/tree/gingerbread (ti patches)
https://github.com/Hashcode/android_packages_apps_Phone/tree/gingerbread (global modes + dual modem patches for null crashes)
and a full manifest (CM7.0.x IIRC):
https://github.com/Hashcode/cm4D3/tree/gingerbread
The biggest hurdles I ran into, still centered around ducati sources for syslink 2.0 (codecs/camera).
In ways there is more for ICS/JB than there ever was for GB.
To do the camera correctly, you'd need to add more Motorola GB source to omx and dynamically link against their libs from the device used in the camera (libarc**).
Hashcode said:
For reference my gits for CM7 are still around. Tho, I'm sure they are very outdated compared to 7.3 sources:
Click to expand...
Click to collapse
By 7.3, are you referring to post 7.2 nightlies, culminating at current cm7-20130301?
Sent from my DROID RAZR MAXX HD
Is this still in the works/gonna happen? Because that would be great.
I just downloaded cm-7-20120708-UNOFFICIAL-solana and am going to test.
Related
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
cooljais said:
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
Click to expand...
Click to collapse
a suggestion for you...try the cm7 rom instead of miui ics build.
thanks for your effort. i will also dig about it but after my last exam. i request everyone who could contribute....its for our phone.
keep trying bro.
If it is simple enough I could give it a try, any moderate to advanced programming I wouldnt have a clue
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
st.matt said:
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
Click to expand...
Click to collapse
good job. if you need any help just let us know. i will try to look into it today night positively.
Anyone got any guides/tutorials kinda stuff for this?
Nopes, no tuts as such... just small guides....
Any links??
Keen to see how much of your port is working so far as well
EDIT: just tried it myself using a guide in other thread. used the DHD beta 3 and vivo latest CM7 nightly and is stuck at htc splashscreen
EDIT2: didnt sign the rom before, lets try that again...
EDIT3: still stuck on splashscreen
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Sounds good, what ROMs did you use to port it?
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Looks like a nice birthday gift... ;D
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://www.multiupload.com/Z4JKSC1JK2
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
l0st.prophet said:
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's probably not a bad idea. I will see if I have time tonight to try and see if I can get market working by using some of the desire s stuff.. or maybe someone else could try as well.
For anyone that gives it a go, just keep in mind that the button backlight levels are in framework-res.apk, and will need to be recompiled from source or decompiled and edited to get the levels right.
P1n3apqlExpr3ss said:
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Click to expand...
Click to collapse
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
st.matt said:
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
Click to expand...
Click to collapse
This sounds WAY over my head, all I tried was unzipping CM nightly 146 and the DHD build and changing files, rezipping and signing it. No wonder I got stuck at the HTC splashscreen...
Keep up the good work
st.matt said:
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://dl.dropbox.com/u/52030869/vivo_ics.zip
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Click to expand...
Click to collapse
great job bro! just need the camera and gmail account. rest everything is perfect ! i will try it today and see. thanks for your efforts
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Splux said:
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
yes its not working. can we get other links please?
Yeah sorry I didn't realise dropbox imposed download limits. Here is another download link: http://www.multiupload.com/Z4JKSC1JK2
I think I may have fixed Google accounts though, so there might be another download in another 30 minutes or so.
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
acerbix said:
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
Click to expand...
Click to collapse
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
+1 it's a good one and is one of my references too.
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
+1. Great recommendation. Just used it to complete my first build.
Sent from my MB860 using XDA App
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
acerbix said:
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
Click to expand...
Click to collapse
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info - trying it now.
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
acerbix said:
Thanks so much for the info - trying it now.
Click to expand...
Click to collapse
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
ghost_og said:
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
Click to expand...
Click to collapse
Oh okay - I thought I must be doing something stupid so I PM'd you last night rather than post here. So we all can get trackpad working in the kang but not device setting/lock/unlock
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
I tried replacing default.xml in .repo with the one in Atrix dev git repository, and then pulling down the code. That lead to multiple build failure, so I am assuming hte changes in the atrix dev github are not synced with the changes upstream coz vanilla cyanogenmod builds fine.
I am not even getting the "Device Settings" option that shows up in the weekly build, though the trackpad works fine. I'll try looking at the Settings.apk code to see if there is something I am missing.
cmkoj: Do you have a local_manifest.xml that works and gives you a good build? Open to sharing that?
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Right now, I'd settle for one that works for building. I manually overlay files, so that will definitely be easier
t.s.eliot said:
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
Click to expand...
Click to collapse
Lets know if you get it working I'm building too [clobber build just for the heck of it - will keep you posted]
Thanks a ton, cmkoj for all the help/pointers!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
ghost_og said:
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
Click to expand...
Click to collapse
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
acerbix said:
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
Click to expand...
Click to collapse
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
ghost_og said:
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
Click to expand...
Click to collapse
ye i forgot to mention that one lol, i thought its in the fingerprint build though. for my use i manually git cloned the vendor_motorola repo into /working_dir/vendor/ but havent had any luck. regarding the kernel afaik if you put the additional repos into your local_manifest.xml it should use the kernel from there (if one is available). but i dont really think the kernel is needed to be changed, since on my builds i had the authentec.truesuite (or whatever the process for fp is called) running, only the fp unlock/device option were missing (there is a Fingerprintsomething.apk in the vendor repo of atrix dev team that i have had pulled in and built with but it didnt work, so yes im slowly giving up (second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
as for the local_manifest.xml it should look like this http://pastebin.com/ccvVi2k9 for building the gb (that is with nav functioning fp but no unlock) if you want to get unlock to work you need to probably put in the other ones aswell (just by copying the <project path="device/motorola/olympus"
name="Atrix-Dev-Team/android_device_motorola_olympus.git"
remote="gh"
revision="gingerbread"/>
part and changing the name to appropriate and teh revision in all to fingerprint)
thanks go to fattire from the nook color forums who thought me how to make and edit these local_manifest.xml files and i used his file as a template for mine aswell.
i have to admit it im slowly sick of not being able to build one with working fp =/
Guys, see here for what directories to be pulled from atrix-dev-team github vs what to be kept in original CM7:
https://github.com/Atrix-Dev-Team/android/blob/gingerbread/default.xml
crnkoj said:
(second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
Click to expand...
Click to collapse
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
Another workaround is to add the following remote definition:
Code:
<remote name="github-https"
fetch="https://github.com/" />
Then change the project definition to:
Code:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https"/>
Once things are back to normal, you can remove the additional remote, and restore the original manifest.
Click to expand...
Click to collapse
It was provided in the comments section here.
ghost_og said:
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
It was provided in the comments section here.
Click to expand...
Click to collapse
yes thanks, lol, i knew about the fix and had the first part of it done with changing to https, but forgot about the second part, idiot i...
anyhow i resynced and am building now on the other pc with this local manifest http://paste.pocoo.org/show/534837/
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.
Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse
Woohoo! Look forward to trying this!
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Great work, thanks! I'm glad that there is work going on!
Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium
Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!
Wow!! Keep up the good work!!!
can't wait, great work!
Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia
obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.
this isnt for the K1 is it
It's for tpt only
When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?
TPT= ThinkPad Tablet
Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.
Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.
mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.
Hi, if anyone would like to run a 5.0.1 Google OS on a Archos G9 80S device (and currently basically verified only with this), download and extract the file
18_03_2015-20_58_50.7z
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important for the first installation. Updating a existing installation (same major version) doesn't require this step !).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient at least ~20 minutes for the first run!
What's new ?
------------ since 18_03_2015-20_58_50 -------------
tiler size modifications within kernel, suggested by stevemp (thanks!)
CM updates.
------------ since 15_03_2015-22_26_59 -------------
Netflix and widevine fixes from stargo (thanks!)
CM updates.
------------ since 09_02_2015-22_26_59 -------------
Only CM updates.
------------ since 12_12_2014-21_41_41 -------------
Initial release.
Kernel got some zram optimizations.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Thanks: @stargo @Hashcode @trevd
@CM community @all the cool omap4 hackers where I taken some code and inspirations !!!
Without these peoples, It would not so easy to make some (working) builds of the CM-12.0.
Archive:
15_03_2015-22_26_59.7z
12_12_2014-21_41_41 / 12_12_2014-21_41_41 (devHost)
09_02_2015-22_26_59.7z
XDA:DevDB Information
Archos G9 CyanogenMod 12.0, ROM for the Archos Gen9
Contributors
Quallenauge
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Current Beta Version: 12_12_2014-21_41_41
Created 2014-12-12
Last Updated 2015-03-18
Dankeschön
I now understand why TI exited the mobile SOC market - How can they expect to sell new stuff when the OMAP4xxx just won't die!
I shall give this one a whirl, It'll be good to get my archos off of the stock ICS.
I'm assuming you've dropped the recovery nonsense for that moment then?
is selinux off?
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
IIRC the 2012 nexus 7 took about 10 Minutes to boot so it's not far off.
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Anyway If I've got a bit of time / motivation I might have to have a cheeky hack on this , now that you've done all the hard work! .
I hope you don't mind but I've also given the file some re-hosting love just uploading it to devhost and androidfilehost too. I figured the space might aswell get used for something useful.. I'lll post the links when it's complete.:good:
Hack On! :good:
trevd
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J
Installed and i must say it's working really good :good:
schwatter said:
Installed and i must say it's working really good :good:
Click to expand...
Click to collapse
Hahahah! BI ZAR! I check the forum for my Archos 101 Gen9 Turbo once every X months, and checked it today and see LOLLIPOP / CM12?! GREAT!
And whats the status? I use the tablet a lot still, so what is NOT working?
Edit: Flashed it to a Archos 101 Gen9 Turbo, and all is working, and fast as hell. GREAT!
I came from Freezenook's ROM BUILD7 (VERY happy user) but now tried this:
A MA ZING!
How fast and cool this Lollipop is on our (old) Archos (101) Gen9 (Turbo) tablet!!!
For now only compliments and almost everything seems to work, and this is a major and recommended step! Great OS this Lollipop!
Tested
Speed: Good (17.106 AnTuTu 5.3)
Sound/Video: Yes
Touch: Very good
Camera: Yes
Battery: Good
Size: Lot of free space (3 - 4 GB free!)
Memcard: NOT TESTED YET
USB: Yes (with Archos Panel app (USB & deep sleep))(USB storage works)
MicroUSB: Only charging (no devices?)
HDMI: NOT TESTED YET
Headphone: Yes (low volume though)
Apps: Some apps I normally use on my tablet and phones (KitKat or older) are not (yet?) compatible, and cannot install. I really miss some, like Archos Video (Free)(MediaCenter.apk). Is it possible to port this APK to our new Lollipop, I would love that. And the other apps are just not there yet I guess (busy making them Lollipop compat)?
Thanks a lot !!
Supergeil!!!
Still amazing to see that you're still at it @Quallenauge
I will definitely flash it as soon as I have time.
The only concern I have is the USB Port. Does it stil work in 5.0 ? For me it didnt in 4.4, so I flashed back as I needed my Archos to read my Media USB-HDD. I have a 101S btw.
Well as soon as I have flashed it, I am going to test it and try a few things, hope I'll get it working :fingers-crossed:
Hi trevd!
trevd said:
I'm assuming you've dropped the recovery nonsense for that moment then?
Click to expand...
Click to collapse
This is not a "nonsense". But it doesn't reflect my current needs. It would be cool to have a standard recovery image to format the data partition with f2fs (The kernel should support it right now!).
trevd said:
is selinux off?
Click to expand...
Click to collapse
Yes. Currently I doesn't know how to enable selinux rules, because "rootfs" isn't the mounted loop device but the "real" root. So the file nods are forced to "ubject_r:unlabeled:s0" which doesn't fits.
trevd said:
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
Click to expand...
Click to collapse
Yes, ADB is turned on by default. I don't like it, when my device doesn't be verbose
trevd said:
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Click to expand...
Click to collapse
Yes, the old binary is bound to an older libsigchain.so. So I had to recompile it. The code quality is far better than my output So thanks for your work!
I have an issue with the ril implementation. Mobile signal is turned on, but the datakey pppd stuff is not called. Do you have an idea whats going wrong - where can I look.
Should I use your implementation from android_hardware_ril_libarchos_ril ?
trevd said:
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J
Click to expand...
Click to collapse
[/QUOTE]
Done. Thanks!
trevd said:
Dankeschön
I now understand why TI exited the mobile SOC market - How can they expect to sell new stuff when the OMAP4xxx just won't die!
I shall give this one a whirl, It'll be good to get my archos off of the stock ICS.
I'm assuming you've dropped the recovery nonsense for that moment then?
is selinux off?
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
IIRC the 2012 nexus 7 took about 10 Minutes to boot so it's not far off.
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Anyway If I've got a bit of time / motivation I might have to have a cheeky hack on this , now that you've done all the hard work! .
I hope you don't mind but I've also given the file some re-hosting love just uploading it to devhost and androidfilehost too. I figured the space might aswell get used for something useful.. I'lll post the links when it's complete.:good:
Hack On! :good:
trevd
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J
Click to expand...
Click to collapse
nilse said:
Supergeil!!!
Still amazing to see that you're still at it @Quallenauge
I will definitely flash it as soon as I have time.
The only concern I have is the USB Port. Does it stil work in 5.0 ? For me it didnt in 4.4, so I flashed back as I needed my Archos to read my Media USB-HDD. I have a 101S btw.
Well as soon as I have flashed it, I am going to test it and try a few things, hope I'll get it working :fingers-crossed:
Click to expand...
Click to collapse
External USB drive isn't supported right now. I will have a look, when I have some free time ( and after fixing the RIL mobile data connection stuff ).
Quallenauge said:
Hi, if anyone would like to run a 5.0.1 Google OS on a Archos G9 80S device (and currently basically verified only with this),
Click to expand...
Click to collapse
Wow, excellent! Thank you!
Could you please, write what you know that definitely doesn't and does work, as you did for older CMs?
Does ART work? Could CM 10.2 be updated to 12, or should we erase everything like with clean CM installation? HDMI?
@nilse: Yes USB (inc drives/storage) works (via Archos Panel app)!
@Bor-ka: Always do a full format/erase/factory settings etc, for SURE with a major leap like CM11 > CM12 or MORE!!
See my older post for a test of all hardware etc!
And again: Some apps I normally use on my tablet and phones (KitKat or older) are not (yet?) compatible, and cannot install. These apps are just not there yet I guess (busy making them Lollipop compat)?
I really miss some, like Archos Video (Free)(MediaCenter.apk). Is it possible to port this APK to our new Lollipop, I would love that!
thank you again for your great work.
Works on 80g9H 512 mb ram.
will test more functions and edit this post later.
@hackwerk, thanks!
For some reason unknown to me, there is no "export partition" in my SDE, so reformatting and copying to the /local/ is a little bit painful to me - should do it with adb shell.
But anyway, Archos Video Player is a show stopper for me. Since it is the only player that can natively play 720p/1080p movies on this tablet via DLNA/Samba. Tried MX player with latest codecs - no luck.
All
Did anybody compare deep sleep in CM with the stock ROM?
IIRC deep sleeped tablet with a stock ROM (4.*, 3.*) could lose only about 10 battery _a_week_ if not used. May be my memory deceives me, of course. But with CM 10.2 and no background tasks it drops by ~ 10% a night. (Didn't try Wakelock and Greenify though)
Bor-ka said:
@hackwerk, thanks!
For some reason unknown to me, there is no "export partition" in my SDE, so reformatting and copying to the /local/ is a little bit painful to me - should do it with adb shell.
But anyway, Archos Video Player is a show stopper for me. Since it is the only player that can natively play 720p/1080p movies on this tablet via DLNA/Samba. Tried MX player with latest codecs - no luck.
All
Did anybody compare deep sleep in CM with the stock ROM?
IIRC deep sleeped tablet with a stock ROM (4.*, 3.*) could lose only about 10 battery _a_week_ if not used. May be my memory deceives me, of course. But with CM 10.2 and no background tasks it drops by ~ 10% a night. (Didn't try Wakelock and Greenify though)
Click to expand...
Click to collapse
SDE: This ia an easy alternative way of installing the ROM (which I used)!
Video: Have you tried Skifta (good for network!) or other majors, like GoodPlayer, MediaPlayer Classic or the brand new official VLC Player (and thus MX Player))?
Maybe in combination with the "All Codecs for Archos Video" app?? Must be possible!
And maybe / I hope we can 'port' the MediaCenter.apk to Lollipop!
Battery: Is already good, but everyone talks about an app called Lux! And Greenify.
But yes Deep Sleep can be enabled in this ROM in the Archos Panel app too.
And maybe these famous mods can help too ( @Quallenauge: Checked them already I think?)?
hackwerk said:
SDE: This ia an easy alternative way of installing the ROM (which I used)!
Click to expand...
Click to collapse
Unfortunately I do not have "Enter the SDE menu on your device and select export data partition," in SDE.
See here, with screenshot http://forum.xda-developers.com/showpost.php?p=57243821&postcount=2
For video thanks, I'll try. Completely forgot about VLC. Tried MX already, it plays Ok from the internal memory/SD but gloriously fails over the network.
What Lux does is automagically lowers screen brightness, Yes, it is very useful app, but it will lower battery drain in the active mode, not in sleep when the screen is off. And it has a bad habit on my current cm10 installation - sometimes it restarts when I'm reading a pdf book at night (low memory?) and I get some two seconds of full brightness in my eyes. Ouch.. I think I'd revert back to manual "dimmer" or "blue light filter" and manual brightness adjustment.
What is strange, users at our local forum report that 5.0 is slower than the stock (?!) ROM on 80S 1.5 Turbo (4460) / 1GB RAM. I wonder what it will be like on my 1.2 (4430) / 512 RAM..
Thanks Quallange and all of you who helped him I saw your progress with 5.0 on github and I wanted to compile it myself but yeah I didn't had space for that sadly, I wanted to ask you flr it but then I see now that you got a cm12 thread when I am tomorrow home from school I will flash this :good:
Edit:
This song describes my 5.0 feeling:
http://youtu.be/p8sZcmQr6KY
It works till now pretty good. I am having the 512mb turbo version but after disabling things that I don't use it runs all smooth :good: o
I installed this Rom on my 101 g9 with 512 MB RAM.
It s like a new device. A lot less lagging and better ui response.
Only thing i found is that the keybord hides every now and then when i want to type some text.
Thanks a lot for this masterpiece of work *like*
Sent from my SM-N7505 using XDA Free mobile app
biggoof75 said:
I installed this Rom on my 101 g9 with 512 MB RAM.
It s like a new device. A lot less lagging and better ui response.
Only thing i found is that the keybord hides every now and then when i want to type some text.
Thanks a lot for this masterpiece of work *like*
Sent from my SM-N7505 using XDA Free mobile app
Click to expand...
Click to collapse
I agree, much more snappy than CM11. I've also had the keyboard hiding issue (stock and Swype). Thanks for keeping the G9 alive Quallenauge :good::good:
G9 80H
i installed the rom but it places data on internal storage. hard drive is placed at /storage/sdcard1 and is read-only
how can i place data on the hard drive?
Note: besides the internal storage issue, the rom runs nicely.
Hi Quallenauge.
Realy magic this ROM, many thanks.
If with JB sometime I have only 80 MB RAM free and with KK 145, now I have over 200 !!!
But I have a problem, app ( iGO ) can't write on external card.
Tried with 3 different SDFix and manually in system/etc/permissions/platform.xml
With Root Explorer I can copy, but can't modify permision.
There is a solution to this problem ?
Thanks in advance.