Related
I have started working on an app for Windows Mobile 6 phones w/ GPS to do run/walk/bike tracking like the Nike+. Here is a little Video of the app in action:
http://www.youtube.com/watch?v=bIqKHCb21cg&feature=channel_page
Version 0.6.5 9s attached
- Smartphone detection is in
- Run Form updated to be smartphone happy, view log is next.
Version 0.6.4 is attached
- Calories burnt calc!!!! (put your weight in...lbs for now...kg coming )
Version 0.6.3 is attached
- 1 Mile/KM kills the app bug fixed!
Version 0.6.2 is attached
- I am not dead! I promise
- This is mostly a maintence update. All the tracking code has been pulled from the views and put off in modules (as it should have been from the get go) so I can get a Smartphone version working soon.
Version 0.6.1 is attached
- Audio updates - new sounds for mile/km passed and distance goal hit
- Audio updates - updates to how the power management is dealt with for audio, still not perfect, but better
- Center button (on your direction pad) now turns the display off and on and also it stops the phone from sleeping when you use that display off method. This is great for phones that get a bit wierd on their GPS in unattended mode.
Version 0.6 is attached
- New internal tracking code to improve performance and make new feature additions easier (this was more about me than you )
- First audible notices. Each mile/km and distance goal hit. It is just a tone right now, but I will record and add voiced stuff tonight.
- New Settings tab for audible notices
- Smartphone users can atleast start the app and track a run now! (still no settings or view log...that is coming)
Version 0.5.9 is attached
- Fix the View/Save log bug (I hope)...you might have to delete your Run Log (yeah for Alpha testing!)
- New way to calculate speed that is more accurate for me. This might depend on what GPS chip your phone uses...try both and see which you like more (change in the Settings Screen)
Version 0.5.8 is attached
- AppToDate bug fix
- Start of true metric support
- little bug fixes
Version 0.5.7 is attached
- I think the String->Date bug is fixed, please let me know!
- Added an "Action" menu under the left soft key for start/stop/save (silly non-touch screen phone users!)
Version 0.5.6 is attached
- EMAIL A RUN!
(that is a horrible name for the feature right now....since it just gives you a link to share...)
http://www.trackmyrun.mobi/viewrun.php?run_id=18&auth_code=5qii4mfy
Version 0.5.5 is attached
- Settings screen is up and working
- Goal progress is based on settings now (not just 3.1 all the time)
- All based on miles still, KM is coming soon fear not!
- Few more bug fixes and exception catches
Version 0.5.3 is attached
- GPS unattended mode updates
- Few bug fixes
- Ignore Calories/Pace, those spots are place holders/debugging right now...they will work in a later release
Version 0.5.1 is attached
- GPS stays up in unattended mode now (screen off by time out or hitting the power button)
- Few little bug fixes
Version 0.5 is attached
- KML support is all in now
- Go to view a lot (has to be a new one) and select View in Google Maps
- Change the line in the KML file to be green since that yellow was hard to see
Version 0.4 is attached.
- Fixed a few of the stupid SubString() bugs
- Added Experimental KML support! (start a run, do some stuff, then go to options->experimental->Build KML). It will put test.kml in your devices root folder
- Working on new speed tracking code, it is far more accurate...but not done yet (so ignore that it has like 900 #'s after the decimal point)
- Ignore what it says for calories burnt...that isn't what you think it is
ENJOY!
Version 0.3 is attached.
Looks good! I would definatly use this app!
Looks impressive. The auditory upgrade feature would be cool to add.
There are similar Apps. One in particular is also cool is:
GPS Cycle Computer v2
http://forum.xda-developers.com/showthread.php?t=424423
How would this calculate calories burned if your activity differs?
i.e. Rollerblading vs. Running vs Cycling, etc.
or is it simply based on time and distance to give a general calculation?
Nice looking app, I will definitely be keeping an eye out for this one. Keep up the good work.
Does this track coordinates? Or does it track via something else? Cause then I'm thinking that you need an active data connection for this to work :|
Kraize said:
Does this track coordinates? Or does it track via something else? Cause then I'm thinking that you need an active data connection for this to work :|
Click to expand...
Click to collapse
It tracks coordinates, so no data plan is needed at all for this. Just a working GPS. Now, I plan in the future to have online features for showing your routes on google maps and storing run data online, ect...but that is in the future...
band27 said:
Looks impressive. The auditory upgrade feature would be cool to add.
How would this calculate calories burned if your activity differs?
i.e. Rollerblading vs. Running vs Cycling, etc.
or is it simply based on time and distance to give a general calculation?
Click to expand...
Click to collapse
There are some standard formulats that are based on weight, time of exercise and how vigorous the activity is. For walk, jog, run that is easy (since I now your MPH's). For biking, roller blading, ect that gets tougher.
This is looking awesome. Could really do with an App like this. Keep it up and hope your "about a week" estimate is correct for a first beta.
A question though; I have a Touch HD. Has the interface been written to be able to cope with a WVGA resolution?
dom_mitchell1 said:
This is looking awesome. Could really do with an App like this. Keep it up and hope your "about a week" estimate is correct for a first beta.
A question though; I have a Touch HD. Has the interface been written to be able to cope with a WVGA resolution?
Click to expand...
Click to collapse
I have only tested it on a VGA display (my Touch Diamond). I have played with it in the QVGA emulator and the Square VGA emulator. The layout is far from final (I am not happy with it at all right now), so that is in flux a lot.
Go ahead and try the current version if you like:
http://grebowiec.net/trackmyrun.zip
Please be aware this is a VERY alpha version. There are known bugs that throw exceptions that I don't catch...so be nice
If you do however have any failures or success, please let me know.
gweedo767 said:
Go ahead and try the current version if you like:
http://grebowiec.net/trackmyrun.zip
Please be aware this is a VERY alpha version. There are known bugs that throw exceptions that I don't catch...so be nice
If you do however have any failures or success, please let me know.
Click to expand...
Click to collapse
Thanks a lot! I'll give it a go once I get home and give you some feedback!
AppToDate Support
Could you possibly think about having this AppToDate Support. Since this is in the early stages of development, it would be great to run AppToDate to get the current version. Thanks.
Couldn't wait until I got home so just loaded it up here. Everything seems good until I tried to View Log when it crashes out on me.Unfortunately I don't have NETCFv35.Messages.EN.wm.cab installed installed so cannot view details.
Also +1 for Apptodate support!
dom_mitchell1 said:
Couldn't wait until I got home so just loaded it up here. Everything seems good until I tried to View Log when it crashes out on me.Unfortunately I don't have NETCFv35.Messages.EN.wm.cab installed installed so cannot view details.
Also +1 for Apptodate support!
Click to expand...
Click to collapse
Did you start and then stop a run? The log file isn't created until you do atleast one and I bet it is dying trying to read the log file (which doesn't exist yet for you if you didn't do a start/stop)
I will do some reading on AppToDate in a bit, see what all it takes to integrate it.
gweedo767 said:
I will do some reading on AppToDate in a bit, see what all it takes to integrate it.
Click to expand...
Click to collapse
That would be very much appreciated. It just makes things a lot easier.
gweedo767 said:
Did you start and then stop a run? The log file isn't created until you do atleast one and I bet it is dying trying to read the log file (which doesn't exist yet for you if you didn't do a start/stop)
Click to expand...
Click to collapse
Yeah I had done and paced about abit; notched up 0.003 miles. Stopped the run successfully and then tried to view the log.
I've just jogged home from a friend's house (1.237 miles). This time when I stopped the run it crashed. No error code or anything; just said I had to quit and restart.
Sorry that's probably not much good for bug finding!
dom_mitchell1 said:
Yeah I had done and paced about abit; notched up 0.003 miles. Stopped the run successfully and then tried to view the log.
I've just jogged home from a friend's house (1.237 miles). This time when I stopped the run it crashed. No error code or anything; just said I had to quit and restart.
Sorry that's probably not much good for bug finding!
Click to expand...
Click to collapse
Did it do fine during the whole run though?
gweedo767 said:
Did it do fine during the whole run though?
Click to expand...
Click to collapse
Yeah no problems there. Slight lag on speed changes but I guess that's to be expected/part of the suposed and much debated GPS lag on the HD!
No complaints about performance at all.
I'm really liking the look of the App, certianly looks good so far; will be awesome if/when audio feedback can be given.
Something that would be good is if you could make the data from the logs uploadable to a PC to plot onto a graph (via Excel).
Like I said, great work so far! Loving this, who needs Nike/Apple!
dom_mitchell1 said:
Yeah no problems there. Slight lag on speed changes but I guess that's to be expected/part of the suposed and much debated GPS lag on the HD!
No complaints about performance at all.
I'm really liking the look of the App, certianly looks good so far; will be awesome if/when audio feedback can be given.
Something that would be good is if you could make the data from the logs uploadable to a PC to plot onto a graph (via Excel).
Like I said, great work so far! Loving this, who needs Nike/Apple!
Click to expand...
Click to collapse
The lag might be that I only update the display every 5 seconds (that is for all data). I think I might update the speed in real time (there is a call back function I can attach to for that). I do have plans for graphing/tracking/mapping in the future via an upload to a website feature...but that is a bit down the road I want to get all the stand alone client features working correctly first!
Please let us know when you have completed a final version. this program will be very useful. I know its still in the early stages hopefully you will be able to find the bugs and get them fixed, so we can download complete version.
If you are using the EVO based build, you can ignore this thread.
This fix is ONLY for Desire based build with EVO's Camera application.
PLEASE DO NOT USE THIS FIX IF YOU ARE USING THE EVO BASED BUILD.
First!!
After i fix the real 5MP capture in HTCCamera, i have also fix the Thunder Cloud Review window in HTCCamera today.
The fix APK is including the real 5MP fix and correct review window after you capture.
There is no more thunder & cloud strange picture again. You can also do some actions, like Share,Delete,Goto Media Gallery or Capture again.
What's the fix
1.fix the Thunder Cloud Review Window
2.fix the real 5MP
3.fix the Shutter Sound , if you use my old file, please download it again(Update @2010/11/07)
I have only test in Desire base, OTA 2.29
How to install it?
The APK CAN NOT INSTALL into your HD2 Android.
You have two way to install this fix.
Make sure your /system is Rear/Write not Read Only.
1. Putting the HTCCamera.apk into your HD2 SD Card using File Explorer with root access, copy the fixed HTCCamera.apk to /system/app and overwrite the original one, if you can find HTCCamera.odex in the /system/app, please delete it. In order to prevent the default shutter sound, you have delete(or rename) the camera_click.ogg in system. Go to /system/media/audio/ui and find out the camera_click.ogg, delete it or rename it.
I suggest you can use a Free root File Explorer called "Super Manager". The software you can search it on Market by "Super Manager" or "gpc". It is my design. It can help you move the fixed APK file into /system/app.
2. Using shell command
Code:
adb push HTCCamera.apk /system/app
adb shell rm /system/app/HTCCamera.odex
adb shell rm /system/media/audio/ui/camera_click.ogg
If you use it in your release build, CREDITS, thanks
How to use it?
First, you have using the last EVO-bases kernel and the attachment APK file.
After installing it, you just have to launch the Camera.
If you are lucky, you can enjoy the new real 5 Mega pixel camera without Thunder Cloud right now. You don't have to reset you HD2-Android.
Enjoy it!!
If the fix is helpful, you can donate to me. thanks
Awesome!
Thanks a lot. I've been looking for something like this for quite a while.
Oh yes !
Thanks a lot !
Thanks for your work. now fix HD recording
(i know its codec related)
i have tried this but it just disable review after photo taking, is it something wrong?
Worked like a charm for me. thanks.
I used Android Commander to copy the file, I tried using super manager like you said but it would copy the file incorrectly to 0.00k, weird.
Anyway works now.
Thanks man. Works great.
Great Job
Tested Work 100%
Thanks
Does this fix the widescreen picture at 5mpx resolution. I don't think so
Sent from my HTC HD2 using XDA App
Any one having this resolution with this?
2592*1944 (Real 5 Mega Pixel)
How is it possible?
I did as mentioned in the first post, cloud at preview has been successfully fixed, but I didn't get the real 5 mega pixel. I desire it!
Can some one please help me?
After replacing my Camera app I now have no camera app at all! I tried 3 or 4 times, downloaded the file twice and used 2 different root explorers, including the one suggested.
Anyone know what could be causing this?
I am using a Desire-based build for Tmo-US, and I upgraded the kernel to Hastarin r8 before attempting this.
EDIT: Nevermind, switched builds now fix is already applied
works for me!
Hiya, first a big thanks for this one, seems to work perfectly, getting full 5mp (2592 x 1944) res photo's without the cloud stuff, review window works well, seems to keep to the 5 second timeout i put in settings for it too.. replaced original file with android commander btw, just make sure u got usb debugging mode on for that to work
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
working with darkstone froyostone 3.2 with hastarin r8 + letama's pppd wrapper v0.3 here
edit: been trying some more settings, and it seems that setting the camera to widescreen just stretches the photo to widescreen, the picture looks squashed compared to what u see in the viewfinder(screen) before u take the photo. doesn't seem to be the case for the 4:3 mode though, taking pictures there just gives nice unsquashed photos
Perfect !
Thank for your hard work !
But how to ZOOM ?!
djbarney said:
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
Click to expand...
Click to collapse
Thanks for the work and I second the shutter sound request too.
noobshite said:
Thanks for the work and I second the shutter sound request too.
Click to expand...
Click to collapse
fix it now.
You can referrer to the first post
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Will next fix for Face detection?
shree.cse said:
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Click to expand...
Click to collapse
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
I remember 1 of the version from darkstone ROM, the camera face detection is working fine. But i can't recall which version is that.
iamgpc said:
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
Click to expand...
Click to collapse
Then what does this mean?
Fix: Real 5mpx
Sent from my HTC HD2 using XDA App
Weeds2000 fixed the orientation on our Folio100 to work with games like Asphalt5 and now its possible to play, although graphics are still kinda messed up. but other games like the 3d tilt works nearly perfect now too.
you might find it useful, and VEGAn mod might be able to include this as my FolioTntMod is based of the TNT framework...
Find the download patch i made for our folio in this thread.
it also include a full 360 rotation fix, if you need it
As we all share the same Tegra2 platform and can nearly swap experience here, im posting this to share the fixes weeds2000 made for us...
Hope you find it useful..
Note:
The patch i made might actually work fine as update.zip on your tablet as well, or might need minor adjust to install, but let g tablet modders fix this if needed.
at least now you know its available.
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
roebeet said:
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
Click to expand...
Click to collapse
Roeby wan Kanobi, is this something that could work and be added to TnT Lite? My Clockwork back up just completed
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
This could be another watershed update Also- with the accelerometer corrected, folks will be getting exercise by holding up the G while playing games
added:
Perhaps the one extra update that would be nice is a DSP manager so dB level or gain increases can be made. Modders released a DSP manager on the Incredible that allows increases to 3.5mm and speaker output. Hardware based EQ too.
Perhaps being too picky, but louder speakers would be nice.
Did you see.. they provided the SOURCE!!!!! This is what we need!
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
What does the patch change? Would is break things when the application developer fixes the orientation code in their game.
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Click to expand...
Click to collapse
okay here are some details.
the framework.jar modified comes from this file: update-smb_a1002-3338-user.zip
the library should be generic, but is required for the gsensor/rotation/orientation fix as part of the new framework.jar changes.
the 2 primary folders in the framework.jar changed are /android/hardware /android/view
you should be able to easily spot the differences in filesizes..
do note: there is another change android\os\Environment.smali as i modified it to work with /mnt/sdcard and /mnt/sdcard/sdcard-disk0 and /mnt/usbdisk-disk0 for compatibility with folio mount functionality.
here is the "vold" also different but works fine with the tap'n'tap framework.
remember that /etc/vold.fstab needs changed to support the more new mount devices if you wish to use that one too.
360 rotation fix is in android\view\WindowOrientationListener$SensorEventListenerImpl.smali
orientation fix is
android\hardware\SensorManager*.smali
but again, the framework.jar is Tap'n'Tap based, so works directly on top of r3338 edition.. and i made a patch in my section with just framework + lib files included.
rothnic said:
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
Click to expand...
Click to collapse
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Dexter_nlb said:
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Click to expand...
Click to collapse
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Thanks for the explanation - this is something I suspected would fix it, but it's good to see that someone had pushed the idea all the way through to an actual fix.
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
roebeet said:
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
Click to expand...
Click to collapse
That makes more sense to me if that is true.
I read through the code ... Prior to the code change they were performing the rotation either for Acceleration minus Gy on the y-axis
or Acceleration minus Gz on the z-axis and NOT Acceleration minus Gx on the x-axis. Now the axis swap is always occurring... under all 3 conditions irregardless of sensor.
Dont know why there was an exclusion in the first place for Acceleration minus Gx on the x-axis...
When I get back I will look through the code some more...
rothnic said:
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
rothnic said:
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
if Google didn't "invent" the different way of reading sensors, there would only be one way of doing it, so developers would not be able to see it, so an update to like 2.2 or higher is now an requirement, right? but if older games do not check, it would work with them, so this fix solves it as i see it.
putting back androidos orientation handling to its original state, as many developers should be reading it.
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
gojimi said:
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
Click to expand...
Click to collapse
remember its all done by weeds2000 , i cannot/will not take credits for his effort here, i am just sharing the good work done on this fix.
I have released a new version of the fix, this should clean up all the remaining issues with the accelerometer/compass. Code is also much cleaner now. Some weird hacks you may have seen were caused by the legacy API which was used by my test game.
Only known issue up to now is that the mouse coordinates are also rotated.
The source can be found in the zip file attached to the original post, I hope that all changes are prefixed with // XXX:
The source files are based on the nvidia-froyo tree.
Link:
http://forum.xda-developers.com/showpost.php?p=10209624&postcount=38
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Does this work for the VegaN Ginger Edition, or is that fix built into the ROM, I think I am having issues with some games on that ROM.
bmw4aaron said:
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Click to expand...
Click to collapse
I think you can write the developer and tell , that the games is not working normally.. all other games work fine, so why would one game stand out, only reason, bad programming, or misunderstanding of androidOS and orientation. maybe developer thought he should fix the "orientation" in his game on tablet, and forgot other trying to make it reverse.. so: bad programming and choice of developer..he should follow guidelines and not his ideas.
Hi, I moved to this ROM in the hope that doing a complete wipe would allow me to use my camera and this ROM seemed to have a lot of activity on the dev forum. Unfortunately I decided my camera is broken and I will have to order the part to replace it. I can accept that. However since moving to CodeFire I have been unable to run acatlog, logcat, or catlog extreme, or even 'adb catlog'. Logcat correctly requests superuser but does not build a log. I hope someone can help me. Other discussion on the net has not fixed this issue. Notably the supposed hidden menu to enable logcat does not open after entering the code.
The other issue is opening camera crashes CodeFire. But since everything else on this ROM works so well I'm going to just go along with it. What I really want is to just be able to watch the crash on 'adb catlog' though.
p.s. Why doesn't android embed nano? How am I supposed to read or edit config files? Is there another channel I should be asking these questions in? And what are the standard users in android? System and what? ADB was complaining it couldn't run catlog 'cause it couldn't write to /dev/[some_dir].
Never mind. I moved to the Synthetic AOSPx MOD. It's perfect except for lacking the swipe keyboard the JB mods have. I miss that but not as much as I appreciate having a mod that doesn't crash d/t broken HW. Really happy about this one. This also fixes my problem with catlog and even allows me to keep Google Now. How cool is that?
bnjo said:
Never mind. I moved to the Synthetic AOSPx MOD. It's perfect except for lacking the swipe keyboard the JB mods have. I miss that but not as much as I appreciate having a mod that doesn't crash d/t broken HW. Really happy about this one. This also fixes my problem with catlog and even allows me to keep Google Now. How cool is that?
Click to expand...
Click to collapse
Glad you've found your ROM.
Know issues:
1. Bluetooth toggle will not turn on
2. video codec makes first 10-15 seconds of video only green screen--(not noticed so much after install gapps and using chrome browser)
3. Camera not working
Resolved*
*testing phone had stock camera app disabled and was using open camera. With stock camera multiple crashes and unable to connect issue with camera. V3.5 has removed stock camera and added open camera to priv-app (preinstalled)
4. Microphone is also not working
V3.5 has fixed microphone.
5. video recording not working
V3.7 fixed video record for back camera only--also seems to have stabilized photo camera--(but still has crashed)
V-x-4.1 minor edits. Removed old renamed files. Removed apps and libs for fingerprint scanner. Swapped apns-config.xml from V21 to try get connection for more carriers. But it seems some devices are not able to even see imei from board V4.1 removed. Audio broken
x-v-4.6 has audio streaming partly functioning. Audio/ video plays some amount of time then stops. but will continues if playing through bluetooth. Further testing on speaker needed. Audio issue notIS present in FMRadio and unknown in phone. So far only in streamingMOST SOUND situations, like music apps and YouTube.
Also list of added apps primarily added for testing reasons
1. GPS test
2. AudioRecorder
3. File_Manager _es_file V3 (fewer ads)
4. OpenCamera
V5.0
removed extra fingerprint program, added MDDB folder (base band) trying to resolve 2 reports of lost IMEI on this rom. I have not had issue, so cannot confirm if adding these files has fixed problem.
V6.7-current beta
/system changes tracked on github
v6.7-or current /system
boot.img changes on github
https://github.com/mrmazakblu/Slim-port-boot-img
..
..
Install:
must have unlocked boot loader.
put rom file on sdcard and install with twrp =>Latest TWRP 3.1.1-0
you needs to install gapps.
http://opengapps.org/http://opengapps.org/
You need to enable navigation bar to get onscreen buttons.
settings >Navigation >Navigation bar >Enable navigation bar.
thanks to : @vampirefo this rom is ported from his build for the BLU Life Max
XDA:DevDB Information
Slim6 port for R1-HD, ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 's Blu Life Max SlimRom
Version Information
Status: Beta
Stable Release Date: 2017-06-16
Current Beta Version: x-5.0
Created 2017-06-09
Last Updated 2017-11-02
Thanks Great work I would like a RR.5.7.4
Enviado desde mi R1 HD mediante Tapatalk
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
meroher said:
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
Click to expand...
Click to collapse
there are 4 screen shots on the screenshot tab. But the look of any rom can be changes how you like with different launchers if desired.
Fixed the bugs except for the camera one.
New zip file in download tab.
Moved status from testing to beta.
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
vampirefo said:
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Camera Is Fixed*
I now have camera working on this slim port...
uploading built/port number 33 (X-3.3)
still needs small bug fixed, that will not screen cast to chromecast.
and first time I opened camera I did not have any on-screen navigation buttons(no way to exit camera). after some time buttons were available and next time it opened normal.
mrmazak said:
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Click to expand...
Click to collapse
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
vampirefo said:
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
mrmazak said:
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
Click to expand...
Click to collapse
Yes, ROM is built for 6737, R1HD and Life Max are almost the same phone, difference size, camera and 6737 instead of 6735.
Anyway good job.
Sent from my Life Max using Tapatalk
how is the performance vs stock with all bloatware removed?
deathblade200 said:
how is the performance vs stock with all bloatware removed?
Click to expand...
Click to collapse
Seems a little quicker on slim6
Great job, I like it
So is this a usable daily driver?
roboman2444 said:
So is this a usable daily driver?
Click to expand...
Click to collapse
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
mrmazak said:
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
Click to expand...
Click to collapse
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
roboman2444 said:
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
Click to expand...
Click to collapse
I do not think the camera fix here will help 7.
These lib files, "so" files, "blobs", call them as you will. Are still for Android 6 so , as I believe will not work on 7
mrmazak said:
Seems a little quicker on slim6
Click to expand...
Click to collapse
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
deathblade200 said:
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
Click to expand...
Click to collapse
They would be the same or about the same, a rom doesn't increase benchmarks, a custom kernel might, benchmarks have their place this isn't one of them.
To each their own I guess.
Sent from my Life_Max using Tapatalk